[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b052c43c-5f4c-4cfa-8779-3dc66a451c4e@lunn.ch>
Date: Fri, 8 Dec 2023 14:08:35 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Marek BehĂșn <kabel@...nel.org>
Cc: Daniel Golle <daniel@...rotopia.org>, Lee Jones <lee@...nel.org>,
Pavel Machek <pavel@....cz>, Jakub Kicinski <kuba@...nel.org>,
Christian Marangi <ansuelsmth@...il.com>,
"David S. Miller" <davem@...emloft.net>,
Li Zetao <lizetao1@...wei.com>, linux-kernel@...r.kernel.org,
linux-leds@...r.kernel.org
Subject: Re: [PATCH v3 1/2] leds: trigger: netdev: extend speeds up to 10G
> What if the netdev does not have a PHY? The MAC also has speed
> information.
The ethtool API provides a list of link modes the MAC supports:
/usr/sbin/ethtool enp2s0
Settings for enp2s0:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
The MAC driver can provide this information by calling into phylib or
phylink, or it can do it some other way. In fact, none of the LED code
goes direct to the PHY when determining when to blink in software, its
all via the struct net_device.
We should use the ethtool API to determine which speed sysfs files
should exist.
Andrew
Powered by blists - more mailing lists