From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lee Jones Subject: Re: [PATCH v4 6/6] ARM: dts: STiH407: Add B2120 board support Date: Wed, 21 May 2014 11:02:45 +0100 Message-ID: <20140521100245.GI6679@lee--X1> References: <1394614210-15698-1-git-send-email-maxime.coquelin@st.com> <1394614210-15698-7-git-send-email-maxime.coquelin@st.com> <20140520072048.GC20874@lee--X1> <20140520074353.GD20874@lee--X1> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-doc-owner@vger.kernel.org To: Olof Johansson Cc: Maxime COQUELIN , Rob Landley , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Russell King , Srinivas Kandagatla , Stuart Menefy , Linus Walleij , Giuseppe Cavallaro , "linux-doc@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "devicetree@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "kernel@stlinux.com" List-Id: devicetree@vger.kernel.org > >> >> > + soc { > >> >> > + sbc_serial0: serial@9530000 { > >> >> > + status =3D "okay"; > >> >> > + }; > >> >> > >> >> You might want to consider reference-based syntax here instead,= so you > >> >> don't have to mimic the hierarchy. That'd be (at the root level= of the > >> >> file, below this secion: > >> >> > >> >> &sbc_serial0: { > >> >> status =3D "okay"; > >> >> }; > >> > > >> > I'm personally not keen on this scheme. It's sometimes helpful = to know > >> > the hierarchy and I don't think it's a large overhead to format = the > >> > subordinate DTS files in this way. > >> > > >> > Please consider not enforcing this. > >> > >> Definitely not enforcing it, and I didn't use to like it either bu= t it > >> has some real upsides. > >> > >> In particular, it saves a lot of grief when you're changing someth= ing > >> like the unit-id of a node in .dtsi and forget to do the same upda= te > >> in the dts. > > > > I'm not entirely sure what a unit-id is, but I can see that there > > would be benefits to using the referenced-based syntax as you call > > it. If any of those benefits hold true here I won't push back, but= I > > would personally like to see us default to the hierarchical scheme. >=20 > Sorry, I meant unit-address. I.e. the portion that goes behind the @ > in the node name. Ah yes, makes sense now, thanks. --=20 Lee Jones Linaro STMicroelectronics Landing Team Lead Linaro.org =E2=94=82 Open source software for ARM SoCs =46ollow Linaro: Facebook | Twitter | Blog