linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: manabian@gmail.com (Joachim Eastwood)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/7] ARM: dts: lpc18xx: remove unit addresses from creg childs
Date: Wed, 30 Mar 2016 00:30:42 +0200	[thread overview]
Message-ID: <1459290646-3592-4-git-send-email-manabian@gmail.com> (raw)
In-Reply-To: <1459290646-3592-1-git-send-email-manabian@gmail.com>

DT nodes without reg properties should not have a unit address. This
fixes the following warnings from dtc.

 Warning (unit_address_vs_reg): Node /soc/syscon at 40043000/phy at 004 has a
 unit name, but no reg property
 Warning (unit_address_vs_reg): Node /soc/syscon at 40043000/dma-mux at 11c has
 a unit name, but no reg property

Signed-off-by: Joachim Eastwood <manabian@gmail.com>
---
 arch/arm/boot/dts/lpc18xx.dtsi | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/arm/boot/dts/lpc18xx.dtsi b/arch/arm/boot/dts/lpc18xx.dtsi
index fdc991b..fdb736c 100644
--- a/arch/arm/boot/dts/lpc18xx.dtsi
+++ b/arch/arm/boot/dts/lpc18xx.dtsi
@@ -201,13 +201,13 @@
 				#clock-cells = <1>;
 			};
 
-			usb0_otg_phy: phy at 004 {
+			usb0_otg_phy: phy {
 				compatible = "nxp,lpc1850-usb-otg-phy";
 				clocks = <&ccu1 CLK_USB0>;
 				#phy-cells = <0>;
 			};
 
-			dmamux: dma-mux at 11c {
+			dmamux: dma-mux {
 				compatible = "nxp,lpc1850-dmamux";
 				#dma-cells = <3>;
 				dma-requests = <64>;
-- 
2.7.4

  parent reply	other threads:[~2016-03-29 22:30 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-29 22:30 [PATCH 0/7] fix unit name warnings on lpc18xx Joachim Eastwood
2016-03-29 22:30 ` [PATCH 1/7] ARM: dts: armv7-m: add unit name to interrupt-controller Joachim Eastwood
2016-04-04  6:05   ` Uwe Kleine-König
2016-04-04  6:42     ` Joachim Eastwood
2016-04-04  6:51       ` Stefan Agner
2016-04-04  7:30       ` Uwe Kleine-König
2016-03-29 22:30 ` [PATCH 2/7] ARM: dts: skeleton: add unit name to memory node Joachim Eastwood
2016-03-30 10:12   ` Vladimir Zapolskiy
2016-03-30 11:06   ` Mark Rutland
2016-03-30 12:36     ` Joachim Eastwood
2016-03-30 13:06     ` Vladimir Zapolskiy
2016-03-30 13:41       ` Mark Rutland
2016-03-30 16:15         ` Joachim Eastwood
2016-03-30 17:06           ` Mark Rutland
2016-03-30 20:45             ` Joachim Eastwood
2016-03-31 10:38               ` Mark Rutland
2016-03-31 15:21                 ` Joachim Eastwood
2016-03-31 16:34                   ` Joachim Eastwood
2016-04-12 22:45                     ` Rob Herring
2016-04-12 23:03                       ` Joachim Eastwood
2016-03-31 16:27           ` Rob Herring
2016-03-31 16:31             ` Rob Herring
2016-03-31 16:33               ` Joachim Eastwood
2016-03-29 22:30 ` Joachim Eastwood [this message]
2016-03-29 22:30 ` [PATCH 4/7] ARM: dts: lpc4357-ea4357: fix unit name warnings from dtc Joachim Eastwood
2016-03-29 22:30 ` [PATCH 5/7] ARM: dts: lpc4350-hitex-eval: " Joachim Eastwood
2016-03-29 22:30 ` [PATCH 6/7] ARM: dts: lpc4337-ciaa:: fix unit name warning " Joachim Eastwood
2016-03-29 22:30 ` [PATCH 7/7] dt-bindings: phy-lpc18xx-usb-otg: remove unit address from binding Joachim Eastwood

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=1459290646-3592-4-git-send-email-manabian@gmail.com \
    --to=manabian@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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: 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).