linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Heiner Kallweit <hkallweit1@gmail.com>
To: "Wolfram Sang" <wsa+renesas@sang-engineering.com>,
	"Guenter Roeck" <linux@roeck-us.net>,
	"Armin Wolf" <W_Armin@gmx.de>,
	linux-hwmon@vger.kernel.org, linux-i2c@vger.kernel.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"René Rebe" <rene@exactcode.de>,
	"Thomas Weißschuh" <linux@weissschuh.net>,
	"Stephen Horvath" <s.horvath@outlook.com.au>
Subject: Re: [PATCH v4 5/6] i2c: smbus: Support DDR5 SPD EEPROMs
Date: Mon, 24 Jun 2024 22:06:16 +0200	[thread overview]
Message-ID: <9183dfda-d3f3-4fa1-9a4b-c6edeb30482d@gmail.com> (raw)
In-Reply-To: <veggn7y6qeeqx2dsmjykktudpwifnt5xzxcx5ulfglkgtq574p@f5dzhj4otjgl>

On 12.06.2024 18:19, Wolfram Sang wrote:
> 
> CCing Heiner...
> 
>>>>> Yes, maybe this could be simplified to "(LP)DDR memory types"
>>>>>
>>>>
>>>> I rephrased it to "Only works for (LP)DDR memory types up to DDR5".
>>>
>>> Thanks!
>>>
>>>> How about "Only works on systems with 1 to 8 memory slots" ?
>>>
>>> This is a question for Heiner. I'd think it is is still correct, but I
>>> don't know exactly.
>>>
>>
>> My interpretation was that it should work if the DIMMs are connected to
>> multiplexed I2C busses, but probably not if they are connected to
>> different adapters. The error message in that case is a bit misleading,
>> though, because it claims that "More than 8 memory slots on a single bus",
>> which isn't necessarily the case. For example, it should be perfectly valid
>> to have up to 24 DIMMs in this system.
>>
>> i2c-0/name:SMBus PIIX4 adapter port 0 at 0b00
>> i2c-1/name:SMBus PIIX4 adapter port 2 at 0b00
>> i2c-2/name:SMBus PIIX4 adapter port 1 at 0b20
>>
>> ... but I guess that is a question for someone with such a system to answer.
>>
>> Ultimately the handling of systems with more than 8 memory slots will need
>> to be updated at some point. On my systems, with 'i2c: piix4: Register SPDs'
>> applied, I see
>>
>> i2c i2c-0: 4/4 memory slots populated (from DMI)
>>     [my system is running 6.6.y which still generates that message]
>> i2c i2c-0: Successfully instantiated SPD at 0x50
>> i2c i2c-0: Successfully instantiated SPD at 0x51
>> i2c i2c-0: Successfully instantiated SPD at 0x52
>> i2c i2c-0: Successfully instantiated SPD at 0x53
>> i2c i2c-1: 4/4 memory slots populated (from DMI)
>> i2c i2c-2: 4/4 memory slots populated (from DMI)
>>
>> meaning the function is called for each adapter (which makes sense).
>> However, the code counting the DIMMs doesn't really take the adapter
>> into account, meaning adapters 1 and 2 are still probed even though
>> all DIMMs were already instantiated from adapter 0.
>>
>> On a system with more than 8 DIMMs connected to different piix4 adapters
>> (without mux) we'd probably see something like
>>
>> i2c i2c-0: More than 8 memory slots on a single bus, contact i801 maintainer ...
>> i2c i2c-1: More than 8 memory slots on a single bus, contact i801 maintainer ...
>> i2c i2c-2: More than 8 memory slots on a single bus, contact i801 maintainer ...
>>
>> which wouldn't be very helpful. I think the main problem may be that
>> the i801 driver implements sub-adapters as muxes, but the piix4 driver
>> doesn't do (or need) that. The message is also i801 centric which doesn't
>> apply anymore after 'i2c: piix4: Register SPDs' is applied.
>>
>> However, I would not want to even try changing that code without access
>> to a system using piix4 and supporting more than 8 memory slots.
>>
>> Thanks,
>> Guenter
>>
>>

It seems Intel systems never have more than one i801 SMBUS adapter,
therefore systems with more than 8 memory slots have to use muxing.
The current code was developed for the Intel use case, and therefore
doesn't consider that a system may have dedicated SMBUS controllers
per 8 memory slots. So support for this scenario has to be added.


  reply	other threads:[~2024-06-24 20:05 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-04  4:02 [PATCH v4 0/6] hwmon: Add support for SPD5118 compliant chips Guenter Roeck
2024-06-04  4:02 ` [PATCH v4 1/6] dt-bindings: trivial-devices: Add jedec,spd5118 Guenter Roeck
2024-06-04  4:02 ` [PATCH v4 2/6] hwmon: Add support for SPD5118 compliant temperature sensors Guenter Roeck
2024-06-04  8:48   ` Stephen Horvath
2024-06-04 14:31     ` Guenter Roeck
2024-06-07 15:55   ` Armin Wolf
2024-06-04  4:02 ` [PATCH v4 3/6] hwmon: (spd5118) Add suspend/resume support Guenter Roeck
2024-06-04  8:45   ` Stephen Horvath
2024-06-04 14:31     ` Guenter Roeck
2024-06-07 15:57   ` Armin Wolf
2024-06-04  4:02 ` [PATCH v4 4/6] hwmon: (spd5118) Add support for reading SPD data Guenter Roeck
2024-06-04 11:58   ` Armin Wolf
2024-06-04 14:30     ` Guenter Roeck
2024-06-07 15:59       ` Armin Wolf
2024-06-04  4:02 ` [PATCH v4 5/6] i2c: smbus: Support DDR5 SPD EEPROMs Guenter Roeck
2024-06-04  7:32   ` Wolfram Sang
2024-06-05 12:21   ` Paul Menzel
2024-06-05 13:56     ` Guenter Roeck
2024-06-17 14:42       ` Paul Menzel
2024-06-17 15:49         ` Guenter Roeck
2024-06-18 10:25           ` Paul Menzel
2024-06-18 13:32             ` Guenter Roeck
2024-06-18 13:51               ` Paul Menzel
2024-06-18 14:23                 ` Guenter Roeck
2024-06-18 14:59                   ` Paul Menzel
2024-06-18 15:10                     ` Guenter Roeck
2024-06-18 15:25                       ` Paul Menzel
2024-06-18 15:43                         ` Guenter Roeck
2024-06-18 18:16                         ` Guenter Roeck
2024-06-18 18:59                           ` Paul Menzel
2024-06-18 19:31                             ` Guenter Roeck
2024-06-18 15:12                     ` Guenter Roeck
2024-06-18 15:27                       ` Paul Menzel
2024-06-07 16:06   ` Armin Wolf
2024-06-07 18:00     ` Wolfram Sang
2024-06-10 13:52       ` Guenter Roeck
2024-06-10 14:52         ` Wolfram Sang
2024-06-10 15:55           ` Guenter Roeck
2024-06-12 16:19             ` Wolfram Sang
2024-06-24 20:06               ` Heiner Kallweit [this message]
2024-06-24 20:30                 ` Guenter Roeck
2024-06-04  4:02 ` [PATCH v4 6/6] hwmon: (spd5118) Add configuration option for auto-detection Guenter Roeck
2024-06-04  4:37   ` Thomas Weißschuh
2024-06-04 14:04     ` Guenter Roeck
2024-06-04  7:44   ` Wolfram Sang
2024-06-04 14:04     ` Guenter Roeck
2024-06-05  2:19   ` [PATCH v4a " Guenter Roeck
2024-06-05  9:22     ` Thomas Weißschuh
2024-06-05 14:04       ` Guenter Roeck
2024-06-07 16:08     ` Armin Wolf

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=9183dfda-d3f3-4fa1-9a4b-c6edeb30482d@gmail.com \
    --to=hkallweit1@gmail.com \
    --cc=W_Armin@gmx.de \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=linux@weissschuh.net \
    --cc=rene@exactcode.de \
    --cc=s.horvath@outlook.com.au \
    --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;
as well as URLs for NNTP newsgroup(s).