linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avinash Patil <patila@marvell.com>
To: <linux-wireless@vger.kernel.org>
Cc: <akarwar@marvell.com>, <cluo@marvell.com>, <gaoqs@marvell.com>,
	Avinash Patil <patila@marvell.com>
Subject: [PATCH v2 00/10] mwifiex: DFS support for mwifiex AP
Date: Wed, 28 Jan 2015 15:54:15 +0530	[thread overview]
Message-ID: <1422440665-3940-1-git-send-email-patila@marvell.com> (raw)

This patch series adds DFS support for mwifiex AP. Series include
patches to handle cfg80211 start_radar_detection and channel_switch
handlers. First 5 patches are actually refactoring effort. Patch6-10
add these handlers and other DFS handling.

Avinash Patil (10):
  mwifiex: do not send regulatory update while starting AP
  mwifiex: store AP configuration in private structure
  mwifiex: update IEs after AP has started
  mwifiex: refactor start_ap handler
  mwifiex: separate function for parsing head and tail IEs
  mwifiex: add cfg80211 start_radar_detection handler
  mwifiex: support for channel report for radar detection
  mwifiex: handle radar detect event from FW
  mwifiex: channel switch support for mwifiex
  mwifiex: 11h handling for AP interface

 drivers/net/wireless/mwifiex/11h.c         | 196 +++++++++++++++++++++++-
 drivers/net/wireless/mwifiex/cfg80211.c    | 232 +++++++++++++++++++++--------
 drivers/net/wireless/mwifiex/decl.h        |  11 ++
 drivers/net/wireless/mwifiex/fw.h          |  58 ++++++++
 drivers/net/wireless/mwifiex/ie.c          |  89 ++++++-----
 drivers/net/wireless/mwifiex/init.c        |   3 +
 drivers/net/wireless/mwifiex/main.c        |   2 +-
 drivers/net/wireless/mwifiex/main.h        |  31 +++-
 drivers/net/wireless/mwifiex/sta_cmd.c     |   4 +
 drivers/net/wireless/mwifiex/sta_cmdresp.c |   2 +
 drivers/net/wireless/mwifiex/sta_event.c   |  10 ++
 drivers/net/wireless/mwifiex/uap_cmd.c     |  70 +++++++++
 drivers/net/wireless/mwifiex/uap_event.c   |   8 +
 13 files changed, 619 insertions(+), 97 deletions(-)

-- 
1.8.1.4


             reply	other threads:[~2015-01-28  4:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-28 10:24 Avinash Patil [this message]
2015-01-28 10:24 ` [PATCH v2 01/10] mwifiex: do not send regulatory update while starting AP Avinash Patil
2015-01-29  8:26   ` [v2, " Kalle Valo
2015-01-28 10:24 ` [PATCH v2 02/10] mwifiex: store AP configuration in private structure Avinash Patil
2015-01-28 10:24 ` [PATCH v2 03/10] mwifiex: update IEs after AP has started Avinash Patil
2015-01-28 10:24 ` [PATCH v2 04/10] mwifiex: refactor start_ap handler Avinash Patil
2015-01-28 10:24 ` [PATCH v2 05/10] mwifiex: separate function for parsing head and tail IEs Avinash Patil
2015-01-28 10:24 ` [PATCH v2 06/10] mwifiex: add cfg80211 start_radar_detection handler Avinash Patil
2015-01-28 10:24 ` [PATCH v2 07/10] mwifiex: support for channel report for radar detection Avinash Patil
2015-01-28 10:24 ` [PATCH v2 08/10] mwifiex: handle radar detect event from FW Avinash Patil
2015-01-28 10:24 ` [PATCH v2 09/10] mwifiex: channel switch support for mwifiex Avinash Patil
2015-01-28 10:24 ` [PATCH v2 10/10] mwifiex: 11h handling for AP interface Avinash Patil

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=1422440665-3940-1-git-send-email-patila@marvell.com \
    --to=patila@marvell.com \
    --cc=akarwar@marvell.com \
    --cc=cluo@marvell.com \
    --cc=gaoqs@marvell.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).