linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Groeneveld <kgroeneveld@gmail.com>
To: Dmitry Tarnyagin <dmitry.tarnyagin@stericsson.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCHv2 00/21] cw1200: ST-Ericsson cw1200 wlan device driver
Date: Thu, 3 May 2012 14:57:23 -0400	[thread overview]
Message-ID: <CABF+-6UgQek50abaLnUsBh3LEccG2Pd1vFQDiLyxgcky-JN4Ag@mail.gmail.com> (raw)
In-Reply-To: <4FA2BF0A.4040307@stericsson.com>

Hi Dmitry,

> It looks like mac80211 tries to monitor beacons and they are filtered by
> cw1200 device.
>
> IEEE80211_HW_CONNECTION_MONITOR and / or IEEE80211_HW_BEACON_FILTER flags
> (I don't remember, but both of them should be set) should prevent mac80211
> from
> monitoring. Please check if they are set in
> drivers/net/wireless/cw1200/main.c

main.c contains the following as in the patches that you posted:

hw->flags = IEEE80211_HW_SIGNAL_DBM |
		    IEEE80211_HW_SUPPORTS_PS |
		    IEEE80211_HW_SUPPORTS_DYNAMIC_PS |
		    IEEE80211_HW_REPORTS_TX_ACK_STATUS |
		    IEEE80211_HW_SUPPORTS_UAPSD |
		    IEEE80211_HW_CONNECTION_MONITOR |
		    IEEE80211_HW_NEED_DTIM_PERIOD;

IEEE80211_HW_BEACON_FILTER does not seem to be defined anywhere in the
header files.  Do I need this?

>>> Also I see unexpectedly high rate of IRQs, they should not come every now
>>> and then..
>>
>> Any ideas what could cause this or how I should debug it?
>
> Are you running with SDIO or GPIO IRQ?

I am using SDIO IRQ.


Thanks,

Kevin

  reply	other threads:[~2012-05-03 18:57 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-02 15:22 [PATCHv2 00/21] cw1200: ST-Ericsson cw1200 wlan device driver Kevin Groeneveld
2012-05-02 16:01 ` Dmitry Tarnyagin
     [not found]   ` <CABF+-6XbdG_QMa0iQJMpbOsr4bXCq4mDEB6unkM8jxNGWYwFyQ@mail.gmail.com>
2012-05-02 16:51     ` Kevin Groeneveld
     [not found]     ` <4FA23DA0.3030207@stericsson.com>
2012-05-03 16:42       ` Kevin Groeneveld
2012-05-03 17:23         ` Dmitry Tarnyagin
2012-05-03 18:57           ` Kevin Groeneveld [this message]
2012-05-03 21:57             ` Janusz Dziedzic
2012-05-04  0:10               ` Kevin Groeneveld
2012-05-04 21:40                 ` Kevin Groeneveld
2012-05-05  7:20                   ` Janusz Dziedzic
2012-05-07  9:25                     ` Janusz Dziedzic
2012-05-07 19:54                       ` Kevin Groeneveld
2012-05-09 17:03   ` Kevin Groeneveld
2012-05-09 18:24     ` Dmitry Tarnyagin
2012-05-09 18:33       ` Johannes Berg
2012-05-09 18:56       ` Kevin Groeneveld
2012-05-09 19:37         ` Dmitry Tarnyagin
2012-05-09 20:37         ` Solomon Peachy
2012-05-09 20:59           ` Kevin Groeneveld
2012-05-10 13:07             ` Solomon Peachy
2012-05-10 20:03               ` Kevin Groeneveld
     [not found] <983b0e2d75af161b8e4dec02fc3497926a0080df-submit>
2012-03-02 20:26 ` Dmitry Tarnyagin
2012-05-09  6:58   ` Dmitry Tarnyagin
2012-05-31  5:45     ` Janusz Dziedzic
2012-07-05 18:16       ` Steev Klimaszewski
2012-07-06 20:18         ` John W. Linville
2012-12-11 23:23           ` Solomon Peachy
2012-12-12 14:40             ` Kalle Valo
2012-12-12 15:13             ` Christian Lamparter
2012-12-12 16:18               ` Solomon Peachy
2012-12-12 16:20                 ` Johannes Berg
2012-12-13 14:53                   ` Solomon Peachy
2012-12-12 18:19             ` John W. Linville

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=CABF+-6UgQek50abaLnUsBh3LEccG2Pd1vFQDiLyxgcky-JN4Ag@mail.gmail.com \
    --to=kgroeneveld@gmail.com \
    --cc=dmitry.tarnyagin@stericsson.com \
    --cc=linux-wireless@vger.kernel.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 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).