mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: llyyr <llyyr.public@gmail.com>
Cc: Jean Delvare <jdelvare@suse.com>,
	linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hwmon: (nct6683) Add another customer ID for NCT6687D sensor chip on some MSI boards.
Date: Mon, 15 May 2023 11:59:23 -0700	[thread overview]
Message-ID: <54471eb9-3cd0-429d-b652-07fd380f359d@roeck-us.net> (raw)
In-Reply-To: <20230515144910.13514-1-llyyr.public@gmail.com>

On Mon, May 15, 2023 at 08:19:10PM +0530, llyyr wrote:
> This value was found on a MSI Z690-A PRO DDR5 with NCT6687D.
> 
> Signed-off-by: llyyr <llyyr.public@gmail.com>

This needs to be a real name.

Guenter

> ---
>  drivers/hwmon/nct6683.c | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/drivers/hwmon/nct6683.c b/drivers/hwmon/nct6683.c
> index a872f783e..f673f7d07 100644
> --- a/drivers/hwmon/nct6683.c
> +++ b/drivers/hwmon/nct6683.c
> @@ -173,6 +173,7 @@ superio_exit(int ioreg)
>  #define NCT6683_CUSTOMER_ID_INTEL	0x805
>  #define NCT6683_CUSTOMER_ID_MITAC	0xa0e
>  #define NCT6683_CUSTOMER_ID_MSI		0x201
> +#define NCT6683_CUSTOMER_ID_MSI2	0x200
>  #define NCT6683_CUSTOMER_ID_ASROCK		0xe2c
>  #define NCT6683_CUSTOMER_ID_ASROCK2	0xe1b
>  
> @@ -1220,6 +1221,8 @@ static int nct6683_probe(struct platform_device *pdev)
>  		break;
>  	case NCT6683_CUSTOMER_ID_MSI:
>  		break;
> +	case NCT6683_CUSTOMER_ID_MSI2:
> +		break;
>  	case NCT6683_CUSTOMER_ID_ASROCK:
>  		break;
>  	case NCT6683_CUSTOMER_ID_ASROCK2:
> -- 
> 2.40.1
> 

  reply	other threads:[~2023-05-15 18:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-15 14:49 llyyr
2023-05-15 18:59 ` Guenter Roeck [this message]
2023-05-15 20:52   ` llyyr
2023-05-16 19:56     ` Guenter Roeck
2023-05-17  4:20 Gopal Prasad
2023-05-19 12:53 ` Guenter Roeck
2023-05-19 13:46   ` llyyr
2023-05-19 13:51     ` Guenter Roeck
2023-05-19 13:53       ` llyyr
2023-05-19 14:03       ` llyyr

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=54471eb9-3cd0-429d-b652-07fd380f359d@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=jdelvare@suse.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llyyr.public@gmail.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
all inboxes | Powered by JetHome®