From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Hemant Kumar <hemantk@codeaurora.org>
Cc: Manivannan Sadhasivam <mani@kernel.org>,
linux-kernel@vger.kernel.org, mhi@lists.linux.dev,
linux-arm-msm@vger.kernel.org,
Mario Limonciello <Mario.Limonciello@amd.com>,
Richard Hughes <hughsient@gmail.com>
Subject: Re: [RFC] bus: mhi: core: Load firmware asynchronous
Date: Tue, 14 Dec 2021 07:32:24 +0100 [thread overview]
Message-ID: <02e32c9d-79d2-4237-bb6b-8bd27029e7a9@t-8ch.de> (raw)
In-Reply-To: <403e93df-5b3c-acb3-2b65-df9a7834a9c5@codeaurora.org>
On 2021-12-13 16:07-0800, Hemant Kumar wrote:
> On 12/10/2021 8:16 AM, Thomas Weißschuh wrote:
> > This gives userspace the possibility to provide the firehose bootloader
> > via the sysfs-firmware-API instead of having to modify the global
> > firmware loadpath.
> >
> > Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
> >
> > ---
> >
> > Please note that this is not tested yet, as I don't have access to a matching
> > firmware file.
> > This submission is to gather general feedback from the maintainers and then
> > Richard will do the actual testing, while I'll do the development.
> >
> > This patch is should not have any impact beyond moving from request_firmware()
> > to request_firmware_nowait() and the involved code reshuffle.
> what are we achieving by moving to async ver of the firmware load ? MHI boot
> flow can not do anything until BHI load is over. Is the intention eventually
> to enable firmware fallback mechanism and manually load the firmware ?
The goal is to provide the firehose bootloader (qcom/prog_firehose_sdx24.mbn)
via the firmware fallback mechanism when upgrading the firmware on the device
via the firehose protocol.
This bootloader firmware is not part of linux-firmware but provided as part of
each firmware update package, so it is not installed statically on the system.
I will extend the commit message with this information.
PS: The current patch is missing 'return' after calls to
'mhi_fw_load_finish()', this will be corrected in v2.
next prev parent reply other threads:[~2021-12-14 6:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 16:16 Thomas Weißschuh
2021-12-14 0:07 ` Hemant Kumar
2021-12-14 6:32 ` Thomas Weißschuh [this message]
2021-12-14 22:55 ` Hemant Kumar
2021-12-14 23:28 ` Thomas Weißschuh
2021-12-16 10:19 ` 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=02e32c9d-79d2-4237-bb6b-8bd27029e7a9@t-8ch.de \
--to=linux@weissschuh.net \
--cc=Mario.Limonciello@amd.com \
--cc=hemantk@codeaurora.org \
--cc=hughsient@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mani@kernel.org \
--cc=mhi@lists.linux.dev \
/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
all inboxes | Powered by JetHome®