[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <s5hvbfm3rbm.wl-tiwai@suse.de>
Date: Thu, 21 May 2015 17:04:13 +0200
From: Takashi Iwai <tiwai@...e.de>
To: Alan Stern <stern@...land.harvard.edu>
Cc: Marcel Holtmann <marcel@...tmann.org>,
Laura Abbott <labbott@...hat.com>,
Oliver Neukum <oneukum@...e.com>,
Ming Lei <ming.lei@...onical.com>,
"David S. Miller" <davem@...emloft.net>,
Laura Abbott <labbott@...oraproject.org>,
Johan Hedberg <johan.hedberg@...il.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
"Gustavo F. Padovan" <gustavo@...ovan.org>,
"bluez mailin list (linux-bluetooth@...r.kernel.org)"
<linux-bluetooth@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
USB list <linux-usb@...r.kernel.org>,
netdev <netdev@...r.kernel.org>
Subject: Re: [RESEND][PATCH] Bluetooth: Make request workqueue freezable
At Thu, 21 May 2015 10:18:08 -0400 (EDT),
Alan Stern wrote:
>
> On Thu, 21 May 2015, Takashi Iwai wrote:
>
> > Then avoiding the failed firmware is no solution, indeed.
> > If it's a new probe, it should be never executed during resume.
>
> Can you expand this comment? What's wrong with probing during resume?
Well, if the probe requires the access to a user-space file, it can't
be done during resume. That's the very problem we're seeing now.
The firmware loader can't help much alone if it's a new device
object.
> The USB stack does carry out probes during resume under certain
> circumstances. A driver lacking a reset_resume callback is one of
> those circumstances.
So, having a proper reset_resume in btusb would help in the end?
Takashi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists