From: Guenter Roeck <linux@roeck-us.net>
To: TINSAE TADESSE <tinsaetadesse2015@gmail.com>,
Andi Shyti <andi.shyti@kernel.org>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
Jean Delvare <jdelvare@suse.com>,
linux-i2c@vger.kernel.org, linux-hwmon@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] i2c: i801: Detect SPD Write Disable and expose as adapter quirk
Date: Wed, 10 Jun 2026 21:35:05 -0700 [thread overview]
Message-ID: <775f22d8-71b0-4a0b-9066-6eb2f62a2f9f@roeck-us.net> (raw)
In-Reply-To: <CAJ12PfPTzHbhaXH3sAnMoE9X8a4rHrpzv2jfdnqqJWXvx+OnGA@mail.gmail.com>
On 6/10/26 01:54, TINSAE TADESSE wrote:
> On Mon, Jun 8, 2026 at 3:28 PM Andi Shyti <andi.shyti@kernel.org> wrote:
>>
>> Hi Tinsae,
>>
>> sorry for the very late reply.
>>
>>> +/* SPD writes are blocked by host controller */
>>> +#define I2C_AQ_SPD_WRITE_DISABLED BIT(8)
>>> +
>>
>> We don't need this extra flag, we already do this statement in
>> i2c_register_spd().
>>
>> Can't we just assume that for spd5118 spd write is always
>> disabled? That's what happens in i2c_register_spd.
>>
>> Check:
>>
>> 84d477354b0a ("i2c: smbus: Support DDR5 and LPDDR5 SPD EEPROMs")
>> 4d6d35d3417d ("i2c: smbus: introduce Write Disable-aware SPD instantiating functions")
>>
>> Thanks,
>> Andi
>
>
> Hi Andi,
>
> Thanks for reviewing this patch series.
>
>> We don't need this extra flag, we already do this statement in
>> i2c_register_spd().
>
> Based on my testing, the issue does not appear to be in the SPD
> registration path
> handled by 'i2c_register_spd()'.
>
> I verified that:
>
> * The i801 driver correctly detects SPD Write Disable.
> * Disabling 'CONFIG_SENSORS_SPD5118_DETECT' completely eliminates the problem.
> * The suspend/resume failures only occur when 'CONFIG_SENSORS_SPD5118_DETECT=y'.
>
> Based on these observations, it appears that the SPD5118 detect path
> may instantiate
> the device independently of the SPD registration logic and therefore
> may bypass the
> SPD Write Disable handling added by commit 4d6d35d3417d ("i2c: smbus:
> introduce Write
> Disable-aware SPD instantiating functions").
>
> This would explain why SPD5118 is still instantiated on systems where SPD Write
> Disable is active, even though the SPD registration helpers are
> already SPD WD aware.
>
> The above observations are what motivated this patch series. Am I correct in
> suspecting that the SPD5118 detect path is separate from the SPD
> registration path, or
> is there another instantiation path that I should investigate?
>
The detect path [spd5118_detect()] is intended for systems where
i2c_register_spd() is not called. After all, not all systems with
DDR5 support have i801 or piix4 I2C controllers installed.
If your system uses one of those controllers (i.e., Intel or AMD
CPU), CONFIG_SENSORS_SPD5118_DETECT is not needed and should not be
enabled. There are some exceptions, such as servers with a large
number of DIMM slots, but that is not common.
Guenter
next prev parent reply other threads:[~2026-06-11 4:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 10:29 [PATCH 0/2] " Tinsae Tadesse
2026-02-05 10:29 ` [PATCH 1/2] " Tinsae Tadesse
2026-06-08 12:28 ` Andi Shyti
2026-06-10 8:54 ` TINSAE TADESSE
2026-06-11 4:35 ` Guenter Roeck [this message]
2026-02-05 10:29 ` [PATCH 2/2] hwmon: spd5118: Fail probe if SPD writes are disabled Tinsae Tadesse
2026-02-05 13:46 ` Guenter Roeck
2026-02-21 9:57 ` [PATCH 0/2] i2c: i801: Detect SPD Write Disable and expose as adapter quirk TINSAE TADESSE
2026-04-21 17:56 ` Mark Pearson
2026-04-23 11:21 ` TINSAE TADESSE
2026-05-04 21:41 ` Mark Pearson
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=775f22d8-71b0-4a0b-9066-6eb2f62a2f9f@roeck-us.net \
--to=linux@roeck-us.net \
--cc=andi.shyti@kernel.org \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tinsaetadesse2015@gmail.com \
--cc=wsa+renesas@sang-engineering.com \
/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
all inboxes | Powered by JetHome®