From: Francesco Dolcini <francesco@dolcini.it>
To: David Lin <yu-hao.lin@nxp.com>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
briannorris@chromium.org, kvalo@kernel.org, francesco@dolcini.it,
tsung-hsien.hsieh@nxp.com
Subject: Re: [PATCH] wifi: mwifiex: added extra delay for firmware ready.
Date: Tue, 5 Dec 2023 21:00:37 +0100 [thread overview]
Message-ID: <ZW+BZRHDta7vKZgs@francesco-nb.int.toradex.com> (raw)
In-Reply-To: <20231128082544.613179-1-yu-hao.lin@nxp.com>
Hello David,
thanks for your patch. Planning to run some test on this over the next
days and we'll provide some actual feedback if this really solves the
issue we are affected by.
Just a couple of nitpicky comments on the actual patch.
On the commit message you should use imperative mood, e.g.
`wifi: mwifiex: add extra delay for firmware ready`
with no period at the end of the line.
On Tue, Nov 28, 2023 at 04:25:44PM +0800, David Lin wrote:
> For SDIO IW416, in a corner case FW may return ready before complete full
> initialization.
> Command timeout may occur at driver load after reboot.
> Workaround by adding 100ms delay at checking FW status.
>
> Signed-off-by: David Lin <yu-hao.lin@nxp.com>
Add
Cc: stable@...
> ---
> drivers/net/wireless/marvell/mwifiex/sdio.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/net/wireless/marvell/mwifiex/sdio.c b/drivers/net/wireless/marvell/mwifiex/sdio.c
> index 6462a0ffe698..744e9403430a 100644
> --- a/drivers/net/wireless/marvell/mwifiex/sdio.c
> +++ b/drivers/net/wireless/marvell/mwifiex/sdio.c
> @@ -783,6 +783,9 @@ static int mwifiex_check_fw_status(struct mwifiex_adapter *adapter,
> ret = -1;
> }
>
> + if (!ret)
> + msleep(100);
> +
you could just add the delay after
if (firmware_stat == FIRMWARE_READY_SDIO) {
this would be more read-able to me. Adding also a short comment like
/* Firmware might pretend to be ready, when it's not.
* Wait a little bit more as a workaround */
Francesco
next prev parent reply other threads:[~2023-12-05 20:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 8:25 David Lin
2023-12-05 20:00 ` Francesco Dolcini [this message]
2023-12-06 1:53 ` [EXT] " David Lin
2023-12-05 20:26 ` Brian Norris
2023-12-06 2:19 ` [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=ZW+BZRHDta7vKZgs@francesco-nb.int.toradex.com \
--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=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®