On Mon, 2012-03-19 at 17:33 +0100, Jiri Kosina wrote: > On Wed, 14 Mar 2012, simon@xxxxxxxxxxxxx wrote: > > > > I'm posting this more as a 'Request for Comments' following on from > > > Michal's patch this morning. > > > > One thing I note sure about is permissions, the LEDs register as > > -- > > 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 > > -- > > > > But I have to be root to perform > > -- > > root@ubuntu:/sys/devices/pci0000:00/0000:00:11.0/0000:02:00.0/usb2/2-1/2-1:1.0/0003:046D:C294.0009/leds/0003:046D:C294.0009::RPM1# > > echo 1 > brightness > > -- > > > > Is it possible to register so that all/any user can control the LED status? > > Looking at the code, I don't think that's possible. Adding Richard to CC, > he definitely might have an opinion on this. Whilst there is kernel side API you could potentially (ab)use, its not encouraged or easy to do with the LED class attributes. Its really a userspace policy issue. You can change the permissions on the files in sysfs to reflect the access you require from something like udev. Cheers, Richard -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
