From: Krzysztof Kozlowski <krzk@kernel.org>
To: Shubhrajyoti Datta <shubhrajyoti.datta@gmail.com>
Cc: Shubhrajyoti Datta <shubhrajyoti.datta@amd.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-edac@vger.kernel.org, git@amd.com, krzk@kernel.or,
robh@kernel.org, conor+dt@kernel.org, bp@alien8.de,
tony.luck@intel.com, james.morse@arm.com, mchehab@kernel.org,
rric@kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: memory-controllers: Add support for Versal NET EDAC
Date: Mon, 23 Dec 2024 15:02:26 +0100 [thread overview]
Message-ID: <c4b58b22-804b-4175-abb8-ff8929c5821d@kernel.org> (raw)
In-Reply-To: <CAKfKVtEREOLxK=SF5F-3MkpxyS+HcSTOH-pML2b4x2pCV13XMA@mail.gmail.com>
On 23/12/2024 10:58, Shubhrajyoti Datta wrote:
> Hi Krzysztof,
>
> On Sat, Nov 23, 2024 at 10:14 PM Krzysztof Kozlowski <krzk@kernel.org> wrote:
>>
>> On Fri, Nov 22, 2024 at 03:36:23PM +0530, Shubhrajyoti Datta wrote:
>>> Add device tree bindings for AMD Versal NET EDAC for DDR controller.
>>>
>>> Signed-off-by: Shubhrajyoti Datta <shubhrajyoti.datta@amd.com>
>>> ---
>>>
>>
> ..
>>> +
>>> + amd,dwidth:
>>> + description:
>>> + DDR memory controller device width.
>>
>> Use existing properties.
> I am not finding any existing properties could you help me with some pointers.
Really? `git grep width` gives plenty of choices, depending on the meaning.
I don't know what this property is about - your description is not
helping. Either obvious or not correct, because memory controller cannot
have a width. Like width in cm? inches?
>
>>
>>
>>> + enum: [16, 32]
>>> + $ref: /schemas/types.yaml#/definitions/uint32
>>> +
>>> + amd,num-chans:
>>> + description:
>>> + Number of channels.
>>
>> Use existing properties, e.g. some of the DDR schemas describing memory.
>> Look how other bindings describe actual chips.
>
> could you share any example. My search didnt return anything
I don't believe you tried to search then... There are like 5 bindings
describing some parts of memory bus to choose from. There are dedicated
bindings for DDR memory - it's all there. Look how other bindings
reference JEDEC DDR.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-12-23 14:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 10:06 [PATCH 0/3] EDAC: Versal NET: Add support for error notification Shubhrajyoti Datta
2024-11-22 10:06 ` [PATCH 1/3] dt-bindings: memory-controllers: Add support for Versal NET EDAC Shubhrajyoti Datta
2024-11-23 16:44 ` Krzysztof Kozlowski
2024-11-26 6:57 ` Datta, Shubhrajyoti
2024-11-26 7:07 ` Krzysztof Kozlowski
2024-12-23 9:58 ` Shubhrajyoti Datta
2024-12-23 14:02 ` Krzysztof Kozlowski [this message]
2024-11-22 10:06 ` [PATCH 2/3] cdx: add DDRMC commands Shubhrajyoti Datta
2024-11-22 10:06 ` [PATCH 3/3] EDAC: Versal NET: Add support for error notification Shubhrajyoti Datta
2024-11-23 16:49 ` Krzysztof Kozlowski
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=c4b58b22-804b-4175-abb8-ff8929c5821d@kernel.org \
--to=krzk@kernel.org \
--cc=bp@alien8.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=git@amd.com \
--cc=james.morse@arm.com \
--cc=krzk@kernel.or \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robh@kernel.org \
--cc=rric@kernel.org \
--cc=shubhrajyoti.datta@amd.com \
--cc=shubhrajyoti.datta@gmail.com \
--cc=tony.luck@intel.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).