From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: [linux-usb-devel] Re: hotplugging to deal with firmware download
Date: Tue, 04 Jun 2002 19:44:06 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-102322046825349@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-102297360623547@msgid-missing>
>>>I see no plan to do it with the present power management system.
>>>The devices are simply assumed to switch from suspended to working
>>>in kernel space. Suspended may mean off here.
>>
>>Well, the usb device drivers _do_ need individual suspend()/resume()
>>callbacks. The "new device model" stuff exists in part to ensure
>>that devices get those calls appropriately.
>
> I agree. But usbcore should help as far as possible.
What were you thinking would transform the "device model" level
suspend/resume calls into USB level ones? :)
>>For example, suspending a bus-powered hub would need to morph into
>>disconnecting the devices it could no longer power ... and in your
>>case, suspending a network device that discards its firmware would
>>also need to morph into a disconnect.
>
> That's exactly what you must _not_ do, you need to retain the information
> which devices was on which port to resume correctly.
Why would that be? In those cases, the device MUST re-enumerate from
scratch, there will be no USB state to resume. In those cases the
devices can't suspend; they can only disconnect/reconnect.
And it'd be pointless, since if any device driver wants to save
information about devices across reconnects -- like usb-storage does
today -- it has all the tools it needs to do that already. There's
no need to bloat the core with such stuff.
Given that userspace tools can already be used to make network device
names be pseudo-stable ("eth2" is always the one with address NN), and
network drivers can even request specific names ("eth3") I don't see
any reason any network device driver should want such functionality.
- Dave
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_______________________________________________
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
next prev parent reply other threads:[~2002-06-04 19:44 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-01 23:16 [linux-usb-devel] Re: hotplugging to deal with firmware download Brad Hards
2002-06-02 5:50 ` Oliver Neukum
2002-06-02 8:19 ` Oliver Neukum
2002-06-02 11:11 ` Brad Hards
2002-06-02 17:16 ` David Brownell
2002-06-02 21:59 ` Oliver Neukum
2002-06-02 22:21 ` Brad Hards
2002-06-03 4:18 ` Oliver Neukum
2002-06-03 17:52 ` Greg KH
2002-06-03 21:00 ` Oliver Neukum
2002-06-03 21:55 ` Greg KH
2002-06-03 22:02 ` David Brownell
2002-06-03 22:26 ` Oliver Neukum
2002-06-03 22:35 ` Greg KH
2002-06-03 22:37 ` Greg KH
2002-06-03 22:48 ` Oliver Neukum
2002-06-03 22:58 ` Oliver Neukum
2002-06-03 23:05 ` Greg KH
2002-06-03 23:30 ` Oliver Neukum
2002-06-03 23:40 ` Greg KH
2002-06-04 8:06 ` Oliver Neukum
2002-06-04 19:32 ` David Brownell
2002-06-04 19:44 ` David Brownell [this message]
2002-06-05 11:45 ` Oliver Neukum
2002-06-05 14:19 ` David Brownell
2002-06-05 14:32 ` Oliver Neukum
2002-06-05 14:54 ` David Brownell
2002-06-05 21:48 ` Oliver Neukum
2002-06-06 0:25 ` David Brownell
2002-06-06 9:04 ` Andries.Brouwer
2002-06-06 12:54 ` Oliver Neukum
2002-06-06 14:55 ` Oliver Neukum
2002-06-06 17:16 ` David Brownell
2002-06-06 19:19 ` Andries.Brouwer
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=marc-linux-hotplug-102322046825349@msgid-missing \
--to=david-b@pacbell.net \
--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).