From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1752833AbbESRNS (ORCPT <rfc822;w@1wt.eu>);
	Tue, 19 May 2015 13:13:18 -0400
Received: from cantor2.suse.de ([195.135.220.15]:37615 "EHLO mx2.suse.de"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751198AbbESRNQ (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Tue, 19 May 2015 13:13:16 -0400
Date: Tue, 19 May 2015 19:13:14 +0200
Message-ID: <s5hpp5wtrrp.wl-tiwai@suse.de>
From: Takashi Iwai <tiwai@suse.de>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Laura Abbott <labbott@redhat.com>, Marcel Holtmann <marcel@holtmann.org>,
        Laura Abbott <labbott@fedoraproject.org>,
        "Gustavo F. Padovan" <gustavo@padovan.org>,
        Johan Hedberg <johan.hedberg@gmail.com>,
        "David S. Miller" <davem@davemloft.net>,
        "bluez mailin list (linux-bluetooth@vger.kernel.org)" 
	<linux-bluetooth@vger.kernel.org>,
        netdev <netdev@vger.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Ming Lei <ming.lei@canonical.com>,
        "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
        <linux-usb@vger.kernel.org>
Subject: Re: [RESEND][PATCH] Bluetooth: Make request workqueue freezable
In-Reply-To: <Pine.LNX.4.44L0.1505191017460.1453-100000@iolanthe.rowland.org>
References: <s5hwq04zypv.wl-tiwai@suse.de>
	<Pine.LNX.4.44L0.1505191017460.1453-100000@iolanthe.rowland.org>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka)
 FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/24.5
 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

At Tue, 19 May 2015 10:26:46 -0400 (EDT),
Alan Stern wrote:
> 
> > > >  Of just have request_firmware()
> > > > actually sleep until userspace is ready. Seriously, why is
> > > > request_firmware not just sleeping for us.
> 
> It won't work.  The request_firmware call is part of the probe 
> sequence, which in turn is part of the resume sequence.  Userspace 
> doesn't start running again until the resume sequence is finished.  If 
> request_firmware waited for userspace, it would hang.

Note that the recent request_firmware() doesn't need the user-space
invocation (unless the fallback is explicitly enabled) but loads the
file directly.  And, request_firmware() for the cached data is valid
to be called in the resume path.


Takashi