From: Sujith Manoharan <sujith@msujith.org>
To: John Linville <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org, ath9k-devel@qca.qualcomm.com
Subject: Re: [PATCH] ath9k: Cancel pending offchannel operations [and 1 more messages]
Date: Mon, 3 Nov 2014 10:09:13 +0530 [thread overview]
Message-ID: <21591.1777.261577.885153@gargle.gargle.HOWL> (raw)
In-Reply-To: <1414825459-8974-1-git-send-email-sujith@msujith.org>, <1414825540-9064-1-git-send-email-sujith@msujith.org>
Hi John,
Can you please hold off on these patches ?
I'll repost them after some more testing.
Sujith
Sujith Manoharan wrote:
> From: Sujith Manoharan <c_manoha@qca.qualcomm.com>
>
> In mgd_prepare_tx(), any pending HW scan is cancelled,
> but pending RoC operations are not cancelled. This
> results in a RoC request that never completes. For example,
> in a GO/STA setup, if p2p-find is initiated on an active GO
> interface wpa_s issues a RoC on the listen channel at the
> end of each scan run.
>
> Enabling the station interface will force the station context
> and the earlier RoC is not cleared. Fix this by clearing all
> pending offchannel operations in mgd_prepare_tx().
Sujith Manoharan wrote:
> From: Sujith Manoharan <c_manoha@qca.qualcomm.com>
>
> When a pending roc or scan operation is cancelled,
> the offchannel operation is cleared, but the offchannel
> state in the main scheduler is not cleared. This causes
> problems since an active GO will try to process a stale
> offchannel request that was deferred earlier. Fix this
> by clearing the state when there is no pending offchannel
> (roc/scan) operation.
prev parent reply other threads:[~2014-11-03 4:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-01 7:04 [PATCH] ath9k: Cancel pending offchannel operations Sujith Manoharan
2014-11-01 7:05 ` [PATCH] ath9k: Clear offchannel state properly Sujith Manoharan
2014-11-03 4:39 ` Sujith Manoharan [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=21591.1777.261577.885153@gargle.gargle.HOWL \
--to=sujith@msujith.org \
--cc=ath9k-devel@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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