[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <430e9fad-a877-4328-848f-59b982a10706@gmail.com>
Date: Wed, 24 Sep 2025 12:00:17 +0200
From: Clément Le Goffic <legoffic.clement@...il.com>
To: Julius Werner <jwerner@...omium.org>
Cc: Krzysztof Kozlowski <krzk@...nel.org>, Rob Herring <robh@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Krzysztof Kozlowski
<krzk+dt@...nel.org>, Maxime Coquelin <mcoquelin.stm32@...il.com>,
Alexandre Torgue <alexandre.torgue@...s.st.com>,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
linux-stm32@...md-mailman.stormreply.com,
linux-arm-kernel@...ts.infradead.org,
Clément Le Goffic <clement.legoffic@...s.st.com>
Subject: Re: [PATCH v7 2/7] dt-bindings: memory: introduce DDR4
On 23/09/2025 00:51, Julius Werner wrote:
>> + - pattern: "^ddr4-[0-9a-f]{4},[a-z]{1,10},[0-9a-f]{2}$"
>
> I don't really understand why there can only be up to 10 characters in
> the module part number. I also don't understand why you wrote "20
> bytes (10 chars)" for this in the previous patch. Are you assuming
> that module part numbers are UTF16LE? According to my reading of the
> spec, it sounds like they're supposed to be plain ASCII, i.e. 20 bytes
> should be able to contain up to 20 chars.
Hi Julius,
Yes plain ASCII needs 8 bits for each char as the value range is 0-127
I was having hexadecimal in mind while writing this, I'm sorry.
I'll fix it here and in the previous patch.
Best regards,
Clément
Powered by blists - more mailing lists