From: Pavel Machek <pavel@ucw.cz>
To: "Uwe Kleine-König" <uwe@kleine-koenig.org>
Cc: Jacek Anaszewski <jacek.anaszewski@gmail.com>,
linux-kernel@vger.kernel.org,
Tomas Hlavacek <tomas.hlavacek@nic.cz>
Subject: Re: led: hw-trigger, global brightness and multi-colored leds
Date: Wed, 2 May 2018 23:21:05 +0200 [thread overview]
Message-ID: <20180502212105.GA9869@amd> (raw)
In-Reply-To: <20180502151108.GA25970@taurus.defre.kleine-koenig.org>
[-- Attachment #1: Type: text/plain, Size: 1409 bytes --]
Hi!
> on the Turris Omnia[1] the LEDs are controllable via an i2c device. Each
> LED can be either in "manual mode" or in a mode I'd call "native mode"
> which is the default. In this native mode the LED being on or off
> depends on an input line that is controlled by another hardware. So a
> LED signals for example activity on the WAN ethernet port without any
> software intervention, but can be used as a normal LED, too, when in
> "manual mode" where it can be switched on and off by a register
> write.
"Native mode" is quite common. We have it for example on Nokia N900
here (charger has hw option to automatically control the LED).
I believe reasonable solution would be to have "hardware" trigger, and
have it selected by default. When active, LED would be controlled by
hardware.
> Another feature of the LED device is that there is a global brightness
> register that influences all LED's brightness (if on) independent of the
> operating mode.
We can't describe that easily.
> Further the color of each LED can be set to an RGB triplet.
We normally handle RGB LED as three independend LEDs, like
notify::red, notify::green, notify::blue. Again, example is Nokia N900
or Motorola Droid 4.
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:[~2018-05-02 21:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-02 15:11 led: hw-trigger, global brightness and multi-colored leds Uwe Kleine-König
2018-05-02 21:21 ` Pavel Machek [this message]
2018-05-03 18:49 ` Uwe Kleine-König
2018-05-03 21:14 ` Jacek Anaszewski
2018-05-03 21:52 ` Pavel Machek
2018-05-24 22:08 ` Tomas Hlavacek
2018-05-25 6:08 ` Turris Omnia firmware possibilities [Was: Re: led: hw-trigger, global brightness and multi-colored leds] Uwe Kleine-König
2018-05-25 14:02 ` Tomas Hlavacek
2018-05-25 18:50 ` Pavel Machek
2018-08-14 7:11 ` Uwe Kleine-König
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=20180502212105.GA9869@amd \
--to=pavel@ucw.cz \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tomas.hlavacek@nic.cz \
--cc=uwe@kleine-koenig.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.