From: Pavel Machek <pavel@ucw.cz>
To: kernel list <linux-kernel@vger.kernel.org>,
hdegoede@redhat.com, andy.shevchenko@gmail.com,
mchehab+huawei@kernel.org, mauro.chehab@huawei.com,
linux-leds@vger.kernel.org
Subject: LEDs with hardware-accelerated patterns, suspend indication
Date: Wed, 26 May 2021 17:30:41 +0200 [thread overview]
Message-ID: <20210526153040.GA4537@amd> (raw)
[-- Attachment #1: Type: text/plain, Size: 1031 bytes --]
Hi!
We have hardware trigger for arbitrary patterns... but then we have
common hardware that can do few simple patterns but not arbitrary
ones.
Proposal:
Have a new hardware trigger "lpattern" that will allow selection of
patterns hardware can commonly provide. I guess that is "off", "on",
"blinking", "breathing". Maybe with variations like "slow" and "fast".
It should provide software fallbacks, so we have reference how the
patterns should look like and behave.
It is quite common to provide LED with charging activity.
Proposal:
Have a trigger called "charging" which would provide three
subdirectories "charged", "charging" and "discharging" with interface
similar to the new "lpattern" trigger.
It is very common to have combined LED for power and suspend.
Proposal:
Have a trigger called "sysstate" with three subdirectories "off", "on"
and "suspended", with interfaces similar to the "lpattern" trigger.
Best regards,
Pavel
--
http://www.livejournal.com/~pavelmachek
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next reply other threads:[~2021-05-26 15:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 15:30 Pavel Machek [this message]
2021-06-04 20:28 ` LEDs with hardware-accelerated patterns, suspend indication Hans de Goede
[not found] ` <CAMW3L+19tP_9=+8j8LLjqCGDaaVZ86UMm9NwLbbpA77zOYnr1Q@mail.gmail.com>
[not found] ` <79988fe2-7b3d-7485-131c-4f654ec6d8b8@redhat.com>
[not found] ` <CAMW3L+13O4jXyp1LVtuxhpXP_fkfWXi9JoNS8FYUAMHaJBGKZg@mail.gmail.com>
2021-06-15 12:17 ` Hans de Goede
2021-06-23 20:39 ` Pavel Machek
2021-06-25 9:18 ` Hans de Goede
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=20210526153040.GA4537@amd \
--to=pavel@ucw.cz \
--cc=andy.shevchenko@gmail.com \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=mauro.chehab@huawei.com \
--cc=mchehab+huawei@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;
as well as URLs for NNTP newsgroup(s).