Linux wireless drivers development
 help / color / mirror / Atom feed
From: Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>,
	Zefir Kurtisi <zefir.kurtisi@neratec.com>,
	linux-wireless@vger.kernel.org,
	mathias.kretschmer@fokus.fraunhofer.de,
	Simon Wunderlich <siwu@hrz.tu-chemnitz.de>
Subject: Re: [PATCH] mac80211: fix recalc_radar hwconf sync problem
Date: Mon, 8 Apr 2013 13:51:11 +0200	[thread overview]
Message-ID: <20130408115111.GA15594@pandem0nium> (raw)
In-Reply-To: <1365165364.8515.24.camel@jlt4.sipsolutions.net>

[-- Attachment #1: Type: text/plain, Size: 1417 bytes --]

On Fri, Apr 05, 2013 at 02:36:04PM +0200, Johannes Berg wrote:
> On Fri, 2013-04-05 at 14:16 +0200, Simon Wunderlich wrote:
> > On Fri, Apr 05, 2013 at 01:22:51PM +0200, Johannes Berg wrote:
> > > On Thu, 2013-04-04 at 20:22 +0200, Simon Wunderlich wrote:
> > > 
> > > > As far as I see, the problem happens when changing from a DFS to a non-DFS
> > > > channel. local->hw.conf.radar_enabled is true from the last (DFS) channel,
> > > > but the channel gets released when stopping the AP, and the channel context
> > > > is freed. 
> > > 
> > > At this point, why doesn't it disable hw.conf.radar_enabled? I really
> > > think it should?
> > 
> > As far as I see release_channel() -> unassign_vif_chanctx() -> ieee80211_recalc_radar_chanctx()
> > is called while the interface with radar enabled is still present, and therefore it is assumed
> > that the radar enable is still required.
> > 
> > We could reset local->hw.conf.radar_enabled ieee80211_free_chanctx() though, but IMHO the cleaner
> > way would be to properly initialize it when the the channel is used next time through
> > vif_use_channel().
> 
> I disagree, it would leave the hardware in a weird state -- idle but
> having to detect radars??
> 
> johannes

Well, you have a point ...

I'll look into it, it should be doable that the radar flag is always set
correctly. Please drop this patch for now.

Cheers,
	Simon

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2013-04-08 11:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-02 16:39 [PATCH] mac80211: fix recalc_radar hwconf sync problem Simon Wunderlich
2013-04-03 12:46 ` Johannes Berg
2013-04-04 13:38   ` Zefir Kurtisi
2013-04-04 18:22     ` Simon Wunderlich
2013-04-05 10:08       ` Zefir Kurtisi
2013-04-05 10:11         ` Zefir Kurtisi
2013-04-05 11:29         ` Simon Wunderlich
2013-04-05 12:11           ` Zefir Kurtisi
2013-04-05 11:22       ` Johannes Berg
2013-04-05 12:16         ` Simon Wunderlich
2013-04-05 12:36           ` Johannes Berg
2013-04-08 11:51             ` Simon Wunderlich [this message]
2013-04-08 12:09             ` [PATCHv2] " Simon Wunderlich
2013-04-08 14:17               ` Zefir Kurtisi
2013-04-08 14:29               ` Johannes Berg
2013-04-08 17:04                 ` [PATCHv3] " Simon Wunderlich
2013-04-08 17:53                   ` Antonio Quartulli
2013-04-08 20:43                     ` [PATCHv4] " Simon Wunderlich
2013-04-09  9: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=20130408115111.GA15594@pandem0nium \
    --to=simon.wunderlich@s2003.tu-chemnitz.de \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mathias.kretschmer@fokus.fraunhofer.de \
    --cc=siwu@hrz.tu-chemnitz.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox