From: Kalle Valo <kvalo@kernel.org>
To: David Lin <yu-hao.lin@nxp.com>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
briannorris@chromium.org, francesco@dolcini.it,
tsung-hsien.hsieh@nxp.com, David Lin <yu-hao.lin@nxp.com>,
stable@vger.kernel.org
Subject: Re: [v3] wifi: mwifiex: add extra delay for firmware ready
Date: Fri, 15 Dec 2023 13:24:35 +0000 (UTC) [thread overview]
Message-ID: <170264667352.1759617.2847802413188933835.kvalo@kernel.org> (raw)
In-Reply-To: <20231208234029.2197-1-yu-hao.lin@nxp.com>
David Lin <yu-hao.lin@nxp.com> wrote:
> For SDIO IW416, due to a bug, 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>
> Cc: stable@vger.kernel.org
> Reviewed-by: Francesco Dolcini <francesco.dolcini@toradex.com>
> Acked-by: Brian Norris <briannorris@chromium.org>
> Tested-by: Marcel Ziswiler <marcel.ziswiler@toradex.com> # Verdin AM62 (IW416)
Patch applied to wireless-next.git, thanks.
1c5d463c0770 wifi: mwifiex: add extra delay for firmware ready
--
https://patchwork.kernel.org/project/linux-wireless/patch/20231208234029.2197-1-yu-hao.lin@nxp.com/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2023-12-15 13:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 23:40 [PATCH v3] wifi: mwifiex: add extra delay for firmware ready David Lin
2023-12-11 7:37 ` Francesco Dolcini
2023-12-14 1:32 ` Brian Norris
2023-12-14 10:44 ` Marcel Ziswiler
2023-12-14 11:46 ` [EXT] " David Lin
2023-12-14 13:35 ` Marcel Ziswiler
2023-12-14 14:27 ` David Lin
2023-12-15 13:24 ` Kalle Valo [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=170264667352.1759617.2847802413188933835.kvalo@kernel.org \
--to=kvalo@kernel.org \
--cc=briannorris@chromium.org \
--cc=francesco@dolcini.it \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.