From: llyyr <llyyr.public@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Jean Delvare <jdelvare@suse.com>,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hwmon: (nct6683) Add another chip ID for NCT6687D sensor chip found on some MSI boards.
Date: Mon, 15 May 2023 20:18:32 +0530 [thread overview]
Message-ID: <d356103b-4d68-dc56-0324-4010a9015548@gmail.com> (raw)
In-Reply-To: <350dc86f-8341-4c3d-a3f8-0f4f5568ae77@roeck-us.net>
On 5/15/23 18:49, Guenter Roeck wrote:
> On Mon, May 15, 2023 at 02:55:46PM +0530, llyyr wrote:
>> This value was found on MSI Z690-A PRO DDR5, with a NCT6687D chip.
>>
>> Signed-off-by: llyyr <llyyr.public@gmail.com>
>> ---
>> drivers/hwmon/nct6683.c | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/drivers/hwmon/nct6683.c b/drivers/hwmon/nct6683.c
>> index a872f783e..5df9b9ce7 100644
>> --- a/drivers/hwmon/nct6683.c
>> +++ b/drivers/hwmon/nct6683.c
>> @@ -14,6 +14,7 @@
>> * nct6683d 21(1) 16 8 32(1) 0xc730
>> * nct6686d 21(1) 16 8 32(1) 0xd440
>> * nct6687d 21(1) 16 8 32(1) 0xd590
>> + * (0xd592)
>> *
>> * Notes:
>> * (1) Total number of vin and temp inputs is 32.
>> @@ -71,6 +72,7 @@ static const char * const nct6683_chip_names[] = {
>> #define SIO_NCT6683_ID 0xc730
>> #define SIO_NCT6686_ID 0xd440
>> #define SIO_NCT6687_ID 0xd590
>> +#define SIO_NCT6687_ID2 0xd592
>> #define SIO_ID_MASK 0xFFF0
>>
>> static inline void
>> @@ -1362,6 +1364,7 @@ static int __init nct6683_find(int sioaddr, struct nct6683_sio_data *sio_data)
>> sio_data->kind = nct6686;
>> break;
>> case SIO_NCT6687_ID:
>> + case SIO_NCT6687_ID2:
>> sio_data->kind = nct6687;
>> break;
>
> The checked value is masked with SIO_ID_MASK, or 0xfff0. Why would it be
> necessary or even make sense to compare that masked value with 0xd592 ?
> Please provide evidence that and why this code is needed.
>
> Guenter
You're right, sorry for the useless traffic. In my testing this only
worked because I was loading the module with `force=1`. This is actually
a case of missing customer ID, I'll be sending a different patch shortly.
next prev parent reply other threads:[~2023-05-15 14:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 9:25 llyyr
2023-05-15 13:19 ` Guenter Roeck
2023-05-15 14:48 ` llyyr [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-15 8:53 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=d356103b-4d68-dc56-0324-4010a9015548@gmail.com \
--to=llyyr.public@gmail.com \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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®