linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luciano Coelho <coelho@ti.com>
To: "Levi, Shahar" <shahar_levi@ti.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] wl12xx: Add support for HW channel switch
Date: Tue, 27 Sep 2011 08:33:34 +0300	[thread overview]
Message-ID: <1317101614.2171.87.camel@cumari> (raw)
In-Reply-To: <CAHiDVwksE1pjwij9cJDbFjQ_6XVdk2X=ULPpvL4KBnJzqJVLUg@mail.gmail.com>

On Mon, 2011-09-26 at 13:29 +0300, Levi, Shahar wrote: 
> On Mon, Sep 26, 2011 at 9:25 AM, Luciano Coelho <coelho@ti.com> wrote:
> > On Sun, 2011-09-25 at 19:08 +0300, Levi, Shahar wrote:
> >> On Fri, Sep 23, 2011 at 1:59 PM, Luciano Coelho <coelho@ti.com> wrote:
> >> > I'm leaving this patch out for now until I understand this better.
> >> Do you prefer me to set v2 without that line or you could fix that in
> >> the apply stage?
> >
> > No need to send v2.  It seems that Victor will need this change for
> > something else he's working on, so I guess he can take it over once it
> > is needed.  I don't want to include this unless we have a good reason to
> > do it.
> There is a good reason to include this:
> a) It solve STA calibration issue in the FW in case of SW channel
> switch (Rx issues)

This is a good reason (fixing a bug) and should be mentioned in the
commit description.  Do we have more detailed information on this?


> b) This is FW support for channel switch with one command instead of
> using several commands: rate_policies, roc \ join...

This is an optimization and not entirely mandatory.  This is the only
thing I thought this patch was addressing (the commit message was not
very descriptive, so I could only assume).  At this stage (ie. close to
the merge window), I didn't want to assume the risk of a change just for
to optimize things a bit.  And, since I had my doubts about the block_tx
value, I decided not to include it.


> Our latest version pass full test cycle with that fix that solve CS issues.

Okay, once I get the answer from the firmware team about the block_tx
value, I'll fix up this patch and apply it.

Thanks for the explanantions.

-- 
Cheers,
Luca.


  reply	other threads:[~2011-09-27  5:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-08 10:01 [PATCH] wl12xx: Add support for HW channel switch Shahar Levi
2011-09-22 13:36 ` Luciano Coelho
2011-09-23 10:59   ` Luciano Coelho
2011-09-25 16:08     ` Levi, Shahar
2011-09-26  6:25       ` Luciano Coelho
2011-09-26  7:23         ` Victor Goldenshtein
2011-09-27  5:28           ` Luciano Coelho
2011-09-26 10:29         ` Levi, Shahar
2011-09-27  5:33           ` Luciano Coelho [this message]
2011-10-06 13:17 ` Luciano Coelho

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=1317101614.2171.87.camel@cumari \
    --to=coelho@ti.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=shahar_levi@ti.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;
as well as URLs for NNTP newsgroup(s).