From: Oleksij Rempel <o.rempel@pengutronix.de>
To: Carlo Szelinsky <github@szelinsky.de>
Cc: kory.maincent@bootlin.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: pse-pd: add LED trigger support
Date: Sun, 15 Mar 2026 17:58:05 +0100 [thread overview]
Message-ID: <abblHRq6Q85j5lXA@pengutronix.de> (raw)
In-Reply-To: <20260314235916.2391678-1-github@szelinsky.de>
Hi Carlo,
On Sun, Mar 15, 2026 at 12:59:16AM +0100, Carlo Szelinsky wrote:
> Add LED trigger registration and polling into the PSE core subsystem.
> Per-PI "delivering" and "enabled" triggers are registered for each PSE
> controller, with a configurable poll interval via the DT property
> "led-poll-interval-ms".
Nice work. However, this needs an architectural shift.
Since the hardware lacks interrupts, we need a core polling mechanism.
However, the PSE core already has an event notification framework. The
new polling should integrate with it instead of being LED-specific.
Please consider this approach:
- Add a generic polling loop in the PSE core. It should simulate the IRQ
handler pse_isr() by detecting state changes and pushing standard
events into the existing ntf_fifo to be processed by
pse_send_ntf_worker()
- Do not poll inside the LED code. The core state tracker should trigger
LED events as a reaction to state changes.
- Please add a define for the default polling interval. Include a
comment explaining why this specific value is chosen.
@Köry, How should we decide when to enable polling? Should we check if
no IRQ is registered? Or add a flag if the controller lacks IRQ support?
@Carlo, What controller are you using?
Best Regards,
Oleksij
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2026-03-15 16:58 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 [this message]
2026-03-15 21:12 ` Carlo Szelinsky
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=abblHRq6Q85j5lXA@pengutronix.de \
--to=o.rempel@pengutronix.de \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=github@szelinsky.de \
--cc=kory.maincent@bootlin.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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