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: Tue, 17 Oct 2023 06:20:29 +0200 [thread overview]
Message-ID: <20231017042029.GA3539182@pengutronix.de> (raw)
In-Reply-To: <CANP3RGfp9dNun7-gAarqXo71ay2jeLnqO6eJzmXpNKAmXYeosw@mail.gmail.com>
On Mon, Oct 16, 2023 at 11:27:07AM -0700, Maciej Żenczykowski wrote:
> On Mon, Oct 16, 2023 at 1:29 AM Oleksij Rempel <o.rempel@pengutronix.de> wrote:
> > On Sun, Oct 15, 2023 at 03:13:26PM -0700, Maciej Żenczykowski wrote:
> > > 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.
>
> No, the dmesg was actually from a (probably clean-ish 6.4-ish) debian
> kernel on my laptop,
> where the device enumerates and works in one of the 2 usb-c ports.
>
> As I mentioned the hardware that actually runs 5.10 is having issues
> even detecting my test device.
> (and while that 5.10 is far from clean mainline, the usb and network
> driver portions are more or less untouched)
>
> > 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
>
> I think this basically means the answer is "if you want this to work
> upgrade to a newer kernel".
> Which of course won't make any users happy, but oh well...
It means - what ever problem there is, it is most probably not related
to the asix driver. In kernel v5.10, there are no external dependencies
to other PHY drivers.
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-17 4:20 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
2023-10-16 18:27 ` Maciej Żenczykowski
2023-10-17 4:20 ` Oleksij Rempel [this message]
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=20231017042029.GA3539182@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