[U-Boot] [PATCH v2 8/9] arm: dts: add ethernet node to Meson gxbb

[Tom Rini]

On Sun, Apr 03, 2016 at 11:12:14AM +0200, Carlo Caione wrote:
> On Sun, Apr 3, 2016 at 9:18 AM, Beniamino Galvani <b.galvani at gmail.com> wrote:
> > Add a node for the Synopsys Designware Ethernet adapter available on
> > Meson SoCs to the Meson GXBaby DTS files. The node is not present in
> > DTS files used in Linux kernel.
> >
> > Signed-off-by: Beniamino Galvani <b.galvani at gmail.com>
> > ---
> >  arch/arm/dts/meson-gxbb-odroidc2.dts | 4 ++++
> >  arch/arm/dts/meson-gxbb.dtsi         | 9 +++++++++
> >  2 files changed, 13 insertions(+)
> >
> > diff --git a/arch/arm/dts/meson-gxbb-odroidc2.dts b/arch/arm/dts/meson-gxbb-odroidc2.dts
> > index 653c2fa..408235d 100644
> > --- a/arch/arm/dts/meson-gxbb-odroidc2.dts
> > +++ b/arch/arm/dts/meson-gxbb-odroidc2.dts
> > @@ -67,3 +67,7 @@
> >  &uart_AO {
> >         status = "okay";
> >  };
> > +
> > +&gmac0 {
> > +       status = "okay";
> > +};
> > diff --git a/arch/arm/dts/meson-gxbb.dtsi b/arch/arm/dts/meson-gxbb.dtsi
> > index 832815d..44a54e7 100644
> > --- a/arch/arm/dts/meson-gxbb.dtsi
> > +++ b/arch/arm/dts/meson-gxbb.dtsi
> > @@ -167,6 +167,15 @@
> >                         };
> >                 };
> >
> > +               gmac0: ethernet at c9410000 {
> > +                       compatible = "snps,dwmac";
> > +                       reg = <0x0 0xc9410000 0x0 0x10000>;
> > +                       interrupts = <0 8 1>;
> > +                       interrupt-names = "macirq";
> > +                       phy-mode = "rgmii";
> > +                       status = "disabled";
> > +               };
> > +
> >                 apb: apb at d0000000 {
> >                         compatible = "simple-bus";
> >                         reg = <0x0 0xd0000000 0x0 0x200000>;
> 
> Adding this gmac node means that this DTS is already different from
> the DTS we have in mainline. This makes me wonder how in u-boot we
> manages the difference in the DT between the kernel and u-boot. Are
> they supposed to be always in sync or we expect to have two different
> DTs?

The expectation is that we keep them in sync, aside from "u-boot,"
prefixed items.  It's OK to sync with whatever the authorative tree is
for a device if it hasn't made it into Linus' tree just yet.  New
bindings also need to be accepted upstream before we pull them in.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160403/6a729a61/attachment.sig>