From: Olaf Hering <olh@suse.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: correct sequencing between driver and hotplug event
Date: Mon, 09 Feb 2004 18:20:30 +0000 [thread overview]
Message-ID: <20040209182030.GA29577@suse.de> (raw)
In-Reply-To: <20040209175502.19371.qmail@web14906.mail.yahoo.com>
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
prev parent reply other threads:[~2004-02-09 18:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-09 17:55 correct sequencing between driver and hotplug event Jon Smirl
2004-02-09 18:20 ` Olaf Hering [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040209182030.GA29577@suse.de \
--to=olh@suse.de \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.