[PATCH v2] ARM: SPEAr600: Add device-tree support to SPEAr600 boards
Stefan Roese
sr at denx.de
Thu Mar 15 04:41:02 EDT 2012
Hi Viresh,
On Thursday 15 March 2012 09:19:54 Viresh Kumar wrote:
> Hi Stefan,
>
> Thanks for your patch. :)
You are welcome. :)
> I have looked carefully at the patch, regarding addresses and irq numbers,
> and they look fine. Just few minor comments below:
>
> On 3/14/2012 8:30 PM, Stefan Roese wrote:
> > diff --git a/arch/arm/boot/dts/spear600.dtsi
> > b/arch/arm/boot/dts/spear600.dtsi
> >
> > + soc {
> > + #address-cells = <1>;
> > + #size-cells = <1>;
> > + compatible = "simple-bus";
> > + ranges;
> > +
> >
> > +
> > + gmac0: ethernet at e0800000 {
>
> There is no gmac1, so can name it gmac only.
I have no strong preference here. Not sure, what the common practice is. But I
can remove the numbers on those single instance devices.
> > + compatible = "st,spear600-gmac";
> > + reg = <0xe0800000 0x8000>;
> > + interrupt-parent = <&vic1>;
> > + interrupts = <24 23>;
> > + interrupt-names = "macirq", "eth_wake_irq";
> > + mac-address = [000000000000]; /* Filled in by
> > U-Boot */ + };
> > +
> >
> > + fsmc0: flash at d1800000 {
>
> same.
>
> > + status = "disabled";
> > + compatible = "st,spear600-fsmc-nand";
> > + #address-cells = <1>;
> > + #size-cells = <1>;
> > + reg = <0xd1800000 0x1000 /* FSMC Register
> > */ + 0xd2000000 0x4000>; /* NAND Base
> > */ + reg-names = "fsmc_regs", "nand_data";
> > + };
> > +
> > + smi0: flash at fc000000 {
>
> same
>
> > + status = "disabled";
> > + compatible = "st,spear600-smi";
> > + #address-cells = <1>;
> > + #size-cells = <1>;
> > + reg = <0xfc000000 0x1000>;
> > + interrupt-parent = <&vic1>;
> > + interrupts = <12>;
> > + };
> > +
> >
> > diff --git a/arch/arm/mach-spear6xx/spear600_evb.c
> > b/arch/arm/mach-spear6xx/spear600_evb.c index c6e4254..c4949aa 100644
> > --- a/arch/arm/mach-spear6xx/spear600_evb.c
> > +++ b/arch/arm/mach-spear6xx/spear600_evb.c
> > @@ -32,9 +32,6 @@ static void __init spear600_evb_init(void)
> >
> > {
> >
> > unsigned int i;
>
> Why don't we remove the devices from arrays above, which are now
> supported by DT?
This is the non-DT file (spear600_evb.c). I wanted to preserve it, so that it
still can be built. But thinking a bit more about it, the current mainline
SPEAr600 port only supports UART and GPIO as peripheral devices. And this
SPEAr600 DT patch also supports those and even more devices.
So why don't we make an even bigger "cut", and remove the non-DT SPEAr600
files/data completely now? If you give me your ACK on this, I'll squash this
into my patch as well, resulting in a nice diffstat. ;)
> > - /* call spear600 machine init function */
> > - spear600_init();
> > -
> >
> > /* Add Platform Devices */
> > platform_add_devices(plat_devs, ARRAY_SIZE(plat_devs));
> >
> > diff --git a/arch/arm/mach-spear6xx/spear6xx.c
> > b/arch/arm/mach-spear6xx/spear6xx.c
> >
> > +static const struct of_device_id vic_of_match[] __initconst = {
> > + { .compatible = "arm,pl190-vic", .data = vic_of_init, },
> > + { /* Sentinel */ }
> > +};
> > +
> > +static void __init spear6xx_dt_init_irq(void)
> > +{
> > + of_irq_init(vic_of_match);
> > +}
> > +
>
> Did you checked this out?
Not yet. Sorry, I missed it. Will check now...
Thanks,
Stefan
More information about the linux-arm-kernel
mailing list