From: Heiner Kallweit <hkallweit1@gmail.com>
To: Wolfram Sang <wsa@kernel.org>, Andi Shyti <andi.shyti@kernel.org>,
Jean Delvare <jdelvare@suse.com>
Cc: "linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>
Subject: [PATCH RFC 0/2] i2c: i801: Call i2c_register_spd for muxed child segments
Date: Thu, 22 Feb 2024 23:24:02 +0100 [thread overview]
Message-ID: <eac54582-44f6-4101-93d9-012eb4ee3241@gmail.com> (raw)
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.
I tested that the events are properly recognized. However I don't have
hw with a muxed SMBUS, so I can't test the actual functionality.
Heiner Kallweit (2):
i2c: smbus: Prepare i2c_register_spd for usage on muxed segments
i2c: i801: Call i2c_register_spd for muxed child segments
drivers/i2c/busses/i2c-i801.c | 23 +++++++++++++++++++++++
drivers/i2c/i2c-smbus.c | 18 +++++++++++-------
2 files changed, 34 insertions(+), 7 deletions(-)
--
2.43.2
next reply other threads:[~2024-02-22 22:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 22:24 Heiner Kallweit [this message]
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
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=eac54582-44f6-4101-93d9-012eb4ee3241@gmail.com \
--to=hkallweit1@gmail.com \
--cc=andi.shyti@kernel.org \
--cc=jdelvare@suse.com \
--cc=linux-i2c@vger.kernel.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).