From: Andrew Lunn <andrew@lunn.ch>
To: Jose Ignacio Tornos Martinez <jtornosm@redhat.com>
Cc: UNGLinuxDriver@microchip.com, davem@davemloft.net,
edumazet@google.com, gregkh@linuxfoundation.org, kuba@kernel.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
lucas.demarchi@intel.com, mcgrof@kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com,
woojung.huh@microchip.com
Subject: Re: [PATCH] net: usb: lan78xx: add weak dependency with micrel phy module
Date: Mon, 29 Jul 2024 14:42:12 +0200 [thread overview]
Message-ID: <c169a84d-d0e5-4fdf-a112-01ac819447e4@lunn.ch> (raw)
In-Reply-To: <20240729083739.11360-1-jtornosm@redhat.com>
On Mon, Jul 29, 2024 at 10:37:38AM +0200, Jose Ignacio Tornos Martinez wrote:
> Hello Andrew,
>
> I like the idea from Jakub, reading the associated phy from the hardware
> in some way, although reading your last comments I don't know if it could
> be possible for all the cases.
> Let me ask you about this to understand better, if present,
> always reading /sys/bus/mdio_bus/devices/*/phy_id,
> could it be enough to get the possible related phy?
> And after this get the related phy module?
There should be sufficient information in /sys. eg.
$ cat /sys/class/net/enp1s0/phydev/phy_id
0x001cc914
So enp1s0 probed a PHY using the ID 0x001cc914. Turn that into binary
and you get 0000 0000 0001 1100 1100 1001 0001 0100. Look that up in alias.
alias mdio:0000000000011100110010?????????? realtek
So you need to realtek PHY driver for my enp1s0.
Andrew
prev parent reply other threads:[~2024-07-29 12:42 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-24 10:23 Jose Ignacio Tornos Martinez
2024-07-24 11:49 ` Andrew Lunn
2024-07-24 13:36 ` Greg KH
2024-07-24 14:46 ` Jose Ignacio Tornos Martinez
2024-07-24 15:31 ` Florian Fainelli
2024-07-24 14:54 ` Jose Ignacio Tornos Martinez
2024-07-24 16:10 ` Jose Ignacio Tornos Martinez
2024-07-24 22:57 ` Andrew Lunn
2024-07-25 4:25 ` Lucas De Marchi
2024-07-25 4:42 ` Florian Fainelli
2024-07-25 6:50 ` Lucas De Marchi
2024-07-25 9:53 ` Paolo Abeni
2024-07-26 11:33 ` Andrew Lunn
2024-07-26 12:15 ` Jose Ignacio Tornos Martinez
2024-07-26 20:59 ` Andrew Lunn
2024-07-27 17:15 ` Dragan Simic
2024-07-27 23:29 ` Andrew Lunn
2024-07-28 14:10 ` Dragan Simic
2024-07-28 19:45 ` Andrew Lunn
2024-07-28 20:46 ` Dragan Simic
2024-07-28 20:57 ` Andrew Lunn
2024-07-29 4:43 ` Dragan Simic
2024-07-29 6:13 ` Greg KH
2024-07-29 6:29 ` Dragan Simic
2024-07-29 8:34 ` Jose Ignacio Tornos Martinez
2024-07-29 9:28 ` Dragan Simic
2024-07-29 12:32 ` Jose Ignacio Tornos Martinez
2024-07-29 18:56 ` Andrew Lunn
2024-07-30 7:55 ` Jose Ignacio Tornos Martinez
2024-07-28 7:37 ` Masahiro Yamada
2024-07-28 9:53 ` Dragan Simic
2024-07-26 14:49 ` Jakub Kicinski
2024-07-26 21:15 ` Andrew Lunn
2024-07-29 8:37 ` Jose Ignacio Tornos Martinez
2024-07-29 12:42 ` Andrew Lunn [this message]
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=c169a84d-d0e5-4fdf-a112-01ac819447e4@lunn.ch \
--to=andrew@lunn.ch \
--cc=UNGLinuxDriver@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=jtornosm@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=mcgrof@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=woojung.huh@microchip.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
all inboxes | Powered by JetHome®