From: Sameer Pujar <spujar@nvidia.com>
To: <robh+dt@kernel.org>, <devicetree@vger.kernel.org>
Cc: <thierry.reding@gmail.com>, <jonathanh@nvidia.com>,
<vkoul@kernel.org>, <tglx@linutronix.de>, <jason@lakedaemon.net>,
<maz@kernel.org>, <linux-tegra@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <dmaengine@vger.kernel.org>,
Sameer Pujar <spujar@nvidia.com>
Subject: [PATCH v2 0/4] Convert few Tegra docs to json-schema
Date: Fri, 6 Nov 2020 21:13:29 +0530 [thread overview]
Message-ID: <1604677413-20411-1-git-send-email-spujar@nvidia.com> (raw)
Following are the summary of changes.
* Update ADMA device node names for some of Tegra210 DT files.
* Convert ADMA, AGIC and ACONNECT docs to YAML.
Changelog
=========
v1 -> v2:
---------
* No change in DT patch.
* Add min/max items for interrupts and clocks in ADMA schema. Add
required 'additionalProperty' and thus fix errors/warnings in
the schema.
* Fix indentation warnings in arm,gic.yaml for AGIC documentation.
With this fix add "Reviewed-by" tag from Rob.
* Drop individual child pattern properties for ACONNECT schema and
instead use generic pattern property.
Sameer Pujar (4):
arm64: tegra: Rename ADMA device nodes for Tegra210
dt-bindings: dma: Convert ADMA doc to json-schema
dt-bindings: interrupt-controller: arm,gic: Update Tegra compatibles
dt-bindings: bus: Convert ACONNECT doc to json-schema
.../bindings/bus/nvidia,tegra210-aconnect.txt | 44 ----------
.../bindings/bus/nvidia,tegra210-aconnect.yaml | 82 ++++++++++++++++++
.../bindings/dma/nvidia,tegra210-adma.txt | 56 ------------
.../bindings/dma/nvidia,tegra210-adma.yaml | 99 ++++++++++++++++++++++
.../bindings/interrupt-controller/arm,gic.yaml | 9 +-
arch/arm64/boot/dts/nvidia/tegra210-p2371-2180.dts | 2 +-
arch/arm64/boot/dts/nvidia/tegra210-p3450-0000.dts | 2 +-
arch/arm64/boot/dts/nvidia/tegra210-smaug.dts | 2 +-
arch/arm64/boot/dts/nvidia/tegra210.dtsi | 2 +-
9 files changed, 193 insertions(+), 105 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/bus/nvidia,tegra210-aconnect.txt
create mode 100644 Documentation/devicetree/bindings/bus/nvidia,tegra210-aconnect.yaml
delete mode 100644 Documentation/devicetree/bindings/dma/nvidia,tegra210-adma.txt
create mode 100644 Documentation/devicetree/bindings/dma/nvidia,tegra210-adma.yaml
--
2.7.4
next reply other threads:[~2020-11-06 15:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 15:43 Sameer Pujar [this message]
2020-11-06 15:43 ` [PATCH v2 1/4] arm64: tegra: Rename ADMA device nodes for Tegra210 Sameer Pujar
2020-11-10 19:44 ` Thierry Reding
2020-11-06 15:43 ` [PATCH v2 2/4] dt-bindings: dma: Convert ADMA doc to json-schema Sameer Pujar
2020-11-09 21:45 ` Rob Herring
2020-11-10 19:46 ` Thierry Reding
2020-11-06 15:43 ` [PATCH v2 3/4] dt-bindings: interrupt-controller: arm,gic: Update Tegra compatibles Sameer Pujar
2020-11-06 15:43 ` [PATCH v2 4/4] dt-bindings: bus: Convert ACONNECT doc to json-schema Sameer Pujar
2020-11-09 21:45 ` Rob Herring
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=1604677413-20411-1-git-send-email-spujar@nvidia.com \
--to=spujar@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=jason@lakedaemon.net \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=maz@kernel.org \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
--cc=thierry.reding@gmail.com \
--cc=vkoul@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).