From: Krzysztof Kozlowski <krzk@kernel.org>
To: Wei Xu <xuwei5@hisilicon.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Krzysztof Kozlowski <krzk@kernel.org>
Subject: [PATCH 1/9] arm64: dts: hisilicon: hip05: move non-MMIO node out of soc
Date: Tue, 2 Apr 2024 21:31:40 +0200 [thread overview]
Message-ID: <20240402193148.62323-1-krzk@kernel.org> (raw)
Non-MMIO devices, which are BTW not really part of the SoC, should not
be within simple-bus, as reported by dtc W=1 warning:
hip05.dtsi:301.30-305.5: Warning (simple_bus_reg): /soc/refclk200mhz: missing or empty reg/ranges property
Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
---
arch/arm64/boot/dts/hisilicon/hip05.dtsi | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/arch/arm64/boot/dts/hisilicon/hip05.dtsi b/arch/arm64/boot/dts/hisilicon/hip05.dtsi
index 65ddc0698f82..d0912ca5f237 100644
--- a/arch/arm64/boot/dts/hisilicon/hip05.dtsi
+++ b/arch/arm64/boot/dts/hisilicon/hip05.dtsi
@@ -279,6 +279,12 @@ its_dsa: msi-controller@c6000000 {
};
};
+ refclk200mhz: refclk200mhz {
+ compatible = "fixed-clock";
+ #clock-cells = <0>;
+ clock-frequency = <200000000>;
+ };
+
timer {
compatible = "arm,armv8-timer";
interrupts = <GIC_PPI 13 IRQ_TYPE_LEVEL_LOW>,
@@ -298,12 +304,6 @@ soc {
#size-cells = <2>;
ranges;
- refclk200mhz: refclk200mhz {
- compatible = "fixed-clock";
- #clock-cells = <0>;
- clock-frequency = <200000000>;
- };
-
uart0: serial@80300000 {
compatible = "snps,dw-apb-uart";
reg = <0x0 0x80300000 0x0 0x10000>;
--
2.34.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:[~2024-04-02 19:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 19:31 Krzysztof Kozlowski [this message]
2024-04-02 19:31 ` [PATCH 2/9] arm64: dts: hisilicon: hip05-d02: correct local-bus unit addresses Krzysztof Kozlowski
2024-04-02 19:31 ` [PATCH 3/9] arm64: dts: hisilicon: hip06: move non-MMIO node out of soc Krzysztof Kozlowski
2024-04-02 19:31 ` [PATCH 4/9] arm64: dts: hisilicon: hip06: correct unit addresses Krzysztof Kozlowski
2024-04-02 19:31 ` [PATCH 5/9] arm64: dts: hisilicon: hip07: move non-MMIO node out of soc Krzysztof Kozlowski
2024-04-02 19:31 ` [PATCH 6/9] arm64: dts: hisilicon: hip07: correct unit addresses Krzysztof Kozlowski
2024-04-02 19:31 ` [PATCH 7/9] arm64: dts: hisilicon: hi6220-hikey: add missing port@0 reg Krzysztof Kozlowski
2024-04-02 19:31 ` [PATCH 8/9] arm64: dts: hisilicon: hi6220-hikey: drop unit addresses from fixed regulators Krzysztof Kozlowski
2024-04-02 19:31 ` [PATCH 9/9] arm64: dts: hisilicon: hi6220: correct tsensor unit addresses Krzysztof Kozlowski
2024-04-24 6:54 ` [PATCH 1/9] arm64: dts: hisilicon: hip05: move non-MMIO node out of soc Krzysztof Kozlowski
2024-04-24 7:16 ` Wei Xu
2024-04-24 7:23 ` Krzysztof Kozlowski
2024-04-24 8:37 ` Krzysztof Kozlowski
2024-04-24 9:16 ` Wei Xu
2024-04-25 11:12 ` Wei Xu
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=20240402193148.62323-1-krzk@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--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=robh@kernel.org \
--cc=xuwei5@hisilicon.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).