public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Heiner Kallweit <hkallweit1@gmail.com>
To: Jean Delvare <jdelvare@suse.com>,
	Andi Shyti <andi.shyti@kernel.org>, Peter Rosin <peda@axentia.se>,
	Wolfram Sang <wsa@kernel.org>,
	Peter Korsgaard <peter.korsgaard@barco.com>
Cc: "linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>
Subject: Re: [PATCH v2 0/4] i2c: Support i2c_register_spd() on multiplexed bus segments
Date: Fri, 26 Jan 2024 22:15:44 +0100	[thread overview]
Message-ID: <90278953-69f9-4602-be25-37da18e9ffb3@gmail.com> (raw)
In-Reply-To: <9f37f64e-f5b8-4928-8716-6d2846c2688a@gmail.com>

On 13.01.2024 12:23, Heiner Kallweit wrote:
> i801 is the last bus driver supporting I2C_CLASS_SPD. It's used for
> device probing on muxed bus segments. Only known use case so far is
> systems with more than 8 memory modules (with thermal sensor) on
> muxed smbus segments.
> As discussed with Jean, to be able to remove I2C_CLASS_SPD completely
> the following has to be done:
> 
> 1. Extend i2c_register_spd() for use on muxed bus segments
> 2. Enable explicit instantiation of thermal sensors on memory modules
> 3. Extend i801 to call i2c_register_spd() on muxed bus segments
> 
> Step 2 has been accomplished:
> caba40ec3531 ("eeprom: at24: Probe for DDR3 thermal sensor in the SPD case")
> 393bd1000f81 ("eeprom: ee1004: add support for temperature sensor")
> 
> Patch 1 does step 1
> Patches 2 and 3 provide the basis for patch 4
> Patch 4 does step 3
> 
> Note: i801 creates the mux platform device, loading and probing of the
> mux driver may be asynchronous. Therefore we can't call i2c_register_spd()
> for the muxed segments from i801. Instead we have to add a flag to the
> platform data, so that the mux driver knows it's supposed to call
> i2c_register_spd().
> 
> This series replaces the earlier RFC series.
> 
> v2:
> - remove now obsolete comment in patch 1
> - fix link error in some configs in patch 2
> 
> Heiner Kallweit (4):
>   i2c: smbus: Prepare i2c_register_spd for usage on muxed segments
>   i2c: mux: add basic support for calling i2c_register_spd on muxed bus
>     segments
>   i2c: mux: gpio: Allow to call i2c_register_spd on a muxed segment
>   i2c: i801: Call i2c_register_spd() on muxed bus segments
> 
>  drivers/i2c/Kconfig                        |  1 +
>  drivers/i2c/busses/i2c-i801.c              |  1 +
>  drivers/i2c/i2c-mux.c                      |  4 ++++
>  drivers/i2c/i2c-smbus.c                    | 20 ++++++++++++--------
>  drivers/i2c/muxes/i2c-mux-gpio.c           |  1 +
>  include/linux/i2c-mux.h                    |  1 +
>  include/linux/platform_data/i2c-mux-gpio.h |  2 ++
>  7 files changed, 22 insertions(+), 8 deletions(-)
> 
Any further feedback on this series, or is it ready to go?


  parent reply	other threads:[~2024-01-26 21:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-13 11:23 [PATCH v2 0/4] i2c: Support i2c_register_spd() on multiplexed bus segments Heiner Kallweit
2024-01-13 11:25 ` [PATCH v2 1/4] i2c: smbus: Prepare i2c_register_spd for usage on muxed segments Heiner Kallweit
2024-01-13 11:27 ` [PATCH v2 2/4] i2c: mux: add basic support for calling i2c_register_spd on muxed bus segments Heiner Kallweit
2024-01-13 11:28 ` [PATCH v2 3/4] i2c: mux: gpio: Allow to call i2c_register_spd on a muxed segment Heiner Kallweit
2024-01-13 11:28 ` [PATCH v2 4/4] i2c: i801: Call i2c_register_spd() on muxed bus segments Heiner Kallweit
2024-01-26 21:15 ` Heiner Kallweit [this message]
2024-02-21 17:19 ` [PATCH v2 0/4] i2c: Support i2c_register_spd() on multiplexed " Wolfram Sang
2024-02-21 19:46   ` Heiner Kallweit
2024-02-22 22:05   ` 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=90278953-69f9-4602-be25-37da18e9ffb3@gmail.com \
    --to=hkallweit1@gmail.com \
    --cc=andi.shyti@kernel.org \
    --cc=jdelvare@suse.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=peda@axentia.se \
    --cc=peter.korsgaard@barco.com \
    --cc=wsa@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