From: Wolfram Sang <wsa@kernel.org>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: Andi Shyti <andi.shyti@kernel.org>,
Jean Delvare <jdelvare@suse.com>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>
Subject: Re: [PATCH RFC 2/2] i2c: i801: Call i2c_register_spd for muxed child segments
Date: Mon, 26 Feb 2024 11:36:30 +0100 [thread overview]
Message-ID: <Zdxprq9jukWj0XJF@shikoro> (raw)
In-Reply-To: <cf8058db-03d2-4d47-bc39-2645c3d42e10@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 723 bytes --]
On Thu, Feb 22, 2024 at 11:25:43PM +0100, Heiner Kallweit wrote:
> Once the gpio mux driver binds to the "i2c-mux-gpio" platform device,
> this creates the i2c adapters for the muxed child segments.
> We can use the bus notifier mechanism to check for creation of the
> child i2d adapters, and call i2c_register_spd() for them. This allows
> to detect all DIMM's on systems with more than 8 memory slots.
>
> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
Yay, this looks *much* better. Thanks for doing it! Sadly, I can also
only review, not test. Let's hope someone can step up to do the real
testing. Maybe resend it as RFT to lkml?
Reviewed-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-02-26 10:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 22:24 [PATCH RFC 0/2] i2c: i801: Call i2c_register_spd for muxed child segments Heiner Kallweit
2024-02-22 22:24 ` [PATCH RFC 1/2] i2c: smbus: Prepare i2c_register_spd for usage on muxed segments Heiner Kallweit
2024-02-26 10:32 ` Wolfram Sang
2024-03-02 20:21 ` Heiner Kallweit
2024-03-03 12:49 ` Wolfram Sang
2024-02-22 22:25 ` [PATCH RFC 2/2] i2c: i801: Call i2c_register_spd for muxed child segments Heiner Kallweit
2024-02-26 10:36 ` Wolfram Sang [this message]
2024-03-02 20:23 ` Heiner Kallweit
2024-03-25 12:34 ` Heiner Kallweit
2024-03-25 17:36 ` Wolfram Sang
2024-03-26 20:37 ` 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=Zdxprq9jukWj0XJF@shikoro \
--to=wsa@kernel.org \
--cc=andi.shyti@kernel.org \
--cc=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