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: [PATCH v3 0/1] NVIDIA Tegra memory improvements
Date: Sun, 4 Apr 2021 18:55:00 +0300 [thread overview]
Message-ID: <20210404155501.5066-1-digetx@gmail.com> (raw)
Hi,
Here is the last patch of the series which had minor problem in v2,
the rest of the patches are already applied by Krzysztof Kozlowski.
Changelog:
v3: - Added new optional reg property for emc-tables nodes in order to
fix dt_binding_check warning.
Please note that I will prepare a separate patch for v5.14 that will
add the new property to the device-trees since Thierry already
sent out PR for v5.13.
v2: - Fixed typos in the converted schemas.
- Corrected reg entry of tegra20-mc-gart schema to use fixed number of items.
- Made power-domain to use maxItems instead of $ref phandle in schemas.
Dmitry Osipenko (1):
dt-bindings: memory: tegra20: emc: Convert to schema
.../memory-controllers/nvidia,tegra20-emc.txt | 130 --------
.../nvidia,tegra20-emc.yaml | 303 ++++++++++++++++++
2 files changed, 303 insertions(+), 130 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/memory-controllers/nvidia,tegra20-emc.txt
create mode 100644 Documentation/devicetree/bindings/memory-controllers/nvidia,tegra20-emc.yaml
--
2.30.2
next reply other threads:[~2021-04-04 15:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-04 15:55 Dmitry Osipenko [this message]
2021-04-04 15:55 ` [PATCH v3 1/1] dt-bindings: memory: tegra20: emc: Convert to schema Dmitry Osipenko
2021-04-08 20:29 ` Rob Herring
2021-04-09 0:16 ` 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=20210404155501.5066-1-digetx@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).