public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: "Heinrich Töws (TWx)" <ht@twx-software.de>
To: Andrew Lunn <andrew@lunn.ch>
Cc: netdev@vger.kernel.org, f.fainelli@gmail.com, olteanv@gmail.com,
	robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org
Subject: Re: [PATCH v1 1/3] dt-bindings: net: dsa: microchip: add microchip,single-led-mode flag
Date: Wed, 28 Jan 2026 16:10:41 +0100	[thread overview]
Message-ID: <9090d12e-e85e-4827-9dc3-5bbece12c50d@twx-software.de> (raw)
In-Reply-To: <6871816c-2732-4c5f-9f10-1f9773d5f23d@lunn.ch>

Hi Andrew,

Am 28.01.26 um 14:59 schrieb Andrew Lunn:
> Are there other blinking modes? If the LED is capable of more, you
> should be using /sys/class/leds and the netdev trigger. If the only
> thing it can indicate is link and activity, this approach is O.K.

I re-checked the datasheet (DS00002392). The KSZ9477 PHY ports indeed 
have two pins, but they are not general-purpose. The term "programmable" 
in the datasheet refers only to switching between two fixed 
hardware-mapped modes via MMD:

1. Tri-Color Dual-LED Mode (Default): The pins LEDx_1 and LEDx_0 work in 
conjunction to indicate link speed (10/100/1000) and activity. For 
example, 10BASE-T status is indicated by both pins working together.

2. Single-LED Mode: Here, the logic is simplified so that LEDx_1 
indicates Link and LEDx_0 indicates Activity.

There is no "Manual Mode" or "GPIO Mode" for these pins. They are driven 
by a fixed internal state machine. Since we cannot control the pins' 
brightness or trigger events independently from the PHY's hardcoded 
logic, the netdev trigger or the LED class cannot be used to emulate 
this behavior.

> Is there a dual LED mode? Triple LED mode? What happens if this
> property is not found?

If the property is not found, the switch remains in its default 
"Tri-Color Dual-LED Mode".

I will clarify this in the description for v2.

Thanks,Heinrich.

  reply	other threads:[~2026-01-28 15:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-28 13:38 [PATCH net-next v1 0/3] net: dsa: microchip: add single-led-mode support Heinrich Toews
2026-01-28 13:38 ` [PATCH v1 1/3] dt-bindings: net: dsa: microchip: add microchip,single-led-mode flag Heinrich Toews
2026-01-28 13:59   ` Andrew Lunn
2026-01-28 15:10     ` Heinrich Töws (TWx) [this message]
2026-01-28 15:22       ` Andrew Lunn
2026-01-28 15:53         ` Heinrich Töws (TWx)
2026-01-28 18:06   ` Rob Herring
2026-02-03 10:22     ` Heinrich Toews
2026-01-28 13:38 ` [PATCH v1 2/3] net: phy: micrel: add flag for KSZ9477 LED erratum Heinrich Toews
2026-01-28 13:38 ` [PATCH v1 3/3] net: dsa: microchip: add single-led-mode support for KSZ9477 Heinrich Toews
2026-01-29  2:25   ` [v1,3/3] " Jakub Kicinski
2026-02-03 11:13     ` Heinrich Toews
  -- strict thread matches above, loose matches on Subject: below --
2026-01-30 19:19 [PATCH v1 1/3] dt-bindings: net: dsa: microchip: add microchip,single-led-mode flag Tim Harvey
2026-02-03 13:44 ` Heinrich Toews

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=9090d12e-e85e-4827-9dc3-5bbece12c50d@twx-software.de \
    --to=ht@twx-software.de \
    --cc=andrew@lunn.ch \
    --cc=f.fainelli@gmail.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=robh+dt@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