From: Pavel Machek <pavel@ucw.cz>
To: Marek Behun <marek.behun@nic.cz>
Cc: Jacek Anaszewski <jacek.anaszewski@gmail.com>,
linux-leds@vger.kernel.org
Subject: Re: HW LED triggers again
Date: Sat, 21 Mar 2020 11:23:15 +0100 [thread overview]
Message-ID: <20200321102315.GA9324@amd> (raw)
In-Reply-To: <20200320204308.411f8d68@nic.cz>
[-- Attachment #1: Type: text/plain, Size: 985 bytes --]
Hi!
> I want to open the discussions about HW LED triggers again.
> The last time (which was almost a year ago, sorry for that) I proposed
> an API which used the same sysfs trigger file as for regular trigger
> setting, but the HW triggers were prefixed with "hw:" (and each LED
> classdev can have different ones).
>
> You wrote:
...
> I would still like to go this way, so my answer to this questions is:
> - IMO this is simpler for users and existing scripts
> - the idea is that it should no be possible to set a software trigger
> and a hardware trigger at the same time (this would just end up in
> more complications), and introducing special hw_trigger file or
> something could make users think that you can
As usual, devil is in the details, but so far, I like the proposal.
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2020-03-21 10:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 19:43 HW LED triggers again Marek Behun
2020-03-21 10:23 ` Pavel Machek [this message]
2020-03-21 19:26 ` Jacek Anaszewski
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=20200321102315.GA9324@amd \
--to=pavel@ucw.cz \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-leds@vger.kernel.org \
--cc=marek.behun@nic.cz \
/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