From: Aswath Govindraju <a-govindraju@ti.com>
Cc: "Lokesh Vutla" <lokeshvutla@ti.com>,
"Vignesh Raghavendra" <vigneshr@ti.com>,
"Kishon Vijay Abraham I" <kishon@ti.com>,
"Grygorii Strashko" <grygorii.strashko@ti.com>,
"Aswath Govindraju" <a-govindraju@ti.com>,
"Mark Brown" <broonie@kernel.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Benoît Cousson" <bcousson@baylibre.com>,
"Tony Lindgren" <tony@atomide.com>, "Nishanth Menon" <nm@ti.com>,
"Tero Kristo" <kristo@kernel.org>,
linux-spi@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/5] dt-bindings: spi: omap-spi: Convert to json-schema
Date: Wed, 2 Jun 2021 18:04:10 +0530 [thread overview]
Message-ID: <20210602123416.20378-1-a-govindraju@ti.com> (raw)
Convert the omap-spi device tree binding documentation to json-schema.
The property ti,pindir-d0-out-d1-in is expected to be of type boolean.
All ti,pindir-d0-out-d1-in occurences are fixed before changing the
binding to avoid dtbs_check warnings.
Aswath Govindraju (5):
ARM: dts: am335x: align ti,pindir-d0-out-d1-in property with dt-shema
ARM: dts: am437x: align ti,pindir-d0-out-d1-in property with dt-shema
arm64: dts: ti: am65: align ti,pindir-d0-out-d1-in property with
dt-shema
arm64: dts: ti: k3-am642-evm: align ti,pindir-d0-out-d1-in property
with dt-shema
dt-bindings: spi: omap-spi: Convert to json-schema
.../devicetree/bindings/spi/omap-spi.txt | 48 -------
.../devicetree/bindings/spi/omap-spi.yaml | 126 ++++++++++++++++++
arch/arm/boot/dts/am335x-cm-t335.dts | 2 +-
arch/arm/boot/dts/am43x-epos-evm.dts | 4 +-
arch/arm64/boot/dts/ti/k3-am642-evm.dts | 2 +-
.../boot/dts/ti/k3-am65-iot2050-common.dtsi | 2 +-
.../arm64/boot/dts/ti/k3-am654-base-board.dts | 2 +-
7 files changed, 132 insertions(+), 54 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/spi/omap-spi.txt
create mode 100644 Documentation/devicetree/bindings/spi/omap-spi.yaml
--
2.17.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-06-02 12:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 12:34 Aswath Govindraju [this message]
2021-06-02 12:34 ` [PATCH 1/5] ARM: dts: am335x: align ti, pindir-d0-out-d1-in property with dt-shema Aswath Govindraju
2021-06-02 12:34 ` [PATCH 2/5] ARM: dts: am437x: " Aswath Govindraju
2021-06-02 12:34 ` [PATCH 3/5] arm64: dts: ti: am65: " Aswath Govindraju
2021-06-07 13:40 ` [PATCH 3/5] arm64: dts: ti: am65: align ti,pindir-d0-out-d1-in " Nishanth Menon
2021-06-07 13:48 ` Aswath Govindraju
2021-06-07 20:24 ` Nishanth Menon
2021-06-02 12:34 ` [PATCH 4/5] arm64: dts: ti: k3-am642-evm: align ti, pindir-d0-out-d1-in " Aswath Govindraju
2021-06-02 12:34 ` [PATCH 5/5] dt-bindings: spi: omap-spi: Convert to json-schema Aswath Govindraju
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=20210602123416.20378-1-a-govindraju@ti.com \
--to=a-govindraju@ti.com \
--cc=bcousson@baylibre.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=grygorii.strashko@ti.com \
--cc=kishon@ti.com \
--cc=kristo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=tony@atomide.com \
--cc=vigneshr@ti.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).