From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 1/9] ARM: kirkwood: convert d2net_v2 to DT
Date: Sat, 12 Oct 2013 17:29:00 +0200 [thread overview]
Message-ID: <20131012172900.787c68eb@skate> (raw)
In-Reply-To: <20130813095830.GI27165@e106331-lin.cambridge.arm.com>
Dear Mark Rutland,
On Tue, 13 Aug 2013 10:58:30 +0100, Mark Rutland wrote:
> > + regulators {
> > + compatible = "simple-bus";
> > + pinctrl-0 = <&pmx_sata_power>;
> > + pinctrl-names = "default";
> > + #address-cells = <1>;
> > + #size-cells = <0>;
>
> That's not really a simple-bus if there's no mapping to the parent's
> address space (and it represents a completely different concept of
> address).
Right, but I guess it is needed for the child nodes to be considered as
platform devices. There are already gazillions of .dts doing this in
arch/arm/boot/dts, not only Kirkwood platforms, but also Tegra
platforms, i.MX platforms and a bunch of others. While I admit it
doesn't look the most appropriate representation, I believe that
considering the number of existing users, solving this problem is a
separate matter to the conversion of the d2net_v2 to the Device Tree.
> Could you explain what the pinctrl's doing here? I couldn't see what
> code would be handling that given the node will get probed as a
> simple-bus and the regulator-fixed binding doesn't mention anything
> about the parent node.
Right, the pinctrl should be one-level down, in the DT sub-node that
describes the regulator, so that it get automatically configured
because the regulator driver is a platform_driver.
I'll fix this.
> > +
> > + sata0_power: regulator at 1 {
> > + compatible = "regulator-fixed";
> > + reg = <1>;
>
> Do we even need the unit-address?
No, I'll fix this one as well.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-10-12 15:29 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 15:07 [PATCHv2 0/9] ARM: kirkwood: convert a few more boards to DT Thomas Petazzoni
2013-08-01 15:07 ` [PATCHv2 1/9] ARM: kirkwood: convert d2net_v2 " Thomas Petazzoni
2013-08-02 14:31 ` Simon Guinot
2013-10-12 15:26 ` Thomas Petazzoni
2013-08-02 14:46 ` [PATCH] leds: leds-ns2: depends on ARCH_KIRKWOOD Simon Guinot
2013-08-03 18:16 ` Jason Cooper
2013-08-05 22:50 ` Bryan Wu
2013-08-13 9:58 ` [PATCHv2 1/9] ARM: kirkwood: convert d2net_v2 to DT Mark Rutland
2013-10-12 15:29 ` Thomas Petazzoni [this message]
2013-10-14 11:26 ` Mark Rutland
2013-08-01 15:07 ` [PATCHv2 2/9] ARM: kirkwood: remove support for legacy booting of Dockstar Thomas Petazzoni
2013-08-03 18:27 ` Jason Cooper
2013-08-01 15:07 ` [PATCHv2 3/9] ARM: kirkwood: remove support for legacy booting of Guruplug Thomas Petazzoni
2013-08-02 12:49 ` Jason Cooper
2013-08-02 13:08 ` Arnaud Patard (Rtp)
2013-08-01 15:07 ` [PATCHv2 4/9] ARM: kirkwood: remove support for legacy booting of Sheevaplug Thomas Petazzoni
2013-08-01 15:07 ` [PATCHv2 5/9] ARM: kirkwood: remove LaCie boards that are supported through DT Thomas Petazzoni
2013-08-01 15:07 ` [PATCHv2 6/9] ARM: kirkwood: convert the mv88f6281gtw_ge board to DT Thomas Petazzoni
2013-08-01 15:07 ` [PATCHv2 7/9] ARM: kirkwood: convert LaCie Net{2, 5}Big v2 platforms " Thomas Petazzoni
2013-08-02 21:25 ` Simon Guinot
2013-08-03 17:12 ` Jason Cooper
2013-08-02 21:34 ` [PATCH] leds: leds-netxbig: depends on ARCH_KIRKWOOD Simon Guinot
2013-08-03 14:12 ` Jason Cooper
2013-08-05 22:52 ` Bryan Wu
2013-08-06 12:17 ` Jason Cooper
2013-08-06 17:40 ` Bryan Wu
2013-08-01 15:07 ` [PATCHv2 8/9] ARM: kirkwood: remove unused common code for LaCie platforms Thomas Petazzoni
2013-08-02 21:45 ` Simon Guinot
2013-08-01 15:07 ` [PATCHv2 9/9] ARM: kirkwood: update defconfig after DT conversions Thomas Petazzoni
2013-08-03 18:56 ` [PATCHv2 0/9] ARM: kirkwood: convert a few more boards to DT Jason Cooper
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=20131012172900.787c68eb@skate \
--to=thomas.petazzoni@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 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.