From: "Kumar, M Chetan" <m.chetan.kumar@linux.intel.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
johannes@sipsolutions.net, ryazanov.s.a@gmail.com,
loic.poulain@linaro.org, ilpo.jarvinen@linux.intel.com,
ricardo.martinez@linux.intel.com,
chiranjeevi.rapolu@linux.intel.com, haijun.liu@mediatek.com,
edumazet@google.com, pabeni@redhat.com,
chandrashekar.devegowda@intel.com, linuxwwan@intel.com,
linuxwwan_5g@intel.com, corbet@lwn.net,
linux-doc@vger.kernel.org, jiri@nvidia.com
Subject: Re: [PATCH v5 net-next 5/5] net: wwan: t7xx: Devlink documentation
Date: Thu, 26 Jan 2023 16:25:34 +0530 [thread overview]
Message-ID: <e8316533-53cc-1533-a8f2-fb8860a31a9d@linux.intel.com> (raw)
In-Reply-To: <20230125100812.026c0a1e@kernel.org>
On 1/25/2023 11:38 PM, Jakub Kicinski wrote:
> On Wed, 25 Jan 2023 16:03:37 +0530 Kumar, M Chetan wrote:
>>> I don't know what fastboot is, and reading this doc I see it used in
>>> three forms:
>>> - fastboot protocol
>>> - fastboot mode
>>> - fastboot command & response
>>
>> The fastboot is sort of a tool. It implements the protocol for
>> programming the device flash or getting device information. The device
>> implements the fastboot commands and host issue those commands for
>> programming the firmware to device flash or to obtain device
>> information. Inorder to execute those commands, first the device needs
>> to be put into fastboot mode.
>>
>> More details on fastboot can be found in links [1].
>>
>>> In the end - I have no idea what the devlink param you're adding does.
>>
>> "fastboot" devlink param is used to put the device into fastboot mode
>> to program firmware to device flash or to obtain device information.
>>
>>
>> [1]
>> https://en.wikipedia.org/wiki/Fastboot
>> https://android.googlesource.com/platform/system/core/+/refs/heads/master/fastboot/README.md
>
> As Ilpo mentions, please add this info into the doc, including
> the links.
Sure. In the next patch, I will detail out the fastboot and include
those links for reference.
>
> The most confusing part is that "fastboot" sounds like it's going
> to boot fast, while IIUC the behavior is the opposite - it's not going
> to boot at all and just expose an interface to load the FW, is that
> right?
On device side, the fastboot protocol is implemented in bootloader. When
the host request the device to enter fastboot mode, the device is reset.
Post reset, the host will be able to communicate with device bootloader
using fastboot protocol.
Fastboot protocol implements a set of commands for various operations.
The "flash" is one such command used for programming firmware.
>
> Please also clarify what the normal operation for the device is.
It means fully functional mode.
In this mode wwan functionalities like AT, MBIM, modem trace collection
& data path are operational.
> In what scenarios does the fastboot mode get used?
It is used in 2 scenarios.
1> Firmware update, when user/app wants to update firmware.
2> Core dump collection, when device encounters an exception.
>
> And just to double confirm - that the FW loaded in fastboot mode is
> persistently stored on the device, and will be used after power cycle.
> Rather than it being an upload into RAM.
That's correct.
The firmware is permanently stored on the device & it will be used after
power cycle.
--
Chetan
prev parent reply other threads:[~2023-01-26 10:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1674307425.git.m.chetan.kumar@linux.intel.com>
2023-01-21 13:33 ` [PATCH v5 net-next 5/5] net: wwan: t7xx: Devlink documentation m.chetan.kumar
2023-01-22 2:13 ` Bagas Sanjaya
2023-01-24 14:30 ` Kumar, M Chetan
2023-01-25 4:51 ` Jakub Kicinski
2023-01-25 10:33 ` Kumar, M Chetan
2023-01-25 11:34 ` Ilpo Järvinen
2023-01-25 18:08 ` Jakub Kicinski
2023-01-26 10:55 ` Kumar, M Chetan [this message]
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=e8316533-53cc-1533-a8f2-fb8860a31a9d@linux.intel.com \
--to=m.chetan.kumar@linux.intel.com \
--cc=chandrashekar.devegowda@intel.com \
--cc=chiranjeevi.rapolu@linux.intel.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=haijun.liu@mediatek.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jiri@nvidia.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linuxwwan@intel.com \
--cc=linuxwwan_5g@intel.com \
--cc=loic.poulain@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ricardo.martinez@linux.intel.com \
--cc=ryazanov.s.a@gmail.com \
/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).