From: Dmitry Osipenko <digetx@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@canonical.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 v2 2/4] dt-bindings: memory: tegra20: emc: Document new LPDDR2 sub-node
Date: Sun, 3 Oct 2021 04:28:33 +0300 [thread overview]
Message-ID: <9290fdda-65f4-70c3-fd1f-2872824795d6@gmail.com> (raw)
In-Reply-To: <20211003003509.28241-3-digetx@gmail.com>
03.10.2021 03:35, Dmitry Osipenko пишет:
> + lpddr2-configuration:
> + $ref: "jedec,lpddr2.yaml#"
> + type: object
...
> +
> + lpddr2-config {
> + jedec,lpddr2-manufacturer-id = <LPDDR2_MANID_ELPIDA>;
> + jedec,lpddr2-revision-id1 = <1>;
> + jedec,lpddr2-density-mbits = <2048>;
> + jedec,lpddr2-io-width-bits = <16>;
> + jedec,lpddr2-type = <LPDDR2_TYPE_S4>;
> + };
I just noticed that this is a wrong node name and I missed to run
dt_binding_check after the last edit. I'll send v3 with the corrected
name shortly.
next prev parent reply other threads:[~2021-10-03 1:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-03 0:35 [PATCH v2 0/4] tegra20-emc: Identify memory chip by LPDDR configuration Dmitry Osipenko
2021-10-03 0:35 ` [PATCH v2 1/4] dt-bindings: memory: Add LPDDR2 binding Dmitry Osipenko
2021-10-03 0:35 ` [PATCH v2 2/4] dt-bindings: memory: tegra20: emc: Document new LPDDR2 sub-node Dmitry Osipenko
2021-10-03 1:28 ` Dmitry Osipenko [this message]
2021-10-03 0:35 ` [PATCH v2 3/4] memory: Add LPDDR2 configuration helpers Dmitry Osipenko
2021-10-03 0:35 ` [PATCH v2 4/4] memory: tegra20-emc: Support matching timings by LPDDR2 configuration 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=9290fdda-65f4-70c3-fd1f-2872824795d6@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;
as well as URLs for NNTP newsgroup(s).