From: Kalle Valo <kvalo@codeaurora.org>
To: "Luis R. Rodriguez" <mcgrof@kernel.org>
Cc: Andres Rodriguez <andresx7@gmail.com>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
Arend Van Spriel <arend.vanspriel@broadcom.com>
Subject: Re: [PATCH] firmware: add a function to load optional firmware v2
Date: Tue, 13 Mar 2018 15:16:34 +0200 [thread overview]
Message-ID: <87a7vcazf1.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAB=NE6VY62KqmhzD=zT8od=PhgPi3rGKKKxKz_zad-ZrYW-97A@mail.gmail.com> (Luis R. Rodriguez's message of "Sat, 10 Mar 2018 06:35:30 -0800")
"Luis R. Rodriguez" <mcgrof@kernel.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
next prev parent reply other threads:[~2018-03-13 13:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180309221243.15489-2-andresx7@gmail.com>
[not found] ` <20180309230925.3573-1-andresx7@gmail.com>
2018-03-10 14:35 ` [PATCH] firmware: add a function to load optional firmware v2 Luis R. Rodriguez
2018-03-10 14:40 ` Luis R. Rodriguez
2018-03-11 16:05 ` Andres Rodriguez
2018-03-11 23:10 ` Arend van Spriel
2018-03-12 19:27 ` Luis R. Rodriguez
2018-03-13 13:39 ` Kalle Valo
2018-03-13 16:38 ` Luis R. Rodriguez
2018-03-20 2:21 ` Andres Rodriguez
2018-03-13 13:35 ` Kalle Valo
2018-03-13 13:16 ` Kalle Valo [this message]
2018-03-13 16:40 ` Luis R. Rodriguez
2018-03-13 16:46 ` Kalle Valo
2018-03-14 8:24 ` Arend van Spriel
2018-03-14 8:48 ` Kalle Valo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a7vcazf1.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=andresx7@gmail.com \
--cc=arend.vanspriel@broadcom.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).