From: "Ondřej Jirman" <megi@xff.cz>
To: u-boot@lists.denx.de
Subject: [U-Boot] [linux-sunxi] Re: [PATCH 3/4] sunxi: dts: added emac node for nanopi m1
Date: Wed, 30 Aug 2017 16:36:38 +0200 [thread overview]
Message-ID: <1504103798.30330.1.camel@xff.cz> (raw)
In-Reply-To: <CAD6G_RQeaJsVTvEJ6U4GvteBw8KSY1pjZGkbb0wiPvPFouGVdg@mail.gmail.com>
Hi,
Jagan Teki píše v St 30. 08. 2017 v 19:48 +0530:
> On Wed, Aug 30, 2017 at 2:40 PM, Philipp Rossak <embed3d@gmail.com> wrote:
> >
> >
> > Am 30.08.2017 um 08:47 schrieb Jagan Teki:
> > >
> > > On Wed, Aug 30, 2017 at 6:02 AM, Philipp Rossak <embed3d@gmail.com> wrote:
> > > >
> > > > From: Philipp Rossak <embed3d@gmail.com>
> > > >
> > > > The sun8i emac hardware is present on the Nanopi M1.
> > > > It uses the internal PHY.
> > > >
> > > > Signed-off-by: Philipp Rossak <embed3d@gmail.com>
> > > > ---
> > > > arch/arm/dts/sun8i-h3-nanopi-m1.dts | 11 +++++++++++
> > > > 1 file changed, 11 insertions(+)
> > > >
> > > > diff --git a/arch/arm/dts/sun8i-h3-nanopi-m1.dts
> > > > b/arch/arm/dts/sun8i-h3-nanopi-m1.dts
> > > > index ec63d10..9c1c380 100644
> > > > --- a/arch/arm/dts/sun8i-h3-nanopi-m1.dts
> > > > +++ b/arch/arm/dts/sun8i-h3-nanopi-m1.dts
> > > > @@ -55,6 +55,17 @@
> > > > status = "okay";
> > > > };
> > > >
> > > > +&emac {
> > > > + phy = <&phy1>;
> > > > + phy-mode = "mii";
> > > > + allwinner,use-internal-phy;
> > > > + allwinner,leds-active-low;
> > > > + status = "okay";
> > > > + phy1: ethernet-phy at 1 {
> > > > + reg = <1>;
> > > > + };
> > > > +};
> > >
> > >
> > > We usually sync Linux for dts changes and I've seen few patches on
> > > Linux, lets wait Linux to merge.
> > >
> > > thanks!
> > >
> >
> > Ok thanks, I didn't know this.
> >
> > Are there also some plans to snyc the sun8i-dwmac driver?
>
> No such plan as of now.
There's apritzel's work on this in this branch:
https://github.com/apritzel/u-boot/commits/a64-pending
> > The dt-binings related to the emac are right now different compared to linux
> > mainline.
>
> Yes, I saw others boards also not using Linux binding. May be we can
> proceed, let me review the patches.
>
> thanks!
> --
> Jagan Teki
> Free Software Engineer | www.openedev.com
> U-Boot, Linux | Upstream Maintainer
> Hyderabad, India.
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 850 bytes
Desc: This is a digitally signed message part
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20170830/cec0fe73/attachment.sig>
next prev parent reply other threads:[~2017-08-30 14:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-30 0:32 [U-Boot] [PATCH 0/4] Enable ethernet on nanopi m1 and nanopi m1 plus Philipp Rossak
2017-08-30 0:32 ` [U-Boot] [PATCH 1/4] sunxi: defconfig: enable sun8i emac on nanopi m1 Philipp Rossak
2017-08-30 0:32 ` [U-Boot] [PATCH 2/4] sunxi: defconfig: enable sun8i emac on nanopi m1 plus Philipp Rossak
2017-08-30 0:32 ` [U-Boot] [PATCH 3/4] sunxi: dts: added emac node for nanopi m1 Philipp Rossak
2017-08-30 6:47 ` Jagan Teki
2017-08-30 9:10 ` Philipp Rossak
2017-08-30 14:18 ` Jagan Teki
2017-08-30 14:36 ` Ondřej Jirman [this message]
2017-08-30 16:59 ` [U-Boot] [linux-sunxi] " Jagan Teki
2017-08-30 23:10 ` Philipp Rossak
2017-08-31 1:31 ` Chen-Yu Tsai
2017-08-30 0:32 ` [U-Boot] [PATCH 4/4] sunxi: dts: added emac node for nanopi m1 plus Philipp Rossak
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=1504103798.30330.1.camel@xff.cz \
--to=megi@xff.cz \
--cc=u-boot@lists.denx.de \
/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