From: Lubomir Rintel <lkundrak@v3.sk> To: soc@kernel.org Cc: Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, Lubomir Rintel <lkundrak@v3.sk> Subject: [PATCH 1/4] ARM: dts: mmp3: Add a name to /clocks node Date: Thu, 31 Oct 2019 17:34:52 +0100 [thread overview] Message-ID: <20191031163455.1711872-2-lkundrak@v3.sk> (raw) In-Reply-To: <20191031163455.1711872-1-lkundrak@v3.sk> It should have one and DTC is indeed unhappy about its absence: <stdout>: Warning (unit_address_vs_reg): /soc/clocks: node has a reg or ranges property, but no unit name Signed-off-by: Lubomir Rintel <lkundrak@v3.sk> --- arch/arm/boot/dts/mmp3.dtsi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/boot/dts/mmp3.dtsi b/arch/arm/boot/dts/mmp3.dtsi index e0dcdab196355..b1e928ed77d66 100644 --- a/arch/arm/boot/dts/mmp3.dtsi +++ b/arch/arm/boot/dts/mmp3.dtsi @@ -486,7 +486,7 @@ cache-level = <2>; }; - soc_clocks: clocks { + soc_clocks: clocks@d4050000 { compatible = "marvell,mmp2-clock"; reg = <0xd4050000 0x1000>, <0xd4282800 0x400>, -- 2.23.0
WARNING: multiple messages have this Message-ID (diff)
From: Lubomir Rintel <lkundrak@v3.sk> To: soc@kernel.org Cc: Olof Johansson <olof@lixom.net>, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Arnd Bergmann <arnd@arndb.de>, Lubomir Rintel <lkundrak@v3.sk> Subject: [PATCH 1/4] ARM: dts: mmp3: Add a name to /clocks node Date: Thu, 31 Oct 2019 17:34:52 +0100 [thread overview] Message-ID: <20191031163455.1711872-2-lkundrak@v3.sk> (raw) In-Reply-To: <20191031163455.1711872-1-lkundrak@v3.sk> It should have one and DTC is indeed unhappy about its absence: <stdout>: Warning (unit_address_vs_reg): /soc/clocks: node has a reg or ranges property, but no unit name Signed-off-by: Lubomir Rintel <lkundrak@v3.sk> --- arch/arm/boot/dts/mmp3.dtsi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/boot/dts/mmp3.dtsi b/arch/arm/boot/dts/mmp3.dtsi index e0dcdab196355..b1e928ed77d66 100644 --- a/arch/arm/boot/dts/mmp3.dtsi +++ b/arch/arm/boot/dts/mmp3.dtsi @@ -486,7 +486,7 @@ cache-level = <2>; }; - soc_clocks: clocks { + soc_clocks: clocks@d4050000 { compatible = "marvell,mmp2-clock"; reg = <0xd4050000 0x1000>, <0xd4282800 0x400>, -- 2.23.0 _______________________________________________ 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:[~2019-10-31 16:41 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-10-31 16:34 [PATCH 1/4] ARM: dts: mmp3: A handful of fixes Lubomir Rintel 2019-10-31 16:34 ` Lubomir Rintel 2019-10-31 16:34 ` Lubomir Rintel [this message] 2019-10-31 16:34 ` [PATCH 1/4] ARM: dts: mmp3: Add a name to /clocks node Lubomir Rintel 2019-10-31 16:34 ` [PATCH 2/4] ARM: dts: mmp3: Fix /soc/watchdog node name Lubomir Rintel 2019-10-31 16:34 ` Lubomir Rintel 2019-10-31 16:34 ` [PATCH 3/4] ARM: dts: mmp3-dell-ariel: Add a name to /memory node Lubomir Rintel 2019-10-31 16:34 ` Lubomir Rintel 2019-10-31 16:34 ` [PATCH 4/4] ARM: dts: mmp3-dell-ariel: Add a serial point alias Lubomir Rintel 2019-10-31 16:34 ` Lubomir Rintel
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=20191031163455.1711872-2-lkundrak@v3.sk \ --to=lkundrak@v3.sk \ --cc=arnd@arndb.de \ --cc=devicetree@vger.kernel.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=olof@lixom.net \ --cc=soc@kernel.org \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.