On Tue, Dec 7, 2010 at 19:33, Greg KH <gregkh@suse.de> wrote:
Sounds a bit like the driver should create its own child device with
its own properties, instead of mangling around with attributes at a
device it binds to.
Sebastian, care to be more specific about the problem and bus in
question. We should avoid new generic events. In some special cases,
sending out 'change' from the driver might be acceptable, but it's
usually not what we would suggest.
Kay
--