Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757981AbaFZQSK (ORCPT ); Thu, 26 Jun 2014 12:18:10 -0400 Received: from cantor2.suse.de ([195.135.220.15]:38131 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755713AbaFZQSI (ORCPT ); Thu, 26 Jun 2014 12:18:08 -0400 Date: Thu, 26 Jun 2014 18:18:05 +0200 Message-ID: From: Takashi Iwai To: "Luis R. Rodriguez" Cc: chunkeey@googlemail.com, leedom@chelsio.com, cocci@systeme.lip6.fr, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org, "Luis R. Rodriguez" Subject: Re: [PATCH 0/3] drivers: expand usage of request_firmware_direct() In-Reply-To: <1403649583-12707-1-git-send-email-mcgrof@do-not-panic.com> References: <1403649583-12707-1-git-send-email-mcgrof@do-not-panic.com> 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.3 (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: X-Mailing-List: linux-kernel@vger.kernel.org At Tue, 24 Jun 2014 15:39:40 -0700, Luis R. Rodriguez wrote: > > From: "Luis R. Rodriguez" > > Takashi added request_firmware_direct() via bba3a87e9 through v3.14-rc1 > which avoids the unnecessary delay introduced by using the udev firmware > loader in case the first try failed when loading we know loading "firmware" > is optional. The first use case was for microcode update but if drivers are > using it for optional configuration updates, custom EEPROMs, and other > junk other than firmware that should apply as well as good use cases, > specially if the driver already had a first phase in which it loaded > the first required firmware. While reviewing one driver I figured it'd > be best to try to give formalizing a check with SmPL. This isn't perfect > it had 1 false possitive drivers/fmc/fmc-fakedev.c on the entire kernel > run but my hope is this can be extended a bit more to build more > confidence, and then perhaps stuff it as a coccicheck. > > I suppose this will not be required once and if we remove > CONFIG_FW_LOADER_USER_HELPER. Is that ever going away for good? I know > there was a recent attempt to remove the udev loader support but > it was unclear if the special alternative helper support would be > removed upstream from the kernel. Actually a few weeks ago I sent a patch to make request_firmware() with usermode helper explicitly to be used by some drivers (like dell-rbu). I hope Greg took it for 3.17. Once when this patch is in, distros can turn off the usermode helper fallback gracefully, so no ugly timeout issue shouldn't happen. Takashi -- 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/