From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Michael Walle <michael@walle.cc>
Cc: Matus Ujhelyi <ujhelyi.m@gmail.com>,
acmattheis@gmx.net,
Christoph Mattheis <christoph.mattheis@arcor.de>,
linux-arm-kernel@lists.infradead.org
Subject: Re: Broken ethernet on SolidRun cubox-i
Date: Sun, 27 Dec 2020 16:11:15 +0000 [thread overview]
Message-ID: <20201227161114.GF1551@shell.armlinux.org.uk> (raw)
In-Reply-To: <a04a56fccd29329ba4a8624c015a5c2e@walle.cc>
On Sun, Dec 27, 2020 at 04:59:39PM +0100, Michael Walle wrote:
> Am 2020-12-27 16:33, schrieb Michael Walle:
> > Am 2020-12-26 13:34, schrieb Russell King - ARM Linux admin:
> > > I'd forgotten that there were boards out there with this problem...
> > > the PHY address configuration is done via the LED_ACT pin, and
> > > SolidRun
> > > omitted a pull resistor on it, so it "floats" with the leakage current
> > > of the LED/pin - resulting in it sometimes appearing at address 0 and
> > > sometimes at address 4.
> >
> > Mh, I've guessed that too, but there must be more to it. The datasheet
> > says it has an internal weak pull-up. Or Atheros messed up and it
> > doesn't
> > reliably work if there is actually an LED attached to it. But then, why
> > would any other stronger pull-up/down work..
>
> Mhh, nevermind, from the commit log [1].
>
> "The LED_ACT pin on the carrier-one boards had a pull down that
> forces the phy address to 0x0; where on CuBox-i and the production
> HummingBoard that pin is connected directly to LED that depending
> on the pull down strength of the LED it might be sampled as '0' or '1'
> thus
> the phy address might appear as either address 0x0 or 0x4."
>
> So it actually depends on the forward voltage of the LED and the
> hi/low thresholds of the AT8035.. nice! Oh and btw. this pin also
> switches between high and low-active LED output. So the missing
> pull-down might not only switch the PHY address to 4 but also invert
> the LED state.
Indeed. And whether it appears at address 0 or 4 will depend on many
factors, including temperature - LEDs have a decrease of 2mV/°C.
I wonder if we can just delete the phy-handle property, and list a
PHY at both address 0 and 4 with the appropriate configuration...
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
_______________________________________________
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:[~2020-12-27 16:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-26 12:18 Broken ethernet on SolidRun cubox-i Michael Walle
2020-12-26 12:34 ` Russell King - ARM Linux admin
2020-12-27 15:33 ` Michael Walle
2020-12-27 15:59 ` Michael Walle
2020-12-27 16:11 ` Russell King - ARM Linux admin [this message]
2020-12-27 18:07 ` Andrew Lunn
2021-01-08 11:53 ` Russell King - ARM Linux admin
2021-01-08 11:58 ` Michael Walle
2021-01-08 12:01 ` Russell King - ARM Linux admin
2021-01-08 12:14 ` Michael Walle
2021-01-08 12:25 ` Christoph Mattheis
2021-01-08 12:27 ` Russell King - ARM Linux admin
2021-01-08 12:33 ` Christoph Mattheis
2021-01-08 12:37 ` Russell King - ARM Linux admin
2021-01-08 12:51 ` Michael Walle
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=20201227161114.GF1551@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=acmattheis@gmx.net \
--cc=christoph.mattheis@arcor.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=michael@walle.cc \
--cc=ujhelyi.m@gmail.com \
/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).