From: Ahmad Khalifa <ahmad@khalifa.ws>
To: Guenter Roeck <linux@roeck-us.net>,
Frank Crawford <frank@crawford.emu.id.au>,
Ai Chao <aichao@kylinos.cn>,
jdelvare@suse.com, linux-hwmon@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] hwmon: (it87) Add support for IT8625E
Date: Wed, 23 Oct 2024 13:41:47 +0100 [thread overview]
Message-ID: <103a68d6-d0b8-4e6f-ac8f-c6186b340f81@khalifa.ws> (raw)
In-Reply-To: <300383ee-3ead-439e-893e-895f3ed49805@roeck-us.net>
On 22/10/2024 14:40, Guenter Roeck wrote:
> On 10/22/24 03:13, Frank Crawford wrote:
>> On Tue, 2024-10-22 at 17:13 +0800, Ai Chao wrote:
>>> Add support for IT8625E on Centerm P410.
...
>> Can I just add that it isn't a good idea to use the same type for
>> different chips. There are some specific differences between the
>> chips, which mean that it should have its own entry in
>>
>> static const struct it87_devices it87_devices[]
>>
>> even if currently they are very similar.
>
> According to the information I have, the ADC voltage is different,
> and 8628 supports PECI but 8625 doesn't. Most importantly, 8625
> has multiple register banks. There are also some differences in
> fan control; 8628 can explicitly turn fans off using register bits.
>
> Just mapping the chip to it8628 may be convenient, but it is not
> acceptable.
Side question here. The standard for an acceptable chip driver is pretty
high (and rightfully so). But a common use case centres around readonly
display of information: temp/fan/in readings. Even just 2-3 readings are
better than nothing.
Example, I still have to use Frank's out of tree it87 for my IT8688.
It works perfectly fine for me, but still not possible to merge that
device into hwmon's it87.
This IT8625 is another example. The NCT6701D-R will be one more shortly.
A readonly driver that is configurable from userspace would help in that
use case. It can be configured for known devices without datasheets or
for testing new devices. Wouldn't even need to access superio config
space.
Filesystem has fuse, i2c has i2c-dev, input has evdev, ...
Would something similar be acceptable for hwmon?
--
Regards,
Ahmad
next prev parent reply other threads:[~2024-10-23 13:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 9:13 Ai Chao
2024-10-22 10:13 ` Frank Crawford
2024-10-22 13:40 ` Guenter Roeck
2024-10-23 12:41 ` Ahmad Khalifa [this message]
2024-10-23 15:42 ` Guenter Roeck
2024-10-23 22:19 ` Ahmad Khalifa
2024-10-24 0:47 ` Guenter Roeck
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=103a68d6-d0b8-4e6f-ac8f-c6186b340f81@khalifa.ws \
--to=ahmad@khalifa.ws \
--cc=aichao@kylinos.cn \
--cc=frank@crawford.emu.id.au \
--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®