Re: [PATCH] nesting class_device in sysfs to solve world peace
From: Adam Belay
Date: Mon Oct 10 2005 - 22:59:36 EST
On Fri, Sep 30, 2005 at 12:32:49AM -0500, Dmitry Torokhov wrote:
> I firmly believe that creating sub-classes (which solves hotplug issues)
> and linking sub-class devices to their parent via 'device' link, much like
> we link top-level class device to their physical parent devices (which
> solves 2, 3 and 4) is much cleanier way. It provides everything that your
> implementation does plus allows different views useful for other tasks
> besides udev.
Could you please outline the class device requirements for the input
subsystem? Specifically I'm interested in the class -> subclass layering.
I'm trying to understand what is needed and how the input subsystem should
I can think of other subystems that might benefit from class layering. One
example might be wireless cards: net and net/wireless. In this case devices
that belong to class "wireless" would inherit all of the capabilities of the
"net" class and also implement the "wireless"-specific feature set.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/