From: Heiner Kallweit <hkallweit1@gmail.com>
To: Jean Delvare <jdelvare@suse.com>
Cc: "linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>
Subject: Re: [PATCH RFC] i2c: i801: Add i801_register_jc42, similar to i2c_register_spd
Date: Wed, 8 Nov 2023 11:28:45 +0100 [thread overview]
Message-ID: <b9a832d6-f7a8-4a9d-b639-181e074b4e9a@gmail.com> (raw)
In-Reply-To: <79977020-69c3-4f87-b861-b043c7fb9077@gmail.com>
On 08.11.2023 08:27, Heiner Kallweit wrote:
> As discussed, this is a RFC version of changing jc42 auto-detection
> with the goal to get rid of I2C_CLASS_SPD completely mid-term.
>
> Code of i801_jc42_probe() was copied from jc42 driver, just w/o
> the device id check. I think it's safe enough w/o this check.
>
> I don't have hw to test this, therefore it's compile-tested only.
>
> Link: https://lore.kernel.org/linux-i2c/a22978a4-88e4-46f4-b71c-032b22321599@gmail.com/
> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
> ---
> drivers/i2c/busses/i2c-i801.c | 48 ++++++++++++++++++++++++++++++++---
> 1 file changed, 44 insertions(+), 4 deletions(-)
>
That's quite some code for more or less nothing. I2C_CLASS_SPD is
relevant only for users:
- having one of the specific old ASUS machines with i2c-muxing
- having RAM with a jc42-compatible temperature sensor
- manually loading module jc42 to expose the temp sensor
From a maintenance point of view the easiest solution would be:
- set flag I2C_CLASS_DEPRECATED in addition to I2C_CLASS_SPD
to encourage potential users to switch to explicit instantiating
- wait few kernel versions and remove class-based instantiation
What do you think?
next prev parent reply other threads:[~2023-11-08 10:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 7:27 [PATCH RFC] i2c: i801: Add i801_register_jc42, similar to i2c_register_spd Heiner Kallweit
2023-11-08 10:28 ` Heiner Kallweit [this message]
2023-11-14 14:00 ` Jean Delvare
2023-11-14 14:44 ` Heiner Kallweit
2023-11-14 15:00 ` Heiner Kallweit
2023-11-15 11:00 ` Heiner Kallweit
2023-11-19 8:39 ` Jean Delvare
2023-11-21 12:34 ` Heiner Kallweit
2023-11-15 18:27 ` Jean Delvare
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=b9a832d6-f7a8-4a9d-b639-181e074b4e9a@gmail.com \
--to=hkallweit1@gmail.com \
--cc=jdelvare@suse.com \
--cc=linux-i2c@vger.kernel.org \
/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