From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/6] ARM: sunxi: DT: Convert to device tree includes
Date: Wed, 17 Dec 2014 22:33:58 +0100 [thread overview]
Message-ID: <20141217213358.GR4337@lukather> (raw)
In-Reply-To: <2559984.DiBeGaGfHy@wuerfel>
Hi Arnd,
On Wed, Dec 17, 2014 at 08:32:01AM +0100, Arnd Bergmann wrote:
> On Tuesday 16 December 2014 22:59:54 Maxime Ripard wrote:
> > Prepare the device trees to use the C preprocessor.
> >
> > Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>
>
> Hi Maxime,
>
> Since you are doing a number of changes to all the sunxi files, I have
> one more request for something that has been bugging me a while:
>
> In your .dtsi files, you define devices like this:
>
> uart0: serial at 01c28000 {
> compatible = "snps,dw-apb-uart";
> reg = <0x01c28000 0x400>;
> interrupts = <0 1 4>;
> reg-shift = <2>;
> reg-io-width = <4>;
> clocks = <&apb1_gates 16>;
> status = "disabled";
> };
>
> and in the .dts files, you extend them like this:
>
> uart0: serial at 01c28000 {
> pinctrl-names = "default";
> pinctrl-0 = <&uart0_pins_a>;
> status = "okay";
> };
>
>
> which duplicates both the node names with their full path, and
> the labels. Please use one or the other, but not both. I don't mind
> you having the full path to each device in the dts files, just drop
> all the labels in that case.
I don't know, maybe it's just a matter of personnal taste, but I do
find convenient to have the labels in the DTS as well, so that
whenever you need to use a label (for a phandle for example), you
don't have to lookup in the DTSI if you have the node in the DTS.
> Most other maintainers these days just use the labels like this in
> the dts files however:
>
> &uart0 {
> status = "okay";
> };
>
> which also seems completely fine.
If that's the current trend, I'll add that to my todo-list, but I
believe it's orthogonal to these patches.
> I'm also a bit puzzled by all the pinctrl references you add in the .dts
> files, but it's possible I'm missing something there. Why can't you move
> these to the .dtsi files and avoid duplicating the pinctrl-0 and
> pinctrl-names properties for every .dts file? I would assume that they
> are not referenced for disabled devices.
The pinctrl nodes we reference are in the DTS. However, each pin of
each controller is most of the time available on several pins of the
package, so we don't have any way to enforce a default at the SoC
level.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20141217/064f02c7/attachment-0001.sig>
next prev parent reply other threads:[~2014-12-17 21:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-16 21:59 [PATCH 1/6] ARM: sunxi: DT: Convert to device tree includes Maxime Ripard
2014-12-16 21:59 ` [PATCH 2/6] ARM: sunxi: DT: convert DTs to use common GPIOs includes Maxime Ripard
2014-12-16 21:59 ` [PATCH 3/6] ARM: sunxi: DT: Convert the DTs to use a header for the DMA arguments Maxime Ripard
2014-12-16 21:59 ` [PATCH 4/6] ARM: sunxi: DT: Convert the DTs to use a header for the pinctrl nodes Maxime Ripard
2015-01-05 7:41 ` Olliver Schinagl
2014-12-16 21:59 ` [PATCH 5/6] ARM: sunxi: DT: Convert the DTs to use the GIC headers Maxime Ripard
2014-12-16 21:59 ` [PATCH 6/6] ARM: sunxi: DT: Convert the DTs to use the generic interrupt header Maxime Ripard
2014-12-17 7:32 ` [PATCH 1/6] ARM: sunxi: DT: Convert to device tree includes Arnd Bergmann
2014-12-17 21:33 ` Maxime Ripard [this message]
2014-12-17 22:33 ` Arnd Bergmann
2014-12-19 8:46 ` Maxime Ripard
2015-01-06 11:08 ` Maxime Ripard
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=20141217213358.GR4337@lukather \
--to=maxime.ripard@free-electrons.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).