From: Simon Horman <horms@verge.net.au>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: linux-renesas-soc@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>,
Magnus Damm <magnus.damm@gmail.com>,
linux-arm-kernel@lists.infradead.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: Re: [PATCH/RFC repost] arm64: dts: renesas: ebisu, draak: Limit EtherAVB to 100Mbps
Date: Wed, 24 Jul 2019 12:52:03 +0200 [thread overview]
Message-ID: <20190724105203.thykr2staw22gdj3@verge.net.au> (raw)
In-Reply-To: <20190717132607.GA1458@kunai>
On Wed, Jul 17, 2019 at 03:26:07PM +0200, Wolfram Sang wrote:
> On Wed, Jul 17, 2019 at 02:57:39PM +0200, Simon Horman wrote:
> > * According to the R-Car Gen3 Hardware Manual Errata for Rev 1.00 of
> > August 24, 2018, the TX clock internal delay mode isn't supported
> > on R-Car E3 (r8a77990) and D3 (r8a77995).
> >
> > * TX clock internal delay mode is required for reliable 1Gbps communication
> > using the KSZ9031RNX phy present on the Ebisu and Draak boards.
> >
> > Thus, the E3 based Ebisu and D3 based Draak boards reliably use 1Gbps and
> > the speed should be limited to 100Mbps.
> >
> > Based on work by Kazuya Mizuguchi.
> >
> > Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
>
> What about adding a short comment explaining the situation?
Do you mean in the DT itself?
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-07-24 10:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-17 12:57 [PATCH/RFC repost] arm64: dts: renesas: ebisu, draak: Limit EtherAVB to 100Mbps Simon Horman
2019-07-17 13:24 ` Kieran Bingham
2019-07-24 10:52 ` Simon Horman
2019-07-17 13:26 ` Wolfram Sang
2019-07-24 10:52 ` Simon Horman [this message]
2019-07-24 21:04 ` Wolfram Sang
2019-07-25 5:57 ` Simon Horman
2019-07-25 7:35 ` Wolfram Sang
2019-07-25 9:51 ` Simon Horman
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=20190724105203.thykr2staw22gdj3@verge.net.au \
--to=horms@verge.net.au \
--cc=andrew@lunn.ch \
--cc=geert+renesas@glider.be \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=wsa@the-dreams.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;
as well as URLs for NNTP newsgroup(s).