From: "Arend van Spriel" <arend@broadcom.com>
To: "Zhou, Robie" <rzhou@qca.qualcomm.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Deng, Flavian" <flaviand@qti.qualcomm.com>
Subject: Re: ath9k_htc p2p finding issue
Date: Thu, 23 May 2013 10:12:38 +0200 [thread overview]
Message-ID: <519DCF76.8050704@broadcom.com> (raw)
In-Reply-To: <A75A50687AD91044B3B81AB78993F668447D2F7F@NASANEXD02E.na.qualcomm.com>
On 05/23/2013 07:58 AM, Zhou, Robie wrote:
> Hi all,
>
> We meet some problem when try P2P by using ath9k_htc compat-wireless-v3.6.8-1.
>
> When using the compat-wireless-v3.6.8-1, AR9271 could find other P2P devices, but other P2P devices couldn't find AR9271 (runs ath9k_htc) because driver couldn't report Probe Request to wpa_supplicant.
>
> And this issue could not be observed when using compat-wireless-v3.0.9-1, by compare with compat-wireless-v3.0.9-1, ATH9K RX filter is set correctly after got "Report Probe Request" command from wpa_supplicant, but ATH9K driver couldn't get "Probe Request" frame(I add debug msg in ieee80211_rx_handlers() function).
>
> <7>[ 205.784118] [DF_DBG] [ieee80211_mgmt_frame_register] : local->probe_req_reg = 1;
> <7>[ 205.830232] [DF_DBG] [ath9k_htc_opmode_init] rfilt = 0x17; -> ath9k_hw_setrxfilter
> <7>[ 205.832858] [DF_DBG] [ieee80211_configure_filter] : new_flags |= FIF_PROBE_REQ;
> <7>[ 205.833101] [DF_DBG] [ath9k_htc_configure_filter] rfilt = 0x287; -> ath9k_hw_setrxfilter
> <7>[ 205.878230] [DF_DBG] [ath9k_htc_opmode_init] rfilt = 0x287; -> ath9k_hw_setrxfilter
> <7>[ 205.882556] [DF_DBG] [ieee80211_configure_filter] : new_flags |= FIF_PROBE_REQ;
> <7>[ 205.883606] [DF_DBG] [ath9k_htc_configure_filter] rfilt = 0x287; -> ath9k_hw_setrxfilter
>
> <7>[ 206.010886] [DF_DBG] [ieee80211_mgmt_frame_register] : local->probe_req_reg = 0;
> <7>[ 206.036237] [DF_DBG] [ath9k_htc_opmode_init] rfilt = 0x287; -> ath9k_hw_setrxfilter
> <7>[ 206.043357] [DF_DBG] [ath9k_htc_configure_filter] rfilt = 0x17; -> ath9k_hw_setrxfilter
> <7>[ 206.044107] [DF_DBG] [ath9k_htc_configure_filter] rfilt = 0x17; -> ath9k_hw_setrxfilter
> <7>[ 206.090106] [DF_DBG] [ath9k_htc_opmode_init] rfilt = 0x17; -> ath9k_hw_setrxfilter
> <7>[ 206.160734] [DF_DBG] [ath9k_htc_opmode_init] rfilt = 0x17; -> ath9k_hw_setrxfilter
> <7>[ 206.230740] [DF_DBG] [ath9k_htc_opmode_init] rfilt = 0x17; -> ath9k_hw_setrxfilter
>
>
> Did anyone ever meet this issue? Any suggestion for further debugging this issue?
Did you confirm ath9k_htc is handing over probe requests to mac80211?
Might be useful to add debugging in prepare_for_handlers() instead.
Regards,
Arend
next prev parent reply other threads:[~2013-05-23 8:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 5:58 ath9k_htc p2p finding issue Zhou, Robie
2013-05-23 8:12 ` Arend van Spriel [this message]
2013-05-24 1:46 ` Deng, Flavian
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=519DCF76.8050704@broadcom.com \
--to=arend@broadcom.com \
--cc=flaviand@qti.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rzhou@qca.qualcomm.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).