Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Manoharan, Rajkumar" <rmanohar@qca.qualcomm.com>
To: Johannes Berg <johannes@sipsolutions.net>,
	"Manoharan, Sujith" <c_manoha@qca.qualcomm.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: RE: mac80211 20/40 coexist
Date: Fri, 16 Mar 2012 18:39:29 +0000	[thread overview]
Message-ID: <8F3AF1C9F856774F8C8D67AA7EDFEC8801E3040B@aphydexd01b> (raw)
In-Reply-To: <1331902885.6753.10.camel@jlt3.sipsolutions.net>

> Hi,
> 
> [I'll also fold in your other email]
> 
> > Not calling hw_config could affect drivers like ath9k_htc where the rate control runs in the firmware.
> > Those drivers will update the rate control based on CHANGED_HT flag.
> 
> Yeah that's actually an interesting point -- but we have it wrong right
> now I think. Did you see Paul's recent patch? We really shouldn't be
> reconfiguring the channel if all we want is to stop transmitting 40 MHz,
> we should just update rate control only. Now for in-device rate control
> that isn't really possible today since they can't get rate_update(), but
> that means we should add a separate callback, I think?

Yes. I missed that. I am not sure about the new callback alone is sufficient. We have to issue a WMI command
to reconfigure the rc in firmware. If so, it needs firmware changes also. May be Sujith is the right person to answer
about ath9k_htc.

> > > If we do that, is it still necessary to stop the queues for it? It seems
> > > like it shouldn't.
> > 
> > Actually the queue stop was added to avoid mismatches b/w hw and rate control. But If you dont stop the queues
> > before the rate control change, the station might send the frames in different ht mode (for example ht40) wrt AP's ht mode (ht20).
> 
> Yes, but that's probably OK. It's going to do that anyway since there
> are still frames in the hardware queues, and those will go out without
> updated rate information. There can be no guarantee (without having some
> form of hardware assist) that from the point we receive a 20/40
> notification we'll send the right bandwidth.

Yes. Sounds fine.

-Rajkumar

  parent reply	other threads:[~2012-03-16 18:39 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-15 13:30 mac80211 20/40 coexist Johannes Berg
2012-03-15 20:49 ` Manoharan, Rajkumar
2012-03-16 13:01   ` Johannes Berg
2012-03-16 13:46     ` Johannes Berg
2012-03-16 18:39     ` Manoharan, Rajkumar [this message]
2012-03-18 10:19       ` Johannes Berg
2012-03-18 19:19         ` Adrian Chadd
2012-03-19  3:49           ` Sujith Manoharan
2012-03-19  4:49             ` Adrian Chadd
2012-03-19  4:59               ` Sujith Manoharan
2012-03-19  8:26             ` Johannes Berg
2012-03-19 10:08               ` Sujith Manoharan
2012-03-19 10:13                 ` Johannes Berg
2012-03-19  8:24           ` Johannes Berg
2012-03-19  2:55         ` Sujith Manoharan
2012-03-19  8:23           ` Johannes Berg
2012-03-19 10:04             ` Sujith Manoharan
2012-03-19 10:09               ` Johannes Berg
2012-03-19 10:32                 ` Sujith Manoharan
2012-03-19 11:12                   ` Johannes Berg
2012-03-19 12:18                     ` Johannes Berg
2012-03-20  4:39                       ` Sujith Manoharan
2012-03-20 11:32                         ` Johannes Berg
2012-03-20 15:26                           ` Sujith Manoharan

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=8F3AF1C9F856774F8C8D67AA7EDFEC8801E3040B@aphydexd01b \
    --to=rmanohar@qca.qualcomm.com \
    --cc=c_manoha@qca.qualcomm.com \
    --cc=johannes@sipsolutions.net \
    --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