From: Johannes Berg <johannes@sipsolutions.net>
To: Victor Goldenshtein <victorg@ti.com>
Cc: linux-wireless@vger.kernel.org, kgiori@qca.qualcomm.com,
mcgrof@frijolero.org, zefir.kurtisi@neratec.com,
adrian.chadd@gmail.com, j@w1.fi, coelho@ti.com, igalc@ti.com,
adrian@freebsd.org, nbd@nbd.name,
simon.wunderlich@s2003.tu-chemnitz.de
Subject: Re: [PATCH v4 5/6] nl80211/cfg80211: add ap channel switch command
Date: Mon, 05 Nov 2012 16:27:25 +0100 [thread overview]
Message-ID: <1352129245.9466.21.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <50922AA3.7000404@ti.com>
On Thu, 2012-11-01 at 09:54 +0200, Victor Goldenshtein wrote:
> >> Yes it works with our 12xx, in the 12xx the FW (upon channel switch
> >> command) is responsible to decrement the channel switch count in the
> >> beacon CSA IE and to remove the CSA IE from the beacon once device moves
> >> to the new channel (+ to updates the DS).
> >
> > So ... you've made this kind of behaviour a mandatory part of the
> > userspace API. Where is it documented then? How will it work with other
> > devices?
>
> It's should work the same with other devices, each device should
> implement AP channel switch op according the spec, the implementation
> can be hardware/driver depended. I just mentioned how we do it in our
> devices, which I think is the right way without introducing any races
> (as you mentioned), So no behavior enforcement here as long as it
> according the spec.
I don't think that's how it works ... you should describe what is
expected of the driver in the right API documentation. Even saying
"implement the procedures as described in 802.11-2012 section ..." could
be sufficient, but I think that needs to be there.
johannes
next prev parent reply other threads:[~2012-11-05 15:26 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-14 14:48 [PATCH v4 0/6] nl/cfg/mac80211: add DFS master ability Victor Goldenshtein
2012-10-14 14:48 ` [PATCH v4 1/6] nl80211/cfg80211: add radar detection command/event Victor Goldenshtein
2012-10-16 19:01 ` Johannes Berg
2012-10-17 16:20 ` Zefir Kurtisi
2012-10-17 16:23 ` Johannes Berg
2012-10-21 16:40 ` Victor Goldenshtein
2012-10-22 12:55 ` Johannes Berg
2012-11-01 7:54 ` Victor Goldenshtein
2012-11-05 15:21 ` Johannes Berg
2012-11-13 15:04 ` Victor Goldenshtein
2012-11-13 18:05 ` Simon Wunderlich
2012-11-20 15:14 ` Victor Goldenshtein
2012-11-26 10:52 ` Johannes Berg
2012-11-14 11:19 ` Johannes Berg
2012-11-20 15:15 ` Victor Goldenshtein
2012-11-14 12:32 ` Michal Kazior
2012-11-14 12:38 ` Johannes Berg
2012-11-20 15:15 ` Victor Goldenshtein
2012-11-26 10:51 ` Johannes Berg
2012-10-14 14:48 ` [PATCH v4 2/6] mac80211: " Victor Goldenshtein
2012-10-14 14:48 ` [PATCH v4 3/6] nl80211/cfg80211: add ability to enable TX on op-channel Victor Goldenshtein
2012-10-14 14:48 ` [PATCH v4 4/6] mac80211: " Victor Goldenshtein
2012-10-16 19:03 ` Johannes Berg
2012-10-21 16:40 ` Victor Goldenshtein
2012-10-14 14:48 ` [PATCH v4 5/6] nl80211/cfg80211: add ap channel switch command Victor Goldenshtein
2012-10-16 19:06 ` Johannes Berg
2012-10-21 16:40 ` Victor Goldenshtein
2012-10-22 12:52 ` Johannes Berg
2012-11-01 7:54 ` Victor Goldenshtein
2012-11-05 15:27 ` Johannes Berg [this message]
2012-11-13 15:04 ` Victor Goldenshtein
2012-10-23 6:20 ` Michal Kazior
2012-11-01 7:54 ` Victor Goldenshtein
2012-11-01 17:15 ` Adrian Chadd
2012-11-01 19:32 ` Johannes Berg
2012-11-05 15:29 ` Johannes Berg
2012-11-13 15:04 ` Victor Goldenshtein
2012-10-14 14:48 ` [PATCH v4 6/6] mac80211: add ap channel switch command/event Victor Goldenshtein
2012-10-16 19:07 ` Johannes Berg
2012-10-21 16:40 ` Victor Goldenshtein
2012-10-22 12:56 ` Johannes Berg
2012-11-01 7:54 ` Victor Goldenshtein
2012-11-05 15:23 ` Johannes Berg
2012-11-13 15:04 ` Victor Goldenshtein
2012-11-14 11:23 ` Johannes Berg
2012-11-14 12:19 ` Michal Kazior
2012-11-14 12:38 ` Johannes Berg
2012-11-20 15:15 ` Victor Goldenshtein
2012-11-26 10:50 ` Johannes Berg
2012-11-20 15:15 ` Victor Goldenshtein
2012-11-26 10:50 ` Johannes Berg
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=1352129245.9466.21.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=adrian.chadd@gmail.com \
--cc=adrian@freebsd.org \
--cc=coelho@ti.com \
--cc=igalc@ti.com \
--cc=j@w1.fi \
--cc=kgiori@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@frijolero.org \
--cc=nbd@nbd.name \
--cc=simon.wunderlich@s2003.tu-chemnitz.de \
--cc=victorg@ti.com \
--cc=zefir.kurtisi@neratec.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.