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 1/2] i2c: smbus: Prepare i2c_register_spd for usage on muxed segments
Date: Mon, 26 Feb 2024 11:32:43 +0100 [thread overview]
Message-ID: <ZdxoVALRR8rz23Z5@shikoro> (raw)
In-Reply-To: <db378364-018e-4e6b-8e41-8cdd21ce2afd@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 748 bytes --]
Hi Heiner,
> + /* Check whether we're a child adapter on a muxed segment */
The comment describes the 'if' but not 'then'. How about sth like "If we
are a child on a muxed segment then limit slots to..."?
> + if (i2c_parent_is_i2c_adapter(adap)) {
> + slot_count = 8;
I don't know much about DMI. I just noticed that there are no printouts
in this code path. Will there be one for the parent?
> + } else {
> + if (slot_count > 8) {
> + dev_err(&adap->dev,
> + "More than 8 memory slots on a single bus, mux config missing?\n");
With this error message, I as a user would think I need to setup a mux
config somewhere. But it is missing from DMI, or? Then, we should
probably use even FW_BUG in the message?
Happy hacking,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-02-26 10:32 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 [this message]
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=ZdxoVALRR8rz23Z5@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