[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20260122150601.586846-1-amadeus@jmu.edu.cn>
Date: Thu, 22 Jan 2026 23:06:01 +0800
From: Chukun Pan <amadeus@....edu.cn>
To: andrew@...n.ch
Cc: amadeus@....edu.cn,
andrew+netdev@...n.ch,
davem@...emloft.net,
dlan@...nel.org,
edumazet@...gle.com,
kuba@...nel.org,
linux-kernel@...r.kernel.org,
linux-riscv@...ts.infradead.org,
netdev@...r.kernel.org,
pabeni@...hat.com,
spacemit@...ts.linux.dev,
wangruikang@...as.ac.cn
Subject: Re: [PATCH 1/1] net: spacemit: display phy driver information
Hi,
> > Print the PHY driver used and interrupt status after connection.
>
> The standard way to do this is call phy_attached_info(). Is it missing
> some information you need?
I initially used phy_attached_info(), but it was too long and printed
phydev_name() "cac80000.ethernet:01" twice:
YT8531 Gigabit Ethernet cac80000.ethernet:01: attached PHY driver (mii_bus:phy_addr=cac80000.ethernet:01, irq=POLL)
So I referenced a part of phylink_bringup_phy() to make it look better:
k1_emac cac80000.ethernet eth0: PHY driver [YT8531 Gigabit Ethernet] (irq=POLL)
k1_emac cac80000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
If we're going to use phy_attached_info(), I think `mii_bus:phy_addr`
is redundant. What's your opinion on this?
Thanks,
Chukun
Powered by blists - more mailing lists