From: Clement LE GOFFIC <clement.legoffic@foss.st.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>
Cc: <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-perf-users@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>
Subject: Re: [PATCH RFC 1/2] dt-bindings: memory: add jedec,ddr[3-4]-channel binding
Date: Thu, 10 Jul 2025 09:26:05 +0200 [thread overview]
Message-ID: <cadb2bcc-9a2a-447a-ac03-459f3e37a173@foss.st.com> (raw)
In-Reply-To: <e016efd6-891b-467e-8a4e-9ea53b7006a9@kernel.org>
Hi Krzysztof,
On 7/9/25 20:27, Krzysztof Kozlowski wrote:
> On 26/06/2025 21:48, Clément Le Goffic wrote:
>> Introduce as per jdec,lpddrX-channel binding, jdec,ddr[3-4]-channel
>
> s/jdec/jedec/
Right thanks
>
>> binding.
>>
>> Signed-off-by: Clément Le Goffic <clement.legoffic@foss.st.com>
>> ---
>
>
>> +
>> +additionalProperties: false
>> +
>> +examples:
>> + - |
>> + ddr_channel: ddr3-channel@0 {
>> + compatible = "jedec,ddr3-channel";
>> + io-width = <16>;
>
> Missing reg... or not? What was your intention
Indeed no reg.
I'll drop the "@0" for the next version.
>
>
>> + };
>>
>
>
> Best regards,
> Krzysztof
next prev parent reply other threads:[~2025-07-10 7:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 19:48 [PATCH RFC 0/2] Introduce ddr[3-4]-channel binding Clément Le Goffic
2025-06-26 19:48 ` [PATCH RFC 1/2] dt-bindings: memory: add jedec,ddr[3-4]-channel binding Clément Le Goffic
2025-07-09 18:27 ` Krzysztof Kozlowski
2025-07-10 7:26 ` Clement LE GOFFIC [this message]
2025-06-26 19:48 ` [PATCH RFC 2/2] dt-bindings: perf: stm32: introduce DDRPERFM dt-bindings Clément Le Goffic
2025-06-26 21:19 ` Rob Herring (Arm)
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=cadb2bcc-9a2a-447a-ac03-459f3e37a173@foss.st.com \
--to=clement.legoffic@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh@kernel.org \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).