> Also for user space application, I think we don't have any user space > LED library, if I'm wrong please correct me. Why there is no such > library, since we don't need it. No - rght now it is a case of "we don't have a kernel driver because we don't need one" > IMHO, firstly we should take this trigger into kernel, most time it > works as a module. But we need to define a good interface between > kernel and user space. You need the interface defined first. To do that it needs to reflect the actual hardware accelerated devices, and also to deal with resource management for those devices if necessary (eg if they can only manage one led of a set at a time). Your API can't handle things like brightness level, cross-fades (which require multiple LEDs handled as one unit) and the like. So the starting point has to be the hardware accelerated devices, whether you then support software emulation in kernel or user space is a follow on discussion. What the kernel/user API is also has to be a follow on discussion from understanding what the hardware accelerated devices can do and what their limits are. Alan -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
