From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Stefan Mavrodiev <stefan.mavrodiev@gmail.com>
Cc: Stefan Mavrodiev <stefan@olimex.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Russell King <linux@armlinux.org.uk>,
Chen-Yu Tsai <wens@csie.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-sunxi@googlegroups.com
Subject: Re: [PATCH v2 1/2] ARM: dts: sun7i: Fix A20-OLinuXino-MICRO dts for LAN8710
Date: Fri, 1 Sep 2017 15:06:56 +0200 [thread overview]
Message-ID: <20170901130656.tfiqepmxxh2zrfee@flea> (raw)
In-Reply-To: <e7e61776-b8d7-c42f-4e9e-04da835374a9@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2702 bytes --]
On Thu, Aug 31, 2017 at 08:20:18AM +0300, Stefan Mavrodiev wrote:
> > > From revision J the board uses new phy chip LAN8710. Compared
> > > with RTL8201, RA17 pin is TXERR. It has pullup which causes phy
> > > not to work. To fix this PA17 is muxed with GMAC function. This
> > > makes the pin output-low.
> > >
> > > This patch is compatible with earlier board revisions, since this
> > > pin wasn't connected to phy.
> > >
> > > Signed-off-by: Stefan Mavrodiev <stefan@olimex.com>
> > > ---
> > > arch/arm/boot/dts/sun7i-a20-olinuxino-micro.dts | 7 ++++++-
> > > 1 file changed, 6 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/arch/arm/boot/dts/sun7i-a20-olinuxino-micro.dts b/arch/arm/boot/dts/sun7i-a20-olinuxino-micro.dts
> > > index 0b7403e..cb1b081 100644
> > > --- a/arch/arm/boot/dts/sun7i-a20-olinuxino-micro.dts
> > > +++ b/arch/arm/boot/dts/sun7i-a20-olinuxino-micro.dts
> > > @@ -102,7 +102,7 @@
> > > &gmac {
> > > pinctrl-names = "default";
> > > - pinctrl-0 = <&gmac_pins_mii_a>;
> > > + pinctrl-0 = <&gmac_pins_mii_a>,<&gmac_txerr>;
> > > phy = <&phy1>;
> > > phy-mode = "mii";
> > > status = "okay";
> > > @@ -229,6 +229,11 @@
> > > };
> > > &pio {
> > > + gmac_txerr: gmac_txerr@0 {
> > > + pins = "PA17";
> > > + function = "gmac";
> > > + };
> > > +
> > The patch looks fine, I still have one question though.
> >
> > Can a PHY operate without this signal? My real question is, would it
> > make sense to mux that pin for all the users, or is it an optional
> > signal that each board designer can choose to use or not?
> >
> > Thanks!
> > Maxime
>
> This phy (LAN8710) cannot work without this pin. Part of the problem
> is in that we've replaced without paying attention to this signal.
>
> RTL8201 has no TXERR pin. The pin PA17 is used as reset signal and
> therefore is pulled up with resistor. However on old revisions this
> option (there is jumper pad between SOC and PHY).
>
> As I said, LAN8710 cannot work without this signal. In the datasheet
> is written:
>
> ...
> The controller drives TXER high when a transmit error is detected.
> ...
>
> In the current variant of the dts, all data is threated as error.
Sorry if my question was unclear, I meant to ask for all PHYs
connected to an A20. I got that you were needing it for that
particular one :)
> So to answer you question. This is feature only on our board and
> highly depends on the chosen PHY. I don't think this should be
> muxed for all users.
Ok, I guess it answers it. Thanks!
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2017-09-01 13:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 6:32 [PATCH v2 0/2] Update board support for A20-OLinuXino-MICRO Stefan Mavrodiev
2017-08-28 6:32 ` [PATCH v2 1/2] ARM: dts: sun7i: Fix A20-OLinuXino-MICRO dts for LAN8710 Stefan Mavrodiev
2017-08-30 14:37 ` Maxime Ripard
2017-08-31 5:20 ` Stefan Mavrodiev
2017-09-01 13:06 ` Maxime Ripard [this message]
2017-09-26 13:09 ` [linux-sunxi] " Jonathan Liu
2017-09-01 13:08 ` Maxime Ripard
2017-08-28 6:32 ` [PATCH v2 2/2] ARM: dts: sun7i: Add dts file for A20-OLinuXino-MICRO-eMMC Stefan Mavrodiev
2017-08-30 14:38 ` Maxime Ripard
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=20170901130656.tfiqepmxxh2zrfee@flea \
--to=maxime.ripard@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=stefan.mavrodiev@gmail.com \
--cc=stefan@olimex.com \
--cc=wens@csie.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
all inboxes | Powered by JetHome®