From: Simon Horman <horms@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3/4] ARM: mach-shmobile: r8a7779: Minimal setup using DT
Date: Mon, 18 Feb 2013 12:37:47 +0000 [thread overview]
Message-ID: <20130218123746.GB31922@verge.net.au> (raw)
In-Reply-To: <CANqRtoQtCG87UrpJTPUWts5svG5r8GXa2Q=GBddHRveX8sba7Q@mail.gmail.com>
On Mon, Feb 18, 2013 at 09:14:05PM +0900, Magnus Damm wrote:
> On Mon, Feb 18, 2013 at 8:37 PM, Simon Horman <horms@verge.net.au> wrote:
> > On Mon, Feb 18, 2013 at 06:36:12PM +0900, Magnus Damm wrote:
> >> Hi Simon,
> >>
> >> Here's some feedback on your r8a7779 DT code.
> >>
> >> On Thu, Jan 31, 2013 at 10:50 AM, Simon Horman
> >> <horms+renesas@verge.net.au> wrote:
> >> > Allow a minimal setup of the r8a7779 SoC using a flattened device tree.
> >> > In particular, configure the i2c and ethernet controllers using a
> >> > flattened device tree.
> >> >
> >> > SCI serial controller and TMU clock source, whose drivers do not yet
> >> > support configuration using a flattened device tree, are still configured
> >> > using C code in order to allow booting of a board with this SoC.
> >> >
> >> > The ethernet controller also requires a regulator which is a board property.
> >> > A sample snippet DT for the marzen board is as follows:
> >> >
> >> > /dts-v1/;
> >> > /include/ "r8a7779.dtsi"
> >> >
> >> > / {
> >> > fixedregulator3v3: fixedregulator@0 {
> >> > compatible = "regulator-fixed";
> >> > regulator-name = "fixed-3.3V";
> >> > regulator-min-microvolt = <3300000>;
> >> > regulator-max-microvolt = <3300000>;
> >> > regulator-boot-on;
> >> > regulator-always-on;
> >> > };
> >> > };
> >> >
> >> > &lan0 {
> >> > vddvario-supply = <&fixedregulator3v3>;
> >> > vdd33a-supply = <&fixedregulator3v3>;
> >> > };
> >> >
> >> > Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
> >> > ---
> >>
> >> > --- a/arch/arm/mach-shmobile/setup-r8a7779.c
> >> > +++ b/arch/arm/mach-shmobile/setup-r8a7779.c
> >> > @@ -321,7 +321,7 @@ static struct platform_device i2c3_device = {
> >> > .num_resources = ARRAY_SIZE(rcar_i2c3_res),
> >> > };
> >> >
> >> > -static struct platform_device *r8a7779_early_devices[] __initdata = {
> >> > +static struct platform_device *r8a7779_early_devices_dt[] __initdata = {
> >> > &scif0_device,
> >> > &scif1_device,
> >> > &scif2_device,
> >> > @@ -330,15 +330,15 @@ static struct platform_device *r8a7779_early_devices[] __initdata = {
> >> > &scif5_device,
> >> > &tmu00_device,
> >> > &tmu01_device,
> >> > +};
> >> > +
> >> > +static struct platform_device *r8a7779_early_devices[] __initdata = {
> >> > &i2c0_device,
> >> > &i2c1_device,
> >> > &i2c2_device,
> >> > &i2c3_device,
> >> > };
> >> >
> >> > -static struct platform_device *r8a7779_late_devices[] __initdata = {
> >> > -};
> >> > -
> >>
> >> Thanks for your work on this. Two things with early/late devices on r8a7779:
> >>
> >> 1) Same thing as sh73a0 applies here, please refrain from using early
> >> devices with DT.
> >
> > I guess you are referring to tmu.
> > If so, yes, I can move them to r8a7779_early_devices.
>
> As we talked about last Friday, please try to avoid using early
> devices in general. It is enough to add SCIF and TMU as late devices.
> This goes for both sh73a0 and r8a7779. The only thing you need to do
> early is to setup the delay. Please look at the emev2 implementation
> for what is needed.
Thanks, I understand.
> >> 2) The i2c devices as early devices look incorrect. Can you make them
> >> late devices?
> >
> > r8a7779_early_devices is only used for the non-DT case.
> > For the non-DT case i2c was set up as early devices before this patch-set.
> > Would you like me to change them to late devices for non-DT,
> > a change that is orthogonal to this patch-set?
>
> Yes. I realize it is not really related to this DT feature, but it
> certainly looks incorrect.
Got it. I will see about making it so.
next prev parent reply other threads:[~2013-02-18 12:37 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 1:50 ARM: mach-shmobile: r8a7779, marzen: Reference DT implementation Simon Horman
2013-01-31 1:50 ` [PATCH 1/4] ARM: mach-shmobile: marzen: defconfig: use regulators by default Simon Horman
2013-01-31 1:50 ` [PATCH 2/4] ARM: mach-shmobile: r8a7779: Allow initialisation of GIC by DT Simon Horman
2013-01-31 12:32 ` Mark Rutland
2013-02-01 0:11 ` Simon Horman
2013-02-01 0:34 ` Simon Horman
2013-02-01 1:47 ` Simon Horman
2013-02-01 4:39 ` Simon Horman
2013-02-01 11:31 ` Mark Rutland
2013-02-01 10:58 ` Mark Rutland
2013-02-01 14:15 ` Rob Herring
2013-02-04 17:37 ` Mark Rutland
2013-02-16 21:43 ` [PATCH 2/4] ARM: mach-shmobile: r8a7779: add SATA support Sergei Shtylyov
2013-02-18 1:23 ` Kuninori Morimoto
2013-02-18 14:07 ` Sergei Shtylyov
2013-02-18 14:21 ` Magnus Damm
2013-02-19 0:40 ` Kuninori Morimoto
2013-02-19 1:26 ` Simon Horman
2013-02-19 14:26 ` Sergei Shtylyov
2013-02-19 1:25 ` Simon Horman
2013-01-31 1:50 ` [PATCH 3/4] ARM: mach-shmobile: r8a7779: Minimal setup using DT Simon Horman
2013-02-18 9:36 ` Magnus Damm
2013-02-18 11:37 ` Simon Horman
2013-02-18 12:14 ` Magnus Damm
2013-02-18 12:37 ` Simon Horman [this message]
2013-02-18 12:22 ` Magnus Damm
2013-02-18 12:37 ` Simon Horman
2013-02-18 19:30 ` [PATCH 3/4] ARM: mach-shmobile: r8a7779: add SATA support Sergei Shtylyov
2013-01-31 1:50 ` [PATCH 4/4] ARM: mach-shmobile: marzen: Reference DT implementation Simon Horman
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=20130218123746.GB31922@verge.net.au \
--to=horms@verge.net.au \
--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