linux-hwmon.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Hardware Monitoring <linux-hwmon@vger.kernel.org>
Cc: Jean Delvare <jdelvare@suse.com>, Michael Larabel <michael@phoronix.com>
Subject: Re: [PATCH] k10temp: 27C Offset needed for Threadripper2
Date: Tue, 7 Aug 2018 09:20:18 -0700	[thread overview]
Message-ID: <20180807162018.GA29384@roeck-us.net> (raw)
In-Reply-To: <1533658648-29154-1-git-send-email-linux@roeck-us.net>

On Tue, Aug 07, 2018 at 09:17:28AM -0700, Guenter Roeck wrote:
> From: Michael Larabel <michael@phoronix.com>
> 
> For at least the Threadripper 2950X and Threadripper 2990WX, it's confirmed a 27 degree offset is needed.

Applied to hwmon-next, and added stable tag. Michael, I took the
freedom to add your Signed-off-by:. Please let me know if that is
not ok.

Thanks,
Guenter

> ---
>  drivers/hwmon/k10temp.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/drivers/hwmon/k10temp.c b/drivers/hwmon/k10temp.c
> index 17c6460ae351..577e2ede5a1a 100644
> --- a/drivers/hwmon/k10temp.c
> +++ b/drivers/hwmon/k10temp.c
> @@ -105,6 +105,8 @@ static const struct tctl_offset tctl_offset_table[] = {
>  	{ 0x17, "AMD Ryzen Threadripper 1950", 10000 },
>  	{ 0x17, "AMD Ryzen Threadripper 1920", 10000 },
>  	{ 0x17, "AMD Ryzen Threadripper 1910", 10000 },
> +	{ 0x17, "AMD Ryzen Threadripper 2950X", 27000 },
> +	{ 0x17, "AMD Ryzen Threadripper 2990WX", 27000 },
>  };
>  
>  static void read_htcreg_pci(struct pci_dev *pdev, u32 *regval)
> -- 
> 2.17.1
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-hwmon" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2018-08-07 18:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-07 16:17 [PATCH] k10temp: 27C Offset needed for Threadripper2 Guenter Roeck
2018-08-07 16:20 ` Guenter Roeck [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180807162018.GA29384@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=jdelvare@suse.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=michael@phoronix.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).