From: simon@mungewell.org
To: John Stoffel <john@stoffel.org>
Cc: simon@mungewell.org, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Building BarGraph with LED subsystem
Date: Fri, 16 Mar 2012 12:26:56 -0400 [thread overview]
Message-ID: <8107d8a0e50b64dd45dc749da87b2c7b.squirrel@mungewell.org> (raw)
In-Reply-To: <20323.25792.171143.809563@quad.stoffel.home>
> 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
>
So what would be the best way to achieve this (once the code gets into
kernel)? I mean so that 'Jane Doe' get the LEDs working when she plugs in
her wheel...
At present the patch uses the devices ID's to register the LED's. ie.
--
Mar 14 14:57:35 ubuntu kernel: [ 6462.204185] Registered led device:
0003:046D:C294.0009::RPM1
Mar 14 14:57:35 ubuntu kernel: [ 6462.204251] Registered led device:
0003:046D:C294.0009::RPM2
Mar 14 14:57:35 ubuntu kernel: [ 6462.204301] Registered led device:
0003:046D:C294.0009::RPM3
Mar 14 14:57:35 ubuntu kernel: [ 6462.204354] Registered led device:
0003:046D:C294.0009::RPM4
Mar 14 14:57:35 ubuntu kernel: [ 6462.204402] Registered led device:
0003:046D:C294.0009::RPM5
--
Simon.
next prev parent reply other threads:[~2012-03-16 16:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 15:24 Building BarGraph with LED subsystem simon
2012-03-16 16:05 ` John Stoffel
2012-03-16 16:26 ` simon [this message]
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=8107d8a0e50b64dd45dc749da87b2c7b.squirrel@mungewell.org \
--to=simon@mungewell.org \
--cc=john@stoffel.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).