linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: simon@mungewell.org
To: linux-input@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Building BarGraph with LED subsystem
Date: Fri, 16 Mar 2012 11:24:47 -0400	[thread overview]
Message-ID: <1b29a178dd288b0f17608b5815ca77a5.squirrel@mungewell.org> (raw)

Hi all,
I have a couple of questions about the (user-land) use of the LED subsystem.

I recently offered a patch for controlling the LEDs of the G27 gaming
wheel, on which the LEDs are arranged in a bar-graph of 5 to show
simulation RPM. The suggestion was to use the LED subsystem, which this
patch implements.

http://www.spinics.net/lists/linux-input/msg19747.html

Thinking further about how to about how to control this I was wondering
whether a 'threshold' trigger would be useful. This would allow the use of
value (uint?) to be compare against a threshold and the LED turned on/off
automatically.

The main benefit of doing this as a 'trigger' is that we could 'link' (or
'sync') multiple LEDs to use the same value input, thus making the
user-land stuff trivial.

Concept - ledtrig-thres would provide the controls:
   threshold - value to compare against.
   value - incoming value, if >= threshold LED is lit, if < threshold LED
is dark.
   link - 'none' (standalone comparison), or the path to the value of
another LED's value to use (ie '/sys/leds/my_device::2/value')

Comments? Is this all too complex?


Also I have a question about the default permissions on the LED controls;
Is it possible to register LEDs so that users have write permission? At
present the controls are only accessible as root.

Many thanks,
Simon.



             reply	other threads:[~2012-03-16 15:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-16 15:24 simon [this message]
2012-03-16 16:05 ` Building BarGraph with LED subsystem John Stoffel
2012-03-16 16:26   ` simon
2012-03-16 16:57     ` John Stoffel
2012-03-16 16:38   ` simon
2012-03-16 16:54     ` John Stoffel
2012-03-16 17:35       ` simon
2012-03-16 20:06         ` John Stoffel

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=1b29a178dd288b0f17608b5815ca77a5.squirrel@mungewell.org \
    --to=simon@mungewell.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.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).