From: Andrew Davis <afd@ti.com>
To: Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Andrew Davis <afd@ti.com>
Subject: [PATCH 4/5] ARM: dts: keystone: Remove ti,keystone from soc node compatible
Date: Mon, 15 May 2023 13:35:14 -0500 [thread overview]
Message-ID: <20230515183515.509371-4-afd@ti.com> (raw)
In-Reply-To: <20230515183515.509371-1-afd@ti.com>
This is just a "simple-bus" node, there is no need for the extra
compatible "ti,keystone" which is unused and undocumented.
Signed-off-by: Andrew Davis <afd@ti.com>
---
arch/arm/boot/dts/keystone.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/keystone.dtsi b/arch/arm/boot/dts/keystone.dtsi
index 50789f9e2215..552ecd546cfd 100644
--- a/arch/arm/boot/dts/keystone.dtsi
+++ b/arch/arm/boot/dts/keystone.dtsi
@@ -69,9 +69,9 @@ psci {
};
soc0: soc@0 {
+ compatible = "simple-bus";
#address-cells = <1>;
#size-cells = <1>;
- compatible = "ti,keystone","simple-bus";
interrupt-parent = <&gic>;
ranges = <0x0 0x0 0x0 0xc0000000>;
dma-ranges = <0x80000000 0x8 0x00000000 0x80000000>;
--
2.39.2
next prev parent reply other threads:[~2023-05-15 18:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 18:35 [PATCH 1/5] ARM: keystone: Merge memory.h into the only file that uses it Andrew Davis
2023-05-15 18:35 ` [PATCH 2/5] ARM: keystone: Merge PM function into main support file Andrew Davis
2023-05-16 21:33 ` kernel test robot
2023-05-15 18:35 ` [PATCH 3/5] ARM: dts: keystone: Fix EEPROM node names Andrew Davis
2023-05-15 18:35 ` Andrew Davis [this message]
2023-05-15 18:35 ` [PATCH 5/5] ARM: dts: keystone: Do not capitalize hex digits Andrew Davis
2023-06-07 18:20 ` (subset) [PATCH 1/5] ARM: keystone: Merge memory.h into the only file that uses it Nishanth Menon
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=20230515183515.509371-4-afd@ti.com \
--to=afd@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=ssantosh@kernel.org \
--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).