[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87a7vcazf1.fsf@kamboji.qca.qualcomm.com>
Date: Tue, 13 Mar 2018 15:16:34 +0200
From: Kalle Valo <kvalo@...eaurora.org>
To: "Luis R. Rodriguez" <mcgrof@...nel.org>
Cc: Andres Rodriguez <andresx7@...il.com>,
"linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-wireless <linux-wireless@...r.kernel.org>,
Arend Van Spriel <arend.vanspriel@...adcom.com>
Subject: Re: [PATCH] firmware: add a function to load optional firmware v2
"Luis R. Rodriguez" <mcgrof@...nel.org> writes:
>> +/**
>> + * request_firmware_optional: - request for an optional fw module
>> + * @firmware_p: pointer to firmware image
>> + * @name: name of firmware file
>> + * @device: device for which firmware is being loaded
>> + *
>> + * This function is similar in behaviour to request_firmware(), except
>> + * it doesn't produce warning messages when the file is not found.
>> + **/
>> +int
>> +request_firmware_optional(const struct firmware **firmware_p, const char *name,
>> + struct device *device)
>> +{
>> + int ret;
>> +
>> + /* Need to pin this module until return */
>> + __module_get(THIS_MODULE);
>> + ret = _request_firmware(firmware_p, name, device, NULL, 0,
>> + FW_OPT_UEVENT | FW_OPT_NO_WARN );
>> + module_put(THIS_MODULE);
>> + return ret;
>> +}
>> +EXPORT_SYMBOL(request_firmware_optional);
>
> New exported symbols for the firmware API should be EXPORT_SYMBOL_GPL().
To me the word optional feels weird to me. For example, in ath10k I
suspect we would be only calling request_firmware_optional() with all
firmware and not request_firmware() at all.
How about request_firmware_nowarn()? That would even match the
documentation above.
--
Kalle Valo
Powered by blists - more mailing lists