[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d9432ec2-7075-4fef-ab39-aa93f4e91eb9@foss.st.com>
Date: Wed, 23 Jul 2025 09:54:31 +0200
From: Clement LE GOFFIC <clement.legoffic@...s.st.com>
To: Julius Werner <jwerner@...omium.org>
CC: Will Deacon <will@...nel.org>, Mark Rutland <mark.rutland@....com>,
Rob
Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor
Dooley <conor+dt@...nel.org>,
Maxime Coquelin <mcoquelin.stm32@...il.com>,
Alexandre Torgue <alexandre.torgue@...s.st.com>,
Philipp Zabel
<p.zabel@...gutronix.de>,
Jonathan Corbet <corbet@....net>,
Gatien Chevallier
<gatien.chevallier@...s.st.com>,
Michael Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...nel.org>,
Gabriel Fernandez
<gabriel.fernandez@...s.st.com>,
Krzysztof Kozlowski <krzk@...nel.org>,
Le
Goffic <legoffic.clement@...il.com>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-perf-users@...r.kernel.org>, <devicetree@...r.kernel.org>,
<linux-stm32@...md-mailman.stormreply.com>,
<linux-kernel@...r.kernel.org>, <linux-doc@...r.kernel.org>,
<linux-clk@...r.kernel.org>
Subject: Re: [PATCH v3 07/19] dt-bindings: memory: factorise LPDDR channel
binding into memory channel
On 7/22/25 23:58, Julius Werner wrote:
>> + purpose of this node is to overall memory topology of the system, including the
>
> nit: Might take the opportunity to fix the typo here (missing words:
> "is to describe the overall memory topology").
Yes true.
>
>> - Julius Werner <jwerner@...omium.org>
>
> Why remove me? (Although I'm also not really sure why I'm maintainer
> for this file and Krzysztof for all the others, tbh.)
I didn't remove you. It is just the minus of the maintainer list :-)
>
>> examples:
>> - |
>
> I think that's a load-bearing pipe character you're removing here?
Didn't remove either. There are spaces before so it it is not the git
minus char.
>
>> - lpddr-channel0 {
>> + memory-channel0 {
>
> Just to double-check, the name of this node doesn't really mean
> anything and isn't directly interpreted by the kernel, right? I'm fine
> with changing the example here to fit better with the new expanded
> scope of the schema, but we have existing firmware that generates
> nodes with the `lpddr-channel0` name, I want to make sure that it
> won't break from making changes here.
Oh ok didn't know about that and didn't find it though.
For now no pattern has been defined for the node name so it shouldn't
break anything.
Best regards,
Clément
Powered by blists - more mailing lists