linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: usb coldplug problem
Date: Mon, 01 Dec 2008 15:29:20 +0000	[thread overview]
Message-ID: <20081201152920.GA12600@kroah.com> (raw)
In-Reply-To: <403A9FAC.2010904@free.fr>

On Mon, Dec 01, 2008 at 03:21:56PM +0000, Bernd Porr wrote:
> Hi!
>
> It's not that easy. The actual udev event triggers comedi_config which does 
> _also_ the firmware upload on the side. Even if I upload the firmware via 
> sysfs I still need to run comedi_config to set up the comedi device. 

Then do it like other USB devices do it:
	- usb probe function calls request firmware
	- after request firmware succeeds, then initialize the comedi
	  interface

That way the driver will work like all other Linux USB devices do :)

> Therefore it's simpler to do it via comedi_config as this supports firmware 
> upload anyway and people can also do it manually if udev is not supported, 
> for example on embedded systems.

udev is supported everywhere.  It's in my daughter's cell phone (the
number 1 selling phone in the USA this year) and if udev isn't there,
than the "generic" way of having hotplug handle firmware events is still
going to work properly for you.

thanks,

greg k-h

  parent reply	other threads:[~2008-12-01 15:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-24  0:49 USB coldplug problem Lionel VICTOR
2008-12-01  8:46 ` usb " Bernd Porr
2008-12-01 14:35 ` Greg KH
2008-12-01 15:21 ` Bernd Porr
2008-12-01 15:29 ` Greg KH [this message]
2008-12-01 18:27 ` Bernd Porr
2008-12-03  6:55 ` Greg KH
2008-12-03  8:40 ` Bernd Porr
2008-12-03  9:18 ` Kay Sievers
2008-12-03 10:28 ` Sujit Karataparambil
2008-12-03 11:13 ` Bernd Porr
2008-12-03 11:46 ` Sujit Karataparambil
2008-12-03 14:59 ` Greg KH

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=20081201152920.GA12600@kroah.com \
    --to=greg@kroah.com \
    --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 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).