From: Jean Delvare <jdelvare@suse.de>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: Andi Shyti <andi.shyti@kernel.org>, linux-i2c@vger.kernel.org
Subject: Re: [PATCH] i2c: i801: Use I2C_CLASS_HWMON for i2c mux children
Date: Mon, 6 Nov 2023 15:50:36 +0100 [thread overview]
Message-ID: <20231106155036.366fb752@endymion.delvare> (raw)
In-Reply-To: <45c5366f-cbee-4c7d-bb62-a446935b2729@gmail.com>
Hi Heiner,
On Tue, 31 Oct 2023 21:30:22 +0100, Heiner Kallweit wrote:
> In case there ever should be a jc42-driven device on a muxed child bus,
> we may end up with multiple logical devices, see linked discussion.
>
> jc42 is the only remaining i2c client device driver supporting
> I2C_CLASS_SPD, however it supports I2C_CLASS_HWMON too. Therefore
> we can safely switch to I2C_CLASS_HWMON on the muxed child busses.
> IMO it's more logical anyway that the muxed child busses support
> the same class that the parent supports if it's not muxed.
>
> This change is one further step towards removing I2C_CLASS_SPD.
>
> Link: https://www.spinics.net/lists/linux-i2c/msg65458.html
> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
> ---
> drivers/i2c/busses/i2c-i801.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/i2c/busses/i2c-i801.c b/drivers/i2c/busses/i2c-i801.c
> index 070999139..8c9bb2e09 100644
> --- a/drivers/i2c/busses/i2c-i801.c
> +++ b/drivers/i2c/busses/i2c-i801.c
> @@ -1298,7 +1298,7 @@ static struct i801_mux_config i801_mux_config_asus_z8_d12 = {
> .gpio_chip = "gpio_ich",
> .values = { 0x02, 0x03 },
> .n_values = 2,
> - .classes = { I2C_CLASS_SPD, I2C_CLASS_SPD },
> + .classes = { I2C_CLASS_HWMON, I2C_CLASS_HWMON },
> .gpios = { 52, 53 },
> .n_gpios = 2,
> };
> @@ -1307,7 +1307,7 @@ static struct i801_mux_config i801_mux_config_asus_z8_d18 = {
> .gpio_chip = "gpio_ich",
> .values = { 0x02, 0x03, 0x01 },
> .n_values = 3,
> - .classes = { I2C_CLASS_SPD, I2C_CLASS_SPD, I2C_CLASS_SPD },
> + .classes = { I2C_CLASS_HWMON, I2C_CLASS_HWMON, I2C_CLASS_HWMON },
> .gpios = { 52, 53 },
> .n_gpios = 2,
> };
> @@ -1395,6 +1395,9 @@ static void i801_add_mux(struct i801_priv *priv)
>
> mux_config = id->driver_data;
>
> + /* Parent and mux children class support must not overlap */
> + priv->adapter.class = 0;
There may also be a hardware monitoring device on the parent segment on
these boards. With this change, that device will no longer be detected.
That would be a regression, so I have to nack this proposed change,
sorry.
The only way forward I can think of (if we want to get rid of
I2C_CLASS_SPD) would be to remove device auto-detection on children
segments completely (.class = 0 for them) and instead actively probe
for SPD EEPROMs and JC42 thermal sensors on these segments. For SPD we
should be able to just reuse i2c_register_spd(). For JC42 we would need
similar code, which doesn't exist yet.
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2023-11-06 14:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 20:30 [PATCH] i2c: i801: Use I2C_CLASS_HWMON for i2c mux children Heiner Kallweit
2023-11-06 14:50 ` Jean Delvare [this message]
2023-11-07 8:04 ` Heiner Kallweit
2023-11-09 13:52 ` Jean Delvare
2023-11-09 16:34 ` Heiner Kallweit
2023-11-10 11:08 ` Jean Delvare
2023-12-20 21:07 ` Heiner Kallweit
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=20231106155036.366fb752@endymion.delvare \
--to=jdelvare@suse.de \
--cc=andi.shyti@kernel.org \
--cc=hkallweit1@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.