Linux LED subsystem development
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Marek Behun <marek.behun@nic.cz>
Cc: Adrian Schmutzler <mail@adrianschmutzler.de>, linux-leds@vger.kernel.org
Subject: Re: How to name multiple LEDs of the same type and color
Date: Mon, 21 Sep 2020 10:31:06 +0200	[thread overview]
Message-ID: <20200921083106.GA13539@ucw.cz> (raw)
In-Reply-To: <20200921030044.304f0d5c@nic.cz>

Hi!


> > My main interest here was/is that I started to evaluate how OpenWrt can migrate from LED labels to the "new" color/function syntax and to me the rssi leds are a dedicated type that should be supported.
> > So I fear I won't be helpful for the implementation of RSSI leds in the kernel in general.

Yep, I guess staying with old "label" is the right solution for you
for now.

> > For the three leds vs. set of leds discussion: Note that we are interested in (and already do) exposing each LED to the user individually (in user-space via sysfs), so the user can redefine the purpose of the LED freely based on his/her desire. Therefore, a total abstraction of the set of LEDs as a single entity would be detrimental for us here.
> > 
> 
> This is interesting. How does this work? Better signal => faster
> blinking?

I suspect it is "no signal" -> "all LEDs off". "weak signal" -> "one
LED on", "medium signal" -> "two LEDs on", "string signal" -> "three
LEDs on".

Best regards,
								Pavel



  reply	other threads:[~2020-09-21  8:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-19 21:21 How to name multiple LEDs of the same type and color Adrian Schmutzler
2020-09-20  1:17 ` Marek Behun
2020-09-20 11:08 ` Pavel Machek
2020-09-20 23:31   ` Adrian Schmutzler
2020-09-21  1:00     ` Marek Behun
2020-09-21  8:31       ` Pavel Machek [this message]
2020-09-21  9:49         ` Adrian Schmutzler

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=20200921083106.GA13539@ucw.cz \
    --to=pavel@ucw.cz \
    --cc=linux-leds@vger.kernel.org \
    --cc=mail@adrianschmutzler.de \
    --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