From: Andrew Lunn <andrew@lunn.ch>
To: Pavel Machek <pavel@ucw.cz>
Cc: Christian Marangi <ansuelsmth@gmail.com>,
Lee Jones <lee@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
Gregory Clement <gregory.clement@bootlin.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
John Crispin <john@phrozen.org>,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [net-next PATCH v6 16/16] arm: mvebu: dt: Add PHY LED support for 370-rd WAN port
Date: Thu, 6 Apr 2023 15:54:14 +0200 [thread overview]
Message-ID: <ebaedccc-a73b-48fc-8735-c0567d899d5c@lunn.ch> (raw)
In-Reply-To: <ZC6OZ2f/NLJxZgle@duo.ucw.cz>
> I don't think basing stuff on position is reasonable. (And am not sure
> if making difference between MAC and PHY leds is good idea).
>
> Normally, there's ethernet port with two LEDs, one is usually green
> and indicates link, second being yellow and indicates activity,
> correct?
Nope. I have machines with 1, 2 or 3 LEDs. I have green, yellow, white
and red LEDs.
Part of the problem is 802.3 says absolutely nothing about LEDs. So
every vendor is free to do whatever why want. There is no
standardisation at all. So we have to assume every vendor does
something different.
> On devices like ADSL modems, there is one LED per port, typically on
> with link and blinking with activity.
>
> Could we use that distinction instead? (id):green:link,
> (id):yellow:activity, (id):?:linkact -- for combined LED as it seems.
>
> Are there any other common leds? I seem to remember "100mbps" lights
> from time where 100mbit was fast...?
But what about 2.5G, 5G, 10G, 40G... And 10Mbps for automotive. And
collision for 1/2 duplex, which is making a bit of a comeback in
automotive.
Plus, we are using ledtrig-netdev. A wifi device is a netdev. A CAN
bus devices is a netdev. Link speed has a totally different meaning
for 802.11 and CAN.
You are also assuming the LEDs have fixed meaning. But they are not
fixed, they mean whatever the ledtrig-netdev is configured to make
them blink. I even have one of my boxes blinking heartbeat, because
if has a habit of crashing... And i think for Linux LEDs in general,
we should not really tie an LED to a meaning. Maybe tie it to a label
on the case, but the meaning of an LED is all about software, what
ledtrig- is controlling it.
As to differentiating MAC and PHY, we need to, because as i said, both
could offer LEDs. Generally, Ethernet switches have LED controllers
per MAC port. Most switches have internal PHYs, and those PHYs don't
have LED controllers. However, not all ports have internal PHYs, there
can be external PHYs with its own LED controller. So in that case,
both the MAC and the PHY could register an LED controller for the same
netdev. It comes down to DT to indicate what LED controllers are
actually wired to an LED.
Andrew
next prev parent reply other threads:[~2023-04-06 13:55 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 14:10 [net-next PATCH v6 00/16] net: Add basic LED support for switch/phy Christian Marangi
2023-03-27 14:10 ` [net-next PATCH v6 01/16] net: dsa: qca8k: move qca8k_port_to_phy() to header Christian Marangi
2023-04-13 14:05 ` Florian Fainelli
2023-03-27 14:10 ` [net-next PATCH v6 02/16] net: dsa: qca8k: add LEDs basic support Christian Marangi
2023-03-27 14:10 ` [net-next PATCH v6 03/16] net: dsa: qca8k: add LEDs blink_set() support Christian Marangi
2023-04-13 14:06 ` Florian Fainelli
2023-03-27 14:10 ` [net-next PATCH v6 04/16] leds: Provide stubs for when CLASS_LED & NEW_LEDS are disabled Christian Marangi
2023-04-13 13:58 ` Florian Fainelli
2023-03-27 14:10 ` [net-next PATCH v6 05/16] net: phy: Add a binding for PHY LEDs Christian Marangi
2023-03-27 14:10 ` [net-next PATCH v6 06/16] net: phy: phy_device: Call into the PHY driver to set LED brightness Christian Marangi
2023-04-13 13:57 ` Florian Fainelli
2023-04-12 23:11 ` Christian Marangi
2023-04-13 14:04 ` Florian Fainelli
2023-04-13 14:43 ` Andrew Lunn
2023-04-13 14:48 ` Andrew Lunn
2023-03-27 14:10 ` [net-next PATCH v6 07/16] net: phy: marvell: Add software control of the LEDs Christian Marangi
2023-04-13 13:55 ` Florian Fainelli
2023-03-27 14:10 ` [net-next PATCH v6 08/16] net: phy: phy_device: Call into the PHY driver to set LED blinking Christian Marangi
2023-04-13 13:56 ` Florian Fainelli
2023-03-27 14:10 ` [net-next PATCH v6 09/16] net: phy: marvell: Implement led_blink_set() Christian Marangi
2023-04-13 13:58 ` Florian Fainelli
2023-03-27 14:10 ` [net-next PATCH v6 10/16] dt-bindings: leds: Document support for generic ethernet LEDs Christian Marangi
2023-03-31 20:09 ` Rob Herring
2023-03-27 14:10 ` [net-next PATCH v6 11/16] dt-bindings: net: ethernet-controller: Document support for LEDs node Christian Marangi
2023-03-27 14:10 ` [net-next PATCH v6 12/16] dt-bindings: net: dsa: qca8k: add LEDs definition example Christian Marangi
2023-04-06 14:10 ` Rob Herring
2023-04-12 22:42 ` Christian Marangi
2023-04-13 13:49 ` Andrew Lunn
2023-03-27 14:10 ` [net-next PATCH v6 13/16] ARM: dts: qcom: ipq8064-rb3011: Drop unevaluated properties in switch nodes Christian Marangi
2023-04-09 16:15 ` Jonathan McDowell
2023-03-27 14:10 ` [net-next PATCH v6 14/16] ARM: dts: qcom: ipq8064-rb3011: Add Switch LED for each port Christian Marangi
2023-03-27 14:10 ` [net-next PATCH v6 15/16] dt-bindings: net: phy: Document support for LEDs node Christian Marangi
2023-03-27 14:10 ` [net-next PATCH v6 16/16] arm: mvebu: dt: Add PHY LED support for 370-rd WAN port Christian Marangi
2023-03-28 8:31 ` Pavel Machek
2023-03-28 11:59 ` Andrew Lunn
2023-04-03 19:54 ` Pavel Machek
2023-04-04 19:52 ` Andrew Lunn
2023-04-06 9:18 ` Pavel Machek
2023-04-06 13:54 ` Andrew Lunn [this message]
2023-04-03 18:46 ` Rob Herring
2023-04-03 19:28 ` Andrew Lunn
2023-03-28 1:46 ` [net-next PATCH v6 00/16] net: Add basic LED support for switch/phy Jakub Kicinski
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=ebaedccc-a73b-48fc-8735-c0567d899d5c@lunn.ch \
--to=andrew@lunn.ch \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=ansuelsmth@gmail.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=gregory.clement@bootlin.com \
--cc=hkallweit1@gmail.com \
--cc=john@phrozen.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=pavel@ucw.cz \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.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®