From: "Krzysztof Hałasa" <khalasa@piap.pl>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: netdev <netdev@vger.kernel.org>,
Oliver Neukum <oneukum@suse.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>, <linux-usb@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Jose Ignacio Tornos Martinez <jtornosm@redhat.com>,
Ming Lei <ming.lei@redhat.com>
Subject: Re: [PATCH REPOST] usbnet: asix: leave the carrier control to phylink
Date: Tue, 08 Apr 2025 13:55:49 +0200 [thread overview]
Message-ID: <m3tt6ydfzu.fsf@t19.piap.pl> (raw)
In-Reply-To: <Z_PVOWDMzmLObRM6@pengutronix.de> (Oleksij Rempel's message of "Mon, 7 Apr 2025 15:38:01 +0200")
Oleksij,
thanks for your fast response.
Oleksij Rempel <o.rempel@pengutronix.de> writes:
> Good point, this artifact should be partially removed, but not for all
> devices. Only ax88772 are converted to PHYlink. ax88178 are not
> converted.
There is also AX88172. I assume the situation with 172 and 178 is
similar.
> The AX88772 portion of the driver, is not forwarding the interrupt to
> the PHY driver. It means, PHY is in polling mode. As long as PHY
> provides proper information, it will work.
It does, yes.
> On other hand, you seems to use AX88772B in 100BASE-FX mode. I'm sure,
> current PHY driver for this device do not know anything about FX mode:
> drivers/net/phy/ax88796b.c
>
> Which 100BASE-FX PHY capable device do you use? Is it possible to buy
> it some where?
No, it's a part of custom hw, but the carrier problem seems to be
independent of the actual PHY type. The PHY code needs a bit of fixing
as well, though (one can't really enable autoneg with 100BASE-FX).
Will attach a version with 8817x parts removed.
--
Krzysztof "Chris" Hałasa
Sieć Badawcza Łukasiewicz
Przemysłowy Instytut Automatyki i Pomiarów PIAP
Al. Jerozolimskie 202, 02-486 Warszawa
next prev parent reply other threads:[~2025-04-08 11:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 12:08 [PATCH REPOST] usbnet: asix: leave the carrier control to phylink Krzysztof Hałasa
2025-04-07 13:38 ` Oleksij Rempel
2025-04-08 11:55 ` Krzysztof Hałasa [this message]
2025-04-08 11:59 ` [PATCH v2] usbnet: asix AX88772: " Krzysztof Hałasa
2025-04-08 15:22 ` Jakub Kicinski
2025-04-10 12:14 ` Oleksij Rempel
2025-04-11 2:20 ` patchwork-bot+netdevbpf
2025-04-08 13:29 ` [PATCH REPOST] usbnet: asix: " Paolo Abeni
2025-04-09 9:07 ` Krzysztof Hałasa
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=m3tt6ydfzu.fsf@t19.piap.pl \
--to=khalasa@piap.pl \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jtornosm@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=oneukum@suse.com \
--cc=pabeni@redhat.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).