From: Dmitry Osipenko <digetx@gmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH v3 2/4] dt-bindings: memory: tegra20: emc: Document new LPDDR2 sub-node
Date: Mon, 4 Oct 2021 19:56:41 +0300 [thread overview]
Message-ID: <184e4ce9-7beb-19ff-1562-453603eb7cce@gmail.com> (raw)
In-Reply-To: <a3713f62-0ece-5ab2-f55a-3d614ce01c00@canonical.com>
04.10.2021 11:37, Krzysztof Kozlowski пишет:
> On 03/10/2021 03:32, Dmitry Osipenko wrote:
>> Some Tegra20 boards don't have RAM code stored in NVMEM, which is used for
>> the memory chip identification and the identity information should be read
>> out from LPDDR2 chip in this case. Document new sub-node containing generic
>> LPDDR2 properties that will be used for the memory chip identification if
>> RAM code isn't available. The identification is done by reading out memory
>> configuration values from generic LPDDR2 mode registers of SDRAM chip and
>> comparing them with the values of device-tree sub-node's.
>>
>> Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
>> ---
>> .../memory-controllers/nvidia,tegra20-emc.yaml | 17 ++++++++++++++---
>> 1 file changed, 14 insertions(+), 3 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/memory-controllers/nvidia,tegra20-emc.yaml b/Documentation/devicetree/bindings/memory-controllers/nvidia,tegra20-emc.yaml
>> index cac6842dc8f1..65f7c3898ac4 100644
>> --- a/Documentation/devicetree/bindings/memory-controllers/nvidia,tegra20-emc.yaml
>> +++ b/Documentation/devicetree/bindings/memory-controllers/nvidia,tegra20-emc.yaml
>> @@ -164,13 +164,14 @@ patternProperties:
>> "#size-cells":
>> const: 0
>>
>> + lpddr2-configuration:
>
> Nodes should be named generic, so just lpddr2?
Yes
>> + $ref: "jedec,lpddr2.yaml#"
>> + type: object
>> +
>> patternProperties:
>> "^emc-table@[0-9]+$":
>> $ref: "#/$defs/emc-table"
>>
>> - required:
>> - - nvidia,ram-code
>
> Isn't lpddr2-configuration required in such case? If not, probably you
> want either this or that (oneOf like in reserved-memory.yaml).
Thanks, oneOf will work.
next prev parent reply other threads:[~2021-10-04 16:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-03 1:32 [PATCH v3 0/4] tegra20-emc: Identify memory chip by LPDDR configuration Dmitry Osipenko
2021-10-03 1:32 ` [PATCH v3 1/4] dt-bindings: memory: Add LPDDR2 binding Dmitry Osipenko
2021-10-04 7:42 ` Krzysztof Kozlowski
2021-10-04 16:53 ` Dmitry Osipenko
2021-10-03 1:32 ` [PATCH v3 2/4] dt-bindings: memory: tegra20: emc: Document new LPDDR2 sub-node Dmitry Osipenko
2021-10-04 8:37 ` Krzysztof Kozlowski
2021-10-04 16:56 ` Dmitry Osipenko [this message]
2021-10-03 1:32 ` [PATCH v3 3/4] memory: Add LPDDR2 configuration helpers Dmitry Osipenko
2021-10-04 8:53 ` Krzysztof Kozlowski
2021-10-03 1:32 ` [PATCH v3 4/4] memory: tegra20-emc: Support matching timings by LPDDR2 configuration Dmitry Osipenko
2021-10-04 9:09 ` Krzysztof Kozlowski
2021-10-04 17:05 ` Dmitry Osipenko
2021-10-05 15:51 ` Dmitry Osipenko
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=184e4ce9-7beb-19ff-1562-453603eb7cce@gmail.com \
--to=digetx@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.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