From: Carlo Szelinsky <github@szelinsky.de>
To: o.rempel@pengutronix.de
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
github@szelinsky.de, kory.maincent@bootlin.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com
Subject: Re: [PATCH] net: pse-pd: add LED trigger support
Date: Sun, 15 Mar 2026 22:12:22 +0100 [thread overview]
Message-ID: <20260315211222.2519478-1-github@szelinsky.de> (raw)
In-Reply-To: <abblHRq6Q85j5lXA@pengutronix.de>
Hi Oleksij,
Thanks for your kind and quick feedback. I appreciate the time you invested on the weekend :-)
I will look into your suggestion and try to work on it...
Regarding your question: It is a simple POE chip (hs104) that is integrated in different cheap realtek managed switches.
It communicates only via i2c with the host and does not have any other GPIP/IRQ functionality. The problem is that the LEDs are controlled via a different (MFD) chip that communicates via i2c as well. We wanted to uncouple this as much as possible to keep things clean.
More information you find here:
https://github.com/openwrt/openwrt/pull/22245 [hs104 driver]
https://forum.openwrt.org/t/support-poe-on-hasivo-devices-s1100wp-8gt-se/244817 [discussion]
https://github.com/openwrt/openwrt/pull/21578 [MFD LED controller]
Side note: We are working hard on supporting PSE-PD for openwrt (backports to 6.12, luci, netifd support) and we plan to port other old drivers.
Do you think this simple driver for the hs104 (openwrt github PR) could get merged to mainline kernel?
best,
Carlo
next prev parent reply other threads:[~2026-03-15 21:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-14 23:59 [PATCH] net: pse-pd: add LED trigger support Carlo Szelinsky
2026-03-15 16:58 ` Oleksij Rempel
2026-03-15 21:12 ` Carlo Szelinsky [this message]
2026-03-16 6:12 ` Oleksij Rempel
2026-03-16 14:44 ` Kory Maincent
2026-03-18 20:55 ` Andrew Lunn
2026-03-21 17:55 ` Carlo Szelinsky
2026-03-23 10:30 ` Kory Maincent
2026-03-23 20:27 ` Carlo Szelinsky
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=20260315211222.2519478-1-github@szelinsky.de \
--to=github@szelinsky.de \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kory.maincent@bootlin.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.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