From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: <ath10k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] ath10k: fix AP/IBSS CSA with template based fw
Date: Sun, 15 Feb 2015 17:51:14 +0200 [thread overview]
Message-ID: <87mw4fgolp.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1423749198-11346-1-git-send-email-michal.kazior@tieto.com> (Michal Kazior's message of "Thu, 12 Feb 2015 14:53:18 +0100")
Michal Kazior <michal.kazior@tieto.com> writes:
> qca6174 with wmi-tlv firmware uses offloaded
> beaconing scheme (i.e. templates). This requires a
> little different approach when implementing CSA.
>
> Add missing code to update CS count and report CSA
> completion to mac80211. Without it channel switch
> was never finished.
>
> To avoid races during interface teardown data_lock
> has been used to protect is_up and is_started so
> they can be compared against before scheduling
> count down work.
>
> Signed-off-by: Michal Kazior <michal.kazior@tieto.com>
> ---
>
> @Kalle: I'm deferring the chanctx patchset v4
> until this gets applied. I'd like to avoid posting
> patches without a valid parent id and leaving you
> with some weird conflicts and implicit depndencies
> in the code to deal with.
Ok.
I actually had strange conflicts already with this patch (in mac.c). As
I'm travelling, please check my resolution from the pending branch very
carefully. I might have done something stupid.
--
Kalle Valo
next prev parent reply other threads:[~2015-02-15 15:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 13:53 [PATCH] ath10k: fix AP/IBSS CSA with template based fw Michal Kazior
2015-02-15 15:51 ` Kalle Valo [this message]
2015-02-16 6:54 ` Michal Kazior
2015-02-16 13:21 ` Kalle Valo
2015-02-16 12:34 ` [PATCH v2] " Michal Kazior
2015-03-07 7:46 ` Kalle Valo
2015-03-09 9:30 ` Michal Kazior
2015-03-09 12:25 ` Kalle Valo
2015-03-09 13:19 ` [PATCH] ath10k: fix patching mistake for AP/IBSS CSA Michal Kazior
2015-03-12 12:19 ` Kalle Valo
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=87mw4fgolp.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=michal.kazior@tieto.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).