Messages in this thread | | | Date | Sat, 4 Sep 2004 13:09:50 +0200 | From | Pavel Machek <> | Subject | Re: [PATCH 2.6.8.1 0/2] leds: new class for led devices |
| |
Hi!
> >> function : a read/write attribute that sets the current function of > >> this led. The available options are > >> > >> timer : the led blinks on and off on a timer > >> idle : the led turns off when the system is idle and on when not idle > >> power : the led represents the current power state > >> user : the led is controlled by user space > > > >I'm afraid this is really good idea. It seems quite overengineered to > >me (and I'd be afraid that idle part slows machine). Perhaps having > >only "user" mode is better idea? > > I was only mimicing the support currently in the arm led code. > After thinking about it from a broader perspective of including GPIOs, > we should probably get rid of this function thing entirely. Just let user > space do everything... userspace can monitor sysfs and hotplug and have the > led represent power or idle or whatever.
Well, it might be okay than.
Another possibility would be to use hard-coded behaviour while system is booting/stopping and /sys-controlled behaviour while userspace is alive.
Pavel - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |