From: Oleksij Rempel <o.rempel@pengutronix.de>
To: "Maciej Żenczykowski" <maze@google.com>
Cc: stable@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Lunn <andrew@lunn.ch>, Patrick Rohr <prohr@google.com>
Subject: Re: USB_NET_AX8817X dependency on AX88796B_PHY
Date: Mon, 16 Oct 2023 10:29:13 +0200 [thread overview]
Message-ID: <20231016082913.GB3502392@pengutronix.de> (raw)
In-Reply-To: <CANP3RGe82EQhdKd_sc7kWDm2jqx1jTa-Rnj23xBSVpFvK_-T2Q@mail.gmail.com>
On Sun, Oct 15, 2023 at 03:13:26PM -0700, Maciej Żenczykowski wrote:
> On Sun, Oct 15, 2023 at 2:55 PM Maciej Żenczykowski <maze@google.com> wrote:
> And actually looking longer at the logs:
>
> usb 1-5: new high-speed USB device number 9 using xhci_hcd
> usb 1-5: New USB device found, idVendor=0b95, idProduct=772b, bcdDevice= 0.02
> usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> usb 1-5: Product: AX88772C
> usb 1-5: Manufacturer: ASIX Elec. Corp.
> usb 1-5: SerialNumber: 000002
> asix 1-5:1.0 (unnamed net_device) (uninitialized): PHY
> [usb-001:009:10] driver [Asix Electronics AX88772C] (irq=POLL)
> Asix Electronics AX88772C usb-001:009:10: attached PHY driver
> (mii_bus:phy_addr=usb-001:009:10, irq=POLL)
> asix 1-5:1.0 eth0: register 'asix' at usb-0000:00:14.0-5, ASIX
> AX88772B USB 2.0 Ethernet, 14:ae:85:70:44:29
> asix 1-5:1.0 enx14ae85704429: renamed from eth0
> asix 1-5:1.0 enx14ae85704429: configuring for phy/internal link mode
> usb 1-5: USB disconnect, device number 9
> asix 1-5:1.0 enx14ae85704429: unregister 'asix' usb-0000:00:14.0-5,
> ASIX AX88772B USB 2.0 Ethernet
>
> It looks like the rest of that patch is needed too, since it is a AX88772C phy.
>
> This means even with the option manually enabled, we'd still need to
> cherrypick dde25846925765a88df8964080098174495c1f10
> "net: usb/phy: asix: add support for ax88772A/C PHYs"
> since apparently this is simply new(ish) hardware with built-in x88772C PHY.
As far as I see, you are not using clean mainline stable kernel. All changes
which make your kernel to need an external PHY driver are _not_ in v5.10.198.
You will need to cherrypick at least 28 last patches from this stack:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/log/drivers/net/usb/asix_devices.c?h=v6.6-rc6
and some from here too:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/log/drivers/net/usb/usbnet.c?h=v6.6-rc6
Regards,
Oleksij
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2023-10-16 8:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-15 21:55 USB_NET_AX8817X dependency on AX88796B_PHY Maciej Żenczykowski
2023-10-15 22:13 ` Maciej Żenczykowski
2023-10-16 8:29 ` Oleksij Rempel [this message]
2023-10-16 18:27 ` Maciej Żenczykowski
2023-10-17 4:20 ` Oleksij Rempel
2023-10-17 5:58 ` Maciej Żenczykowski
2023-10-19 18:19 ` Maciej Żenczykowski
2023-10-16 5:14 ` Oleksij Rempel
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=20231016082913.GB3502392@pengutronix.de \
--to=o.rempel@pengutronix.de \
--cc=andrew@lunn.ch \
--cc=gregkh@linuxfoundation.org \
--cc=maze@google.com \
--cc=prohr@google.com \
--cc=stable@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