From: bjorn.andersson@linaro.org (Bjorn Andersson)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC][PATCH 1/2] remoteproc: Reduce asynchronous request_firmware to auto-boot only
Date: Mon, 6 Feb 2017 13:08:37 -0800 [thread overview]
Message-ID: <20170206210837.GH31134@builder> (raw)
In-Reply-To: <1485299581-30476-1-git-send-email-spjoshi@codeaurora.org>
On Tue 24 Jan 15:13 PST 2017, Sarangdhar Joshi wrote:
> The rproc_add_virtio_devices() requests firmware asynchronously and
> triggers boot if the auto_boot flag is set. However, this
> asynchronous call seems to be redundant for non auto-boot scenario
> since the rproc_boot() would call request_firmware() anyways. Move
> the auto_boot check to rproc_add() so that a redundant call to
> _request_firmware can be avoided for non auto-boot case.
>
> Signed-off-by: Sarangdhar Joshi <spjoshi@codeaurora.org>
Looks good, applied both patches.
Regards,
Bjorn
> ---
>
> I'm requesting RFC on this patch since I'm not aware of any scenario
> where we might need asynchronous firmware loading for non auto-boot case.
>
> drivers/remoteproc/remoteproc_core.c | 14 ++++++++------
> 1 file changed, 8 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/remoteproc/remoteproc_core.c b/drivers/remoteproc/remoteproc_core.c
> index f58e634..16242b0 100644
> --- a/drivers/remoteproc/remoteproc_core.c
> +++ b/drivers/remoteproc/remoteproc_core.c
> @@ -970,9 +970,7 @@ static void rproc_fw_config_virtio(const struct firmware *fw, void *context)
> {
> struct rproc *rproc = context;
>
> - /* if rproc is marked always-on, request it to boot */
> - if (rproc->auto_boot)
> - rproc_boot(rproc);
> + rproc_boot(rproc);
>
> release_firmware(fw);
> }
> @@ -1286,9 +1284,13 @@ int rproc_add(struct rproc *rproc)
>
> /* create debugfs entries */
> rproc_create_debug_dir(rproc);
> - ret = rproc_add_virtio_devices(rproc);
> - if (ret < 0)
> - return ret;
> +
> + /* if rproc is marked always-on, request it to boot */
> + if (rproc->auto_boot) {
> + ret = rproc_add_virtio_devices(rproc);
> + if (ret < 0)
> + return ret;
> + }
>
> /* expose to rproc_get_by_phandle users */
> mutex_lock(&rproc_list_mutex);
> --
> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
> a Linux Foundation Collaborative Project
>
next prev parent reply other threads:[~2017-02-06 21:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 23:13 [RFC][PATCH 1/2] remoteproc: Reduce asynchronous request_firmware to auto-boot only Sarangdhar Joshi
2017-01-24 23:13 ` [PATCH 2/2] remoteproc: Modify the function names Sarangdhar Joshi
2017-02-06 21:08 ` Bjorn Andersson [this message]
2017-02-07 18:55 ` [RFC][PATCH 1/2] remoteproc: Reduce asynchronous request_firmware to auto-boot only Sarangdhar Joshi
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=20170206210837.GH31134@builder \
--to=bjorn.andersson@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).