From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Date: Sat, 26 Feb 2005 03:27:18 +0000 Subject: Re: event sequencing Message-Id: <20050226032717.GA10276@kroah.com> List-Id: References: <9e473391050225081838f673c7@mail.gmail.com> In-Reply-To: <9e473391050225081838f673c7@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Fri, Feb 25, 2005 at 11:18:33AM -0500, Jon Smirl wrote: > I working on adding hotplug monitor change detection code to some > framebuffer drivers. I having trouble with event sequencing. > > In my probe function I do a class_simple_device_add() to create the > class entry. Later in the probe function I do > kobject_hotplug(&info->class_device->kobj, KOBJ_MOUNT); to indicate a > monitor change. Don't use KOBJ_MOUNT, use your own, new event type. And when you do it, a netlink event will also be generated at the same time (to answer your later question.) > I'm receiving the MOUNT event before the ADD one. How can I control the order? You can't, but you can watch the sequence number to make sure you process the events in the proper order. udev does this. > Even in cases where MOUNT comes after ADD udev has not built my device > nodes yet. My MOUNT app needs to use the device node. This is my > bigger problem. Sit and spin, waiting for the device node to show up :) thanks, greg k-h ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel