[lkml]   [2006]   [Jul]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Implement class_device_update_dev() function
On Sat, 2006-07-08 at 11:27 +0200, Marcel Holtmann wrote:
> > > > But userspace should also find out about this change, and this patch
> > > > prevents that from happening. What about just tearing down the class
> > > > device and creating a new one? That way userspace knows about the new
> > > > linkage properly, and any device naming and permission issues can be
> > > > handled anew?
> > >
> > > This won't work for Bluetooth. We create the TTY and its class device
> > > with tty_register_device() and then the device node is present. Then at
> > > some point later we open that device and the Bluetooth connection gets
> > > established. Only when the connection has been established we know the
> > > device that represents it. So tearing down the class device and creating
> > > a new one will screw up the application that is using this device node.
> > >
> > > Would reissuing the uevent of the class device help here?
> >
> I am not that familiar with the internals of kobject. Can you give me an
> example on how to do that?

Just send another event (but not add or remove), for the already created
object. CPU hotplug uses ONLINE/OFFLINE, and we also use it to get
notified when the device mapper table is set up (not upstream). Udev is
able to update symlinks, or run actions on "online" events if asked


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-07-08 15:03    [W:0.048 / U:0.304 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site