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 2/9] arm64: dts: hisilicon: hip05-d02: correct local-bus unit addresses
Date: Tue, 2 Apr 2024 21:31:41 +0200 [thread overview]
Message-ID: <20240402193148.62323-2-krzk@kernel.org> (raw)
In-Reply-To: <20240402193148.62323-1-krzk@kernel.org>
Correct local-bus children unit addresses to fix dtc W=1 warnings:
hip05-d02.dts:57.16-76.4: Warning (simple_bus_reg): /soc/local-bus@80380000/nor-flash@0,0: simple-bus unit address format error, expected "0"
hip05-d02.dts:78.11-81.4: Warning (simple_bus_reg): /soc/local-bus@80380000/cpld@1,0: simple-bus unit address format error, expected "100000000"
Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
---
arch/arm64/boot/dts/hisilicon/hip05-d02.dts | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm64/boot/dts/hisilicon/hip05-d02.dts b/arch/arm64/boot/dts/hisilicon/hip05-d02.dts
index c4eaebbb448f..b7792d443189 100644
--- a/arch/arm64/boot/dts/hisilicon/hip05-d02.dts
+++ b/arch/arm64/boot/dts/hisilicon/hip05-d02.dts
@@ -54,7 +54,7 @@ &lbc {
ranges = <0 0 0x0 0x90000000 0x08000000>,
<1 0 0x0 0x98000000 0x08000000>;
- nor-flash@0,0 {
+ nor-flash@0 {
#address-cells = <1>;
#size-cells = <1>;
compatible = "numonyx,js28f00a", "cfi-flash";
@@ -75,7 +75,7 @@ partition@1000000 {
};
};
- cpld@1,0 {
+ cpld@100000000 {
compatible = "hisilicon,hip05-cpld";
reg = <1 0x0 0x100>;
};
--
2.34.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent 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 [PATCH 1/9] arm64: dts: hisilicon: hip05: move non-MMIO node out of soc Krzysztof Kozlowski
2024-04-02 19:31 ` Krzysztof Kozlowski [this message]
2024-04-02 19:31 ` [PATCH 3/9] arm64: dts: hisilicon: hip06: " 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-2-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).