From: Rob Herring <robh@kernel.org>
To: Andre Przywara <andre.przywara@arm.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Linus Walleij <linus.walleij@linaro.org>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/5] Arm VExpress/Juno motherboard bus clean-ups
Date: Thu, 19 Aug 2021 13:42:34 -0500 [thread overview]
Message-ID: <20210819184239.1192395-1-robh@kernel.org> (raw)
I noticed we once again have warnings on VExpress/Juno bus nodes as the
simple-bus schema now expects child nodes to have a unit-address.
Digging into this I noticed the arm,vexpress-juno.yaml schema is out of
date and missing some properties (some of which are unused). I found the
'ranges' handling to be odd as well. This series fixes all those issues.
Rob
Rob Herring (5):
dt-bindings: arm,vexpress-juno: Fix 'motherboard' node name
dt-bindings: arm,vexpress-juno: Add missing motherboard properties
arm: dts: vexpress: Drop unused properties from motherboard node
arm: dts: vexpress-v2p-ca9: Fix the SMB unit-address
arm: dts: vexpress: Fix addressing issues with 'motherboard-bus' nodes
.../bindings/arm/arm,vexpress-juno.yaml | 46 +++++++++++--------
arch/arm/boot/dts/vexpress-v2m-rs1.dtsi | 17 +++++--
arch/arm/boot/dts/vexpress-v2m.dtsi | 18 ++++++--
arch/arm/boot/dts/vexpress-v2p-ca15-tc1.dts | 11 -----
arch/arm/boot/dts/vexpress-v2p-ca15_a7.dts | 11 -----
arch/arm/boot/dts/vexpress-v2p-ca5s.dts | 11 -----
arch/arm/boot/dts/vexpress-v2p-ca9.dts | 12 +----
arch/arm64/boot/dts/arm/foundation-v8.dtsi | 1 -
arch/arm64/boot/dts/arm/fvp-base-revc.dts | 11 -----
arch/arm64/boot/dts/arm/juno-base.dtsi | 10 ----
arch/arm64/boot/dts/arm/juno-motherboard.dtsi | 17 +++++--
arch/arm64/boot/dts/arm/rtsm_ve-aemv8a.dts | 11 -----
.../boot/dts/arm/rtsm_ve-motherboard-rs2.dtsi | 2 +-
.../boot/dts/arm/rtsm_ve-motherboard.dtsi | 16 +++++--
.../boot/dts/arm/vexpress-v2f-1xv7-ca53x2.dts | 11 -----
15 files changed, 78 insertions(+), 127 deletions(-)
--
2.30.2
_______________________________________________
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-08-19 18:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 18:42 Rob Herring [this message]
2021-08-19 18:42 ` [PATCH 1/5] dt-bindings: arm, vexpress-juno: Fix 'motherboard' node name Rob Herring
2021-08-19 18:42 ` [PATCH 2/5] dt-bindings: arm, vexpress-juno: Add missing motherboard properties Rob Herring
2021-08-19 18:42 ` [PATCH 3/5] arm: dts: vexpress: Drop unused properties from motherboard node Rob Herring
2021-08-19 18:42 ` [PATCH 4/5] arm: dts: vexpress-v2p-ca9: Fix the SMB unit-address Rob Herring
2021-08-19 18:42 ` [PATCH 5/5] arm: dts: vexpress: Fix addressing issues with 'motherboard-bus' nodes Rob Herring
2021-08-19 23:25 ` [PATCH 0/5] Arm VExpress/Juno motherboard bus clean-ups Linus Walleij
2021-09-13 17:21 ` Sudeep Holla
2021-09-16 9:03 ` Sudeep Holla
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=20210819184239.1192395-1-robh@kernel.org \
--to=robh@kernel.org \
--cc=andre.przywara@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=sudeep.holla@arm.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).