From: Julius Werner <jwerner@chromium.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Cc: Dmitry Osipenko <digetx@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Julius Werner <jwerner@chromium.org>
Subject: [PATCH 0/3] Update lpddr2 revision-id binding to match lpddr3
Date: Wed, 23 Feb 2022 16:34:18 -0800 [thread overview]
Message-ID: <20220224003421.3440124-1-jwerner@chromium.org> (raw)
This patch series updates the device tree binding for "jedec,lpddr2" to
encode the revision ID (mode registers 6 and 7) in the same way as they
were already done for the "jedec,lpddr3" binding, and deprecates the old
way.
Julius Werner (3):
dt-bindings: memory: lpddr2: Adjust revision ID property to match
lpddr3
memory: Update of_memory lpddr2 revision-id binding
ARM: dts: Update jedec,lpddr2 revision-id binding
.../memory-controllers/ddr/jedec,lpddr2.yaml | 17 ++++++++++++--
arch/arm/boot/dts/tegra20-asus-tf101.dts | 2 +-
drivers/memory/of_memory.c | 23 ++++++++++++-------
3 files changed, 31 insertions(+), 11 deletions(-)
--
2.31.0
next reply other threads:[~2022-02-24 0:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 0:34 Julius Werner [this message]
2022-02-24 0:34 ` [PATCH v3 1/3] dt-bindings: memory: lpddr2: Adjust revision ID property to match lpddr3 Julius Werner
2022-02-24 20:24 ` Rob Herring
2022-02-25 12:35 ` Krzysztof Kozlowski
2022-02-24 0:34 ` [PATCH 2/3] memory: Update of_memory lpddr2 revision-id binding Julius Werner
2022-02-24 0:34 ` [PATCH 3/3] ARM: dts: Update jedec,lpddr2 " Julius Werner
2022-02-24 7:29 ` Krzysztof Kozlowski
2022-02-24 12:38 ` Thierry Reding
2022-02-25 1:41 ` Julius Werner
2022-02-25 7:08 ` Krzysztof Kozlowski
2022-02-25 12:37 ` [PATCH 0/3] Update lpddr2 revision-id binding to match lpddr3 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=20220224003421.3440124-1-jwerner@chromium.org \
--to=jwerner@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=digetx@gmail.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-kernel@vger.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).