From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH ] ARM: dts: iwg22d-sodimm: Add Ethernet AVB support
Date: Fri, 1 Sep 2017 10:49:23 +0200 [thread overview]
Message-ID: <20170901084923.GC14918@verge.net.au> (raw)
In-Reply-To: <TY1PR06MB07029D315FC6EE500D1EEA55B79D0@TY1PR06MB0702.apcprd06.prod.outlook.com>
On Thu, Aug 31, 2017 at 09:32:25AM +0000, Chris Paterson wrote:
> Hello,
>
> > From: Biju Das
> > Sent: 31 August 2017 10:24
> >
> > > From: Simon Horman [mailto:horms at verge.net.au]
> > > Sent: 31 August 2017 09:46
>
> <snip>
>
> > > > + phy3: ethernet-phy at 3 {
> > > > + /*
> > > > + * On some older versions of the platform (before R4.0) the phy
> > > address
> > > > + * may be 1 or 3. The address is fixed to 3 for R4.0 onwards.
> > > > + */
> > > > + reg = <3>;
> > > > + micrel,led-mode = <1>;
> > >
> > > Does the phy have an interrupt?
> >
> > The current board doesn't support interrupt . But there is a plan to support this
> > in future board variants through (GPIO3_28).
>
> Actually, the plan has recently changed and at the moment interrupt support will not be added in the production version of the board.
>
> If in the end the plan changes again and the actual hardware does add interrupt support we'll submit a new patch accordingly.
Thanks for following-up on this. I'm still surprised there is no interrupt
- does link speed renegotiation initiated by the other end of the link work
in a timely manner? - but if its not there and my wishful thinking won't
make it so.
I have applied this patch for v4.15.
next prev parent reply other threads:[~2017-09-01 8:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-30 15:17 [PATCH ] ARM: dts: iwg22d-sodimm: Add Ethernet AVB support Biju Das
2017-08-31 8:45 ` Simon Horman
2017-08-31 9:24 ` Biju Das
2017-08-31 9:32 ` Chris Paterson
2017-09-01 8:49 ` Simon Horman [this message]
2017-09-01 9:30 ` Geert Uytterhoeven
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=20170901084923.GC14918@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