Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755652AbbEUR1v (ORCPT ); Thu, 21 May 2015 13:27:51 -0400 Received: from mail-gw2-out.broadcom.com ([216.31.210.63]:16536 "EHLO mail-gw2-out.broadcom.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752504AbbEUR1s (ORCPT ); Thu, 21 May 2015 13:27:48 -0400 X-IronPort-AV: E=Sophos;i="5.13,470,1427785200"; d="scan'208";a="65486426" Message-ID: <555E158D.4090607@broadcom.com> Date: Thu, 21 May 2015 19:27:41 +0200 From: Arend van Spriel User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.2.24) Gecko/20111103 Lightning/1.0b2 Thunderbird/3.1.16 MIME-Version: 1.0 To: Takashi Iwai CC: Alan Stern , Marcel Holtmann , Laura Abbott , Oliver Neukum , Ming Lei , "David S. Miller" , Laura Abbott , "Johan Hedberg" , "Rafael J. Wysocki" , "Gustavo F. Padovan" , "bluez mailin list (linux-bluetooth@vger.kernel.org)" , Linux Kernel Mailing List , USB list , netdev Subject: Re: [RESEND][PATCH] Bluetooth: Make request workqueue freezable References: <33C25745-6839-4858-9A3E-19EC6408ECED@holtmann.org> In-Reply-To: Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1681 Lines: 47 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. Regards, Arend > Takashi > -- > To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/