From: Paul Bolle <pebolle@tiscali.nl>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
linux-usb@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] USB: remove CONFIG_USB_PERSIST from Documentation
Date: Wed, 02 Jul 2014 11:05:56 +0200 [thread overview]
Message-ID: <1404291956.12021.23.camel@x220> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1406241317200.888-100000@iolanthe.rowland.org>
On Tue, 2014-06-24 at 13:19 -0400, Alan Stern wrote:
> On Tue, 24 Jun 2014, Paul Bolle wrote:
> > On Tue, 2014-06-24 at 10:25 -0400, Alan Stern wrote:
> > > Also, that "Later kernels" thing has already arrived. I believe it was
> > > implemented in 2.6.35.
> >
> > How does the kernel currently call the disconnect method? I can't yet
> > say for sure, and it seems silly to send a v2 dropping those lines
> > without actually knowing why they can be dropped.
>
> In drivers/usb/core/driver.c:usb_resume_complete(), which is called
> during the final "complete" phase of system suspend, interfaces that
> were marked for rebinding (because their drivers didn't have proper PM
> support) get rebound.
>
> Is that what you wanted to know?
I haven't yet discovered what the link is between rebinding and the
"disconnect" method. I'll have to study that. This is far from urgent,
so that might take me quite some time.
Thanks anyway,
Paul Bolle
next prev parent reply other threads:[~2014-07-02 9:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 10:11 [PATCH] USB: remove CONFIG_USB_PERSIST from Documentation Paul Bolle
2014-06-24 14:25 ` Alan Stern
2014-06-24 16:58 ` Paul Bolle
2014-06-24 17:19 ` Alan Stern
2014-07-02 9:05 ` Paul Bolle [this message]
2014-07-02 14:35 ` Alan Stern
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=1404291956.12021.23.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=stern@rowland.harvard.edu \
/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