From: Francesco Dolcini <francesco@dolcini.it>
To: David Lin <yu-hao.lin@nxp.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"briannorris@chromium.org" <briannorris@chromium.org>,
"kvalo@kernel.org" <kvalo@kernel.org>,
"francesco@dolcini.it" <francesco@dolcini.it>,
Sharvari Harisangam <sharvari.harisangam@nxp.com>,
Pete Hsieh <tsung-hsien.hsieh@nxp.com>
Subject: Re: [PATCH] wifi: mwifiex: added delay after firmware downloaded.
Date: Sat, 21 Oct 2023 14:56:25 +0200 [thread overview]
Message-ID: <ZTPKedZWWAfDjmpo@livingston.pivistrello.it> (raw)
In-Reply-To: <PA4PR04MB96388864C8B07F2B3AA7964AD1DBA@PA4PR04MB9638.eurprd04.prod.outlook.com>
Hello David,
thanks for your patch.
On Fri, Oct 20, 2023 at 03:35:34AM +0000, David Lin wrote:
> Added 100 ms delayed after firmware is downloaded and active in order to
> avoid command timeout for the first command sent to firmware.
Please have a look at Documentation/process/submitting-patches.rst.
In very brief:
- you should use imperative mood to describe your changes
- this is fixing a real issue, I believe this is worth a more complete commit
message, including a log of the failure this is solving.
I am also inclined to think that this change should be backported and it likely
would need a Fixes: tag.
> ---
> drivers/net/wireless/marvell/mwifiex/main.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/net/wireless/marvell/mwifiex/main.c b/drivers/net/wireless/marvell/mwifiex/main.c
> index d99127dc466e..a25e8bb8daec 100644
> --- a/drivers/net/wireless/marvell/mwifiex/main.c
> +++ b/drivers/net/wireless/marvell/mwifiex/main.c
> @@ -570,6 +570,7 @@ static int _mwifiex_fw_dpc(const struct firmware *firmware, void *context)
> goto err_dnld_fw;
>
> mwifiex_dbg(adapter, MSG, "WLAN FW is active\n");
> + mdelay(100);
from my understanding there is already a function polling for the firmware to be
active, e.g. mwifiex_check_fw_status(). Maybe is that function that needs to be
fixed instead of adding an additional delay here?
Francesco
next prev parent reply other threads:[~2023-10-21 12:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 3:35 David Lin
2023-10-21 12:56 ` Francesco Dolcini [this message]
2023-10-23 2:12 ` [EXT] " David Lin
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=ZTPKedZWWAfDjmpo@livingston.pivistrello.it \
--to=francesco@dolcini.it \
--cc=briannorris@chromium.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sharvari.harisangam@nxp.com \
--cc=tsung-hsien.hsieh@nxp.com \
--cc=yu-hao.lin@nxp.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
all inboxes | Powered by JetHome®