From: Jeff Johnson <jjohnson@codeaurora.org>
To: ath11k@lists.infradead.org
Subject: Re: [PATCH 3/3] ath11k: add synchronization operation between reconfigure of mac80211 and ath11k_base
Date: Tue, 12 Oct 2021 17:56:34 -0700 [thread overview]
Message-ID: <66577d4d-5269-2e26-9b73-6a5643a5cede@codeaurora.org> (raw)
In-Reply-To: <20211011081938.30327-4-wgong@codeaurora.org>
On 10/11/2021 1:19 AM, Wen Gong wrote:
> ieee80211_reconfig() of mac80211 is the main function for recovery of
> each ieee80211_hw and ath11k, and ath11k_core_reconfigure_on_crash()
> is the main function for recovery of ath11k_base, it has more than
> one ieee80211_hw and ath11k for each ath11k_base, so it need to add
> synchronization between them, otherwise it has many issue.
>
> For example, when ath11k_core_reconfigure_on_crash() is not complete,
> mac80211 send a hw scan request to ath11k, it leads firmware crash,
> because firmware has not been initilized at that moment, firmware
nit: s/initilized/initialized/
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
prev parent reply other threads:[~2021-10-13 1:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-11 8:19 [PATCH 0/3] ath11k: add feature for device recovery Wen Gong
2021-10-11 8:19 ` Wen Gong
2021-10-11 8:19 ` [PATCH 1/3] ath11k: add ath11k_qmi_free_resource() for recovery Wen Gong
2021-10-11 8:19 ` Wen Gong
2021-10-11 8:19 ` [PATCH 2/3] ath11k: add support for device recovery for QCA6390 Wen Gong
2021-10-11 8:19 ` Wen Gong
2021-10-11 8:19 ` [PATCH 3/3] ath11k: add synchronization operation between reconfigure of mac80211 and ath11k_base Wen Gong
2021-10-11 8:19 ` Wen Gong
2021-10-11 11:59 ` kernel test robot
2021-10-11 11:59 ` kernel test robot
2021-10-11 11:59 ` kernel test robot
2021-10-13 0:56 ` Jeff Johnson [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=66577d4d-5269-2e26-9b73-6a5643a5cede@codeaurora.org \
--to=jjohnson@codeaurora.org \
--cc=ath11k@lists.infradead.org \
/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.