* correct sequencing between driver and hotplug event
@ 2004-02-09 17:55 Jon Smirl
2004-02-09 18:20 ` Olaf Hering
0 siblings, 1 reply; 2+ messages in thread
From: Jon Smirl @ 2004-02-09 17:55 UTC (permalink / raw)
To: linux-hotplug
1) my DRM driver loads
2) it generates a hotplug event
3) hotplug resets the hardware
4) driver registers I2C
5) EEPROM driver picks up EDID data on I2C bus.
Right now my steps 4&5 are happening before step 3; so they don't work since the
hardware needs to be initialized.
What's the right way to get the correct sequencing? Is there a way for the
driver to know when the hotplug event has finished? Or should I do an explicit
IOCTL from the hotplug program back to the driver?
==Jon Smirl
jonsmirl@yahoo.com
__________________________________
Do you Yahoo!?
Yahoo! Finance: Get your refund fast by filing online.
http://taxes.yahoo.com/filing.html
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: correct sequencing between driver and hotplug event
2004-02-09 17:55 correct sequencing between driver and hotplug event Jon Smirl
@ 2004-02-09 18:20 ` Olaf Hering
0 siblings, 0 replies; 2+ messages in thread
From: Olaf Hering @ 2004-02-09 18:20 UTC (permalink / raw)
To: linux-hotplug
On Mon, Feb 09, Jon Smirl wrote:
> 1) my DRM driver loads
> 2) it generates a hotplug event
> 3) hotplug resets the hardware
> 4) driver registers I2C
> 5) EEPROM driver picks up EDID data on I2C bus.
>
> Right now my steps 4&5 are happening before step 3; so they don't work since the
> hardware needs to be initialized.
>
> What's the right way to get the correct sequencing? Is there a way for the
> driver to know when the hotplug event has finished? Or should I do an explicit
> IOCTL from the hotplug program back to the driver?
Maybe do it via a sysfs file like the firmware.agent uploads its stuff?
lock, upload, unlock. register i2c.
--
USB is for mice, FireWire is for men!
sUse lINUX ag, n√úRNBERG
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2004-02-09 18:20 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-02-09 17:55 correct sequencing between driver and hotplug event Jon Smirl
2004-02-09 18:20 ` Olaf Hering
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).