From: "John Stoffel" <john@stoffel.org>
To: simon@mungewell.org
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Building BarGraph with LED subsystem
Date: Fri, 16 Mar 2012 12:05:20 -0400 [thread overview]
Message-ID: <20323.25792.171143.809563@quad.stoffel.home> (raw)
In-Reply-To: <1b29a178dd288b0f17608b5815ca77a5.squirrel@mungewell.org>
simon> I have a couple of questions about the (user-land) use of the
simon> LED subsystem.
simon> I recently offered a patch for controlling the LEDs of the G27 gaming
simon> wheel, on which the LEDs are arranged in a bar-graph of 5 to show
simon> simulation RPM. The suggestion was to use the LED subsystem, which this
simon> patch implements.
simon> http://www.spinics.net/lists/linux-input/msg19747.html
simon> Thinking further about how to about how to control this I was wondering
simon> whether a 'threshold' trigger would be useful. This would allow the use of
simon> value (uint?) to be compare against a threshold and the LED turned on/off
simon> automatically.
simon> The main benefit of doing this as a 'trigger' is that we could 'link' (or
simon> 'sync') multiple LEDs to use the same value input, thus making the
simon> user-land stuff trivial.
While making the kernel more complex... esp for a feature which is of
such limited use. Do it all in userland, it's easier, you can use
floating point math, etc. And to test changes, you don't have to
recompile a module and unload/reload it, etc.
Keeping as much of this in userland is better.
simon> Also I have a question about the default permissions on the LED
simon> controls; Is it possible to register LEDs so that users have
simon> write permission? At present the controls are only accessible
simon> as root.
udev is the answer here. You probably want to make it so that the
LEDs are open to the user logged into the system console or currently
active Xsession.
John
next prev parent reply other threads:[~2012-03-16 16:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 15:24 simon
2012-03-16 16:05 ` John Stoffel [this message]
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=20323.25792.171143.809563@quad.stoffel.home \
--to=john@stoffel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=simon@mungewell.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
all inboxes | Powered by JetHome®