From: Heinrich Toews <ht@twx-software.de>
To: netdev@vger.kernel.org
Cc: andrew@lunn.ch, f.fainelli@gmail.com, olteanv@gmail.com,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org
Subject: [PATCH net-next v1 0/3] net: dsa: microchip: add single-led-mode support
Date: Wed, 28 Jan 2026 14:38:30 +0100 [thread overview]
Message-ID: <20260128133842.1173406-1-ht@twx-software.de> (raw)
This series adds support for single LED mode to KSZ9477 switches.
The first patch adds the YAML device tree binding documentation for the
new 'microchip,single-led-mode' property.
The second patch implements the mode configuration in the ksz_common
driver, including a necessary hardware workaround for Errata Module 19
(DS80000754F), which requires an additional write to a debug register to
ensure proper LED activity.
Heinrich Toews (3):
dt-bindings: net: dsa: microchip: add microchip,single-led-mode flag
net: phy: micrel: add flag for KSZ9477 LED erratum
net: dsa: microchip: add single-led-mode support for KSZ9477
.../bindings/net/dsa/microchip,ksz.yaml | 6 ++++
drivers/net/dsa/microchip/ksz_common.c | 34 +++++++++++++++++++
drivers/net/dsa/microchip/ksz_common.h | 4 +++
include/linux/micrel_phy.h | 1 +
4 files changed, 45 insertions(+)
--
2.52.0
next reply other threads:[~2026-01-28 13:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-28 13:38 Heinrich Toews [this message]
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)
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
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=20260128133842.1173406-1-ht@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