LED devices

[Johannes Berg]

On Fri, 2007-06-01 at 15:48 +0100, Richard Purdie wrote:

> Its probably quite feasible now without too many changes. There is
> already the notion of a "default_trigger", all you'd need is to add some
> kind of optional function pointer to a 'trigger_matches' function and
> find a way to deal with any conflicts which replaced/complimented that.

Hm.

> Triggers are fundamentally a kernel entity and the matching should
> probably happen in the kernel at least by default although its obviously
> totally configurable in userspace too through the existing sysfs
> entries.

Right.

> For contrast, another possibility is we expose the default_trigger
> string, e.g. "ieee80211:%s:rx" and then have userspace set the trigger
> accordingly but that somehow seems more clunky, especially when the
> kernel can handle things itself at the moment with next to no code.

No, the problem I actually have with the trigger names is that they're
fixed, and not actual device entities, but my triggers correspond to a
device. And it's complicated by the fact that those devices can be
renamed, which the trigger won't follow.

johannes
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part
Url : http://lists.freedesktop.org/archives/hal/attachments/20070601/0db95388/attachment-0001.pgp