From: Pavel Machek <pavel@ucw.cz>
To: Marek Behun <marek.behun@nic.cz>
Cc: linux-leds@vger.kernel.org, dmurphy@ti.com
Subject: Re: [PATCH] leds: Add documentation about possible subsystem improvements
Date: Sun, 27 Sep 2020 22:33:09 +0200 [thread overview]
Message-ID: <20200927203308.GA25916@amd> (raw)
In-Reply-To: <20200925164632.22bcd5af@nic.cz>
[-- Attachment #1: Type: text/plain, Size: 1007 bytes --]
On Fri 2020-09-25 16:46:32, Marek Behun wrote:
> On Fri, 25 Sep 2020 11:33:18 +0200
> Pavel Machek <pavel@ucw.cz> wrote:
>
> > +* Command line utility to manipulate the LEDs?
> > +
> > +/sys interface is not really suitable to use by hand, should we have
> > +an utility to perform LED control?
>
> I will try to implement ledtool.
Actually.. I started something. How do you like Rust?
https://gitlab.com/tui/tui/-/blob/master/led/src/main.rs
In future, I'd like utility to accept both old and new names while we
clean them up.
It would be also nice to have useful listing mode -- name, type,
current brightness/trigger...
In future, it would be good to be able to set rgb led to particular
color.
And probably user-friendly interface to access LEDs for particular
ethernet interface would be nice.
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-09-27 20:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 9:33 [PATCH] leds: Add documentation about possible subsystem improvements Pavel Machek
2020-09-25 14:46 ` Marek Behun
2020-09-27 20:33 ` Pavel Machek [this message]
2020-09-27 23:10 ` Marek Behun
2020-09-27 23:15 ` Marek Behun
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=20200927203308.GA25916@amd \
--to=pavel@ucw.cz \
--cc=dmurphy@ti.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;
as well as URLs for NNTP newsgroup(s).