From: Andrew Lunn <andrew@lunn.ch>
To: Michael Walle <michael@walle.cc>
Cc: Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
Horatiu Vultur <horatiu.vultur@microchip.com>,
netdev@vger.kernel.org, Xu Liang <lxu@maxlinear.com>
Subject: Re: GPY215 PHY interrupt issue
Date: Thu, 1 Dec 2022 16:54:26 +0100 [thread overview]
Message-ID: <Y4jOMocoLneO8xoD@lunn.ch> (raw)
In-Reply-To: <c69e1d1d897dd7500b59c49f0873e7dd@walle.cc>
> So, switching the line to GPIO input doesn't help here, which also
> means the interrupt line will be stuck the whole time.
Sounds like they totally messed up the design somehow.
Since we are into horrible hack territory.....
I assume you are using the Link state change interrupt? LSTC?
Maybe instead use Link speed change and Duplex mode change? And
disallow 10/Half. Some PHYs change to 10/Half when they loose
link. They might be enough to tell you the link has changed. You can
then read the BMSR to find out what actually happened.
This is assuming that interrupts in general are not FUBAR.
Andrew
next prev parent reply other threads:[~2022-12-01 15:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 14:44 GPY215 PHY interrupt issue Michael Walle
2022-11-25 15:17 ` Andrew Lunn
2022-11-27 19:01 ` Michael Walle
2022-11-28 7:41 ` Michael Walle
2022-11-28 13:30 ` Andrew Lunn
2022-12-01 10:24 ` Michael Walle
2022-12-01 15:54 ` Andrew Lunn [this message]
2022-12-01 21:31 ` Michael Walle
2022-12-01 22:06 ` Andrew Lunn
2022-12-01 23:24 ` Michael Walle
2022-12-02 0:05 ` Andrew Lunn
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=Y4jOMocoLneO8xoD@lunn.ch \
--to=andrew@lunn.ch \
--cc=hkallweit1@gmail.com \
--cc=horatiu.vultur@microchip.com \
--cc=linux@armlinux.org.uk \
--cc=lxu@maxlinear.com \
--cc=michael@walle.cc \
--cc=netdev@vger.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).