From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Simon Horman <horms@verge.net.au>
Cc: Chris Paterson <Chris.Paterson2@renesas.com>,
Biju Das <biju.das@bp.renesas.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Magnus Damm <magnus.damm@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH ] ARM: dts: iwg22d-sodimm: Add Ethernet AVB support
Date: Fri, 1 Sep 2017 11:30:33 +0200 [thread overview]
Message-ID: <CAMuHMdXFO+oirricuB2prtm2ca1AyMLDgx6ib5cVNRK0=7T+5g@mail.gmail.com> (raw)
In-Reply-To: <20170901084923.GC14918@verge.net.au>
Hi Simon,
On Fri, Sep 1, 2017 at 10:49 AM, Simon Horman <horms@verge.net.au> wrote:
> On Thu, Aug 31, 2017 at 09:32:25AM +0000, Chris Paterson wrote:
>> > From: Biju Das
>> > > From: Simon Horman [mailto:horms@verge.net.au]
>> > > > + phy3: ethernet-phy@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 guess it behaves similar to Koelsch using the new CPG/MSSR driver, and
without the probe deferral fix for of_mdio, where it also falls back to polling.
Cfr. the figures in
https://www.mail-archive.com/linux-renesas-soc@vger.kernel.org/msg17422.html
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2017-09-01 9:30 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
[not found] ` <20170831084534.GF29946-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
2017-08-31 9:24 ` Biju Das
2017-08-31 9:32 ` Chris Paterson
[not found] ` <TY1PR06MB07029D315FC6EE500D1EEA55B79D0-/PRLmSCtZ14u2TXDOttQZW0DtJ1/0DrXvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2017-09-01 8:49 ` Simon Horman
2017-09-01 9:30 ` Geert Uytterhoeven [this message]
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='CAMuHMdXFO+oirricuB2prtm2ca1AyMLDgx6ib5cVNRK0=7T+5g@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=Chris.Paterson2@renesas.com \
--cc=biju.das@bp.renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).