Return-Path: <cyrus@holtmann.org>
Date: Thu, 21 May 2015 19:32:25 +0200
Message-ID: <s5hmw0x4z12.wl-tiwai@suse.de>
From: Takashi Iwai <tiwai@suse.de>
To: Arend van Spriel <arend@broadcom.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
	Marcel Holtmann
	<marcel@holtmann.org>,
	Laura Abbott <labbott@redhat.com>,
	Oliver Neukum
	<oneukum@suse.com>,
	Ming Lei <ming.lei@canonical.com>,
	"David S. Miller"
	<davem@davemloft.net>,
	Laura Abbott <labbott@fedoraproject.org>,
	"Johan Hedberg" <johan.hedberg@gmail.com>,
	"Rafael J. Wysocki"
	<rafael.j.wysocki@intel.com>,
	"Gustavo F. Padovan" <gustavo@padovan.org>,
	"bluez mailin list (linux-bluetooth@vger.kernel.org)"
	<linux-bluetooth@vger.kernel.org>,
	Linux Kernel Mailing List
	<linux-kernel@vger.kernel.org>,
	USB list <linux-usb@vger.kernel.org>,
	netdev
	<netdev@vger.kernel.org>
Subject: Re: [RESEND][PATCH] Bluetooth: Make request workqueue freezable
In-Reply-To: <555E158D.4090607@broadcom.com>
References: <33C25745-6839-4858-9A3E-19EC6408ECED@holtmann.org>
	<Pine.LNX.4.44L0.1505211112310.1397-100000@iolanthe.rowland.org>
	<s5hsiaq3pv4.wl-tiwai@suse.de>
	<555E158D.4090607@broadcom.com>
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
List-ID: <linux-bluetooth.vger.kernel.org>

At Thu, 21 May 2015 19:27:41 +0200,
Arend van Spriel wrote:
> 
> On 05/21/15 17:35, Takashi Iwai wrote:
> > At Thu, 21 May 2015 11:26:17 -0400 (EDT),
> > Alan Stern wrote:
> >>
> >> On Thu, 21 May 2015, Takashi Iwai wrote:
> >>
> >>> 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.
> >>
> >> But the same thing happens during early boot, if the driver is built
> >> into the kernel.  When the probe occurs, userspace isn't up and running
> >> yet, so the firmware loader can't do anything.
> >>
> >> Why should probe during resume be any worse than probe during early
> >> boot?
> >
> > The early boot has initrd, so the files can be there.  But the resume
> > has no way to fetch the file except for cached data.
> 
> but initrd is optional so without initrd it is pretty much the same.

User can build the firmware into the kernel.


Takashi