From: Michael Walle <michael@walle.cc>
To: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: Li Yang <leoyang.li@nxp.com>, Michael Walle <michael@walle.cc>,
Shawn Guo <shawnguo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Marc Zyngier <maz@kernel.org>,
linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/4] dt-bindings: convert freescale extirq and scfg schemas
Date: Wed, 27 Apr 2022 09:53:34 +0200 [thread overview]
Message-ID: <20220427075338.1156449-1-michael@walle.cc> (raw)
The first two patches will be resend to the soc tree once the schema is
approved/picked up.
Please note, I'm still getting these weird "is too short" errors for
for interrupt-map entries, but it seems to work for you, so.. ;)
Michael Walle (4):
ARM: dts: ls1021a: reduce the interrupt-map-mask
arm64: dts: freescale: reduce the interrup-map-mask
dt-bindings: interrupt-controller: fsl,ls-extirq: convert to YAML
dt-bindings: fsl: convert fsl,layerscape-scfg to YAML
.../arm/freescale/fsl,layerscape-scfg.txt | 19 ---
.../interrupt-controller/fsl,ls-extirq.txt | 53 --------
.../interrupt-controller/fsl,ls-extirq.yaml | 118 ++++++++++++++++++
.../bindings/soc/fsl/fsl,layerscape-scfg.yaml | 58 +++++++++
arch/arm/boot/dts/ls1021a.dtsi | 2 +-
.../arm64/boot/dts/freescale/fsl-ls1043a.dtsi | 2 +-
.../arm64/boot/dts/freescale/fsl-ls1046a.dtsi | 2 +-
.../arm64/boot/dts/freescale/fsl-ls1088a.dtsi | 2 +-
.../arm64/boot/dts/freescale/fsl-ls208xa.dtsi | 2 +-
.../arm64/boot/dts/freescale/fsl-lx2160a.dtsi | 2 +-
10 files changed, 182 insertions(+), 78 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/arm/freescale/fsl,layerscape-scfg.txt
delete mode 100644 Documentation/devicetree/bindings/interrupt-controller/fsl,ls-extirq.txt
create mode 100644 Documentation/devicetree/bindings/interrupt-controller/fsl,ls-extirq.yaml
create mode 100644 Documentation/devicetree/bindings/soc/fsl/fsl,layerscape-scfg.yaml
--
2.30.2
next reply other threads:[~2022-04-27 7:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 7:53 Michael Walle [this message]
2022-04-27 7:53 ` [PATCH v3 1/4] ARM: dts: ls1021a: reduce the interrupt-map-mask Michael Walle
2022-05-05 3:56 ` Shawn Guo
2022-04-27 7:53 ` [PATCH v3 2/4] arm64: dts: freescale: reduce the interrup-map-mask Michael Walle
2022-05-05 3:56 ` Shawn Guo
2022-04-27 7:53 ` [PATCH v3 3/4] dt-bindings: interrupt-controller: fsl,ls-extirq: convert to YAML Michael Walle
2022-04-27 20:08 ` Leo Li
2022-04-28 6:16 ` Krzysztof Kozlowski
2022-04-28 7:10 ` Krzysztof Kozlowski
2022-04-28 22:46 ` Rob Herring
2022-04-27 7:53 ` [PATCH v3 4/4] dt-bindings: fsl: convert fsl,layerscape-scfg " Michael Walle
2022-04-27 14:18 ` Rob Herring
2022-04-28 22:47 ` 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=20220427075338.1156449-1-michael@walle.cc \
--to=michael@walle.cc \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maz@kernel.org \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
--cc=tglx@linutronix.de \
/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).