Received: by 10.192.165.148 with SMTP id m20csp140555imm; Thu, 3 May 2018 16:40:56 -0700 (PDT) X-Google-Smtp-Source: AB8JxZp+URolJb1SrUkDiuUWAgmOeMHWXpu8ThvyC+OELa9fmcSey8ArHZLC+hPqGdHWU5T0ShIN X-Received: by 2002:a17:902:1a6:: with SMTP id b35-v6mr25602171plb.80.1525390856573; Thu, 03 May 2018 16:40:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525390856; cv=none; d=google.com; s=arc-20160816; b=SmGzPfGohl3g9ClWpSFHrhCCB9BincMaXw/QcTyrMFSVFrkOKRCAaMFYbmdzTGGJQ2 Z5w1K+5J2y/4JzhA5oCOQU+uRePJ60Oq2STmNSSpUv11hx4mAXmc4NfC2aOa15NMOVX6 nOVzdwiMqw8heyqV9FSREkNlRtbMCQXxgndQbqo5cvq3DlbMnsK4kuuvBdjc3MBiRd1A p7IF7BEFAG4ZwdNowEg79NxjKdVzMuzdczN+Qps9Tv0e/eaFpUgCiGQG2/fGqV/qON5t 2rPgHy8TlgXOOBjF3sIhkVfrnVb+3LKQyNJ1cdsRAsvHS8m2mRjNBquW40xEc6gAXuDT xKag== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=ZZUDCY7seWx/TgpqI3XPM0zEy7reDhDoDivvvsNYSOk=; b=Egedwga0OQ6kuaz2QM6senoOQF+J8EcJPegzy/+7P41iEtTZTshdVzcxu7bZJ6uscx qzYWpzvx7si6pDj9shBqTCqMNhLOs+R7VbUZKkB2eefSX6j1sz1fuilEWhq4jnMRw/UV DD7SQPSJQ54PiMn0rewFc3nosGNwZF0/bSF2kw5SLoU/wpCWlMu4PoBHPmy+UCZyEMar JJ1PDdpjN/NpEDbWDek/TysWwCpY6hZIVjrmfrqZwoEcb+C3sQYs/w6KZxqZVOpc3y6F M/tTDaxVBfS4bIl+HL4usxla1YLEVRXMOt9DwzDSK4v+PAuHt6MaVXgxR8lGj2eLE5Ee +4TA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id l16-v6si11807860pgc.177.2018.05.03.16.40.42; Thu, 03 May 2018 16:40:56 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751415AbeECXkG (ORCPT + 99 others); Thu, 3 May 2018 19:40:06 -0400 Received: from mx2.suse.de ([195.135.220.15]:60058 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750930AbeECXkE (ORCPT ); Thu, 3 May 2018 19:40:04 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (charybdis-ext.suse.de [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 8ADECAD4B; Thu, 3 May 2018 23:40:03 +0000 (UTC) Date: Thu, 3 May 2018 23:40:03 +0000 From: "Luis R. Rodriguez" To: Andres Rodriguez Cc: linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org, mcgrof@kernel.org, alexdeucher@gmail.com, christian.koenig@amd.com, kvalo@codeaurora.org, arend.vanspriel@broadcom.com, linux-wireless@vger.kernel.org, ath10k@lists.infradead.org, hdegoede@redhat.com, Kees Cook Subject: Re: [PATCH 5/9] firmware: add function to load firmware without warnings v5 Message-ID: <20180503234003.GW27853@wotan.suse.de> References: <20180423201205.20533-1-andresx7@gmail.com> <20180423201205.20533-6-andresx7@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180423201205.20533-6-andresx7@gmail.com> User-Agent: Mutt/1.6.0 (2016-04-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Apr 23, 2018 at 04:12:01PM -0400, Andres Rodriguez wrote: > Currently the firmware loader only exposes one silent path for querying > optional firmware, and that is firmware_request_direct(). This function > also disables the fallback path, which might not always be the > desired behaviour. [0] > > This patch introduces a variations of firmware_request() that enable the > caller to disable the undesired warning messages. This is equivalent to > adding FW_OPT_NO_WARN to the old behaviour. > > v2: add header prototype, use updated opt_flags > v3: split debug message to separate patch > added _nowait variant > added documentation > v4: fix kernel-doc style > v5: drop _nowait for now, since we lack agreement on the API > > [0]: https://git.kernel.org/linus/c0cc00f250e1 > > Signed-off-by: Andres Rodriguez > --- > .../driver-api/firmware/request_firmware.rst | 5 +++++ > drivers/base/firmware_loader/main.c | 24 ++++++++++++++++++++++ > include/linux/firmware.h | 2 ++ > 3 files changed, 31 insertions(+) > > diff --git a/Documentation/driver-api/firmware/request_firmware.rst b/Documentation/driver-api/firmware/request_firmware.rst > index 7632f8807472..c8bddbdcfd10 100644 > --- a/Documentation/driver-api/firmware/request_firmware.rst > +++ b/Documentation/driver-api/firmware/request_firmware.rst > @@ -20,6 +20,11 @@ firmware_request > .. kernel-doc:: drivers/base/firmware_loader/main.c > :functions: firmware_request > > +firmware_request_nowarn > +----------------------- > +.. kernel-doc:: drivers/base/firmware_loader/main.c > + :functions: firmware_request_nowarn > + > firmware_request_direct > ----------------------- > .. kernel-doc:: drivers/base/firmware_loader/main.c > diff --git a/drivers/base/firmware_loader/main.c b/drivers/base/firmware_loader/main.c > index d028cd3257f7..58aaadf81e12 100644 > --- a/drivers/base/firmware_loader/main.c > +++ b/drivers/base/firmware_loader/main.c > @@ -631,6 +631,30 @@ firmware_request(const struct firmware **firmware_p, const char *name, > } > EXPORT_SYMBOL(firmware_request); > > +/** > + * firmware_request_nowarn() - request for an optional fw module > + * @firmware: pointer to firmware image > + * @name: name of firmware file > + * @device: device for which firmware is being loaded > + * > + * This function is similar in behaviour to firmware_request(), except > + * it doesn't produce warning messages when the file is not found. It doesn't explain the difference between this and firmware_request_direct() I'll go ahead and add this and expand also on firmware_request_direct() to be clearer on the differences to a reader. I'll queue this up and resubmit myself. Luis > + **/ > +int > +firmware_request_nowarn(const struct firmware **firmware, const char *name, > + struct device *device) > +{ > + int ret; > + > + /* Need to pin this module until return */ > + __module_get(THIS_MODULE); > + ret = _firmware_request(firmware, name, device, NULL, 0, > + FW_OPT_UEVENT | FW_OPT_NO_WARN); > + module_put(THIS_MODULE); > + return ret; > +} > +EXPORT_SYMBOL_GPL(firmware_request_nowarn); > + > /** > * firmware_request_direct() - load firmware directly without usermode helper > * @firmware_p: pointer to firmware image > diff --git a/include/linux/firmware.h b/include/linux/firmware.h > index db8351a42405..a34e16f77f20 100644 > --- a/include/linux/firmware.h > +++ b/include/linux/firmware.h > @@ -42,6 +42,8 @@ struct builtin_fw { > #if defined(CONFIG_FW_LOADER) || (defined(CONFIG_FW_LOADER_MODULE) && defined(MODULE)) > int firmware_request(const struct firmware **fw, const char *name, > struct device *device); > +int firmware_request_nowarn(const struct firmware **fw, const char *name, > + struct device *device); > int firmware_request_nowait( > struct module *module, bool uevent, > const char *name, struct device *device, gfp_t gfp, void *context, > -- > 2.14.1 > > -- Do not panic