linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luciano Coelho <luciano.coelho@nokia.com>
To: ext Shahar Levi <shahar_levi@ti.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2 03/03] wl1271: 11n Support, functionality and configuration ability
Date: Mon, 11 Oct 2010 16:55:56 +0300	[thread overview]
Message-ID: <1286805356.24158.3.camel@chilepepper> (raw)
In-Reply-To: <4CB1DAC8.6050609@ti.com>

On Sun, 2010-10-10 at 17:24 +0200, ext Shahar Levi wrote:
> >>  static const u8 *wl1271_band_rate_to_idx[] = {
> >> diff --git a/drivers/net/wireless/wl12xx/wl1271_rx.c
> b/drivers/net/wireless/wl12xx/wl1271_rx.c
> >> index 94da5dd..109a470 100644
> >> --- a/drivers/net/wireless/wl12xx/wl1271_rx.c
> >> +++ b/drivers/net/wireless/wl12xx/wl1271_rx.c
> >> @@ -53,6 +53,10 @@ static void wl1271_rx_status(struct wl1271 *wl,
> >>      status->band = wl->band;
> >>      status->rate_idx = wl1271_rate_to_idx(wl, desc->rate);
> >>  
> >> +    /* 11n support */
> >> +    if (desc->rate <= CONF_HW_RXTX_RATE_MCS0)
> >> +            status->flag |= RX_FLAG_HT;
> >> +
> >>      status->signal = desc->rssi;
> > 
> > Should this be #ifdef'ed also?
> 
> No, in case of HT not supported the HW will not set MCS rate.

True, but if you don't have the ifdef you're adding unnecessary code in
the RX data path.


> >> diff --git a/drivers/net/wireless/wl12xx/wl1271_tx.c
> b/drivers/net/wireless/wl12xx/wl1271_tx.c
> >> index 1b8295c..af54fef 100644
> >> --- a/drivers/net/wireless/wl12xx/wl1271_tx.c
> >> +++ b/drivers/net/wireless/wl12xx/wl1271_tx.c
> >> @@ -236,6 +236,15 @@ u32 wl1271_tx_enabled_rates_get(struct wl1271
> *wl, u32 rate_set)
> >>              rate_set >>= 1;
> >>      }
> >>  
> >> +    /* MCS rates indication are on bits 16 - 23 */
> >> +    rate_set >>= HW_HT_RATES_OFFSET - band->n_bitrates;
> >> +
> >> +    for (bit = 0; bit < 8; bit++) {
> >> +            if (rate_set & 0x1)
> >> +                    enabled_rates |= (CONF_HW_BIT_RATE_MCS_0 <<
> bit);
> >> +            rate_set >>= 1;
> >> +    }
> >> +
> > 
> > And this? #ifdef here as well, maybe? 
> 
> No, in case of HT not supported MCS bit in rate_set will not be set.

Same here, this loop will add more CPU cycles in the TX data path
unnecessarily.



-- 
Cheers,
Luca.


  reply	other threads:[~2010-10-11 13:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-06 18:08 [PATCH v2 00/03] wl1271: 11n Support, add support to 80211n spec Shahar Levi
2010-10-06 18:08 ` [PATCH v2] " Shahar Levi
2010-10-06 18:08 ` [PATCH v2 01/03] wl1271: 11n Support, Add Definitions Shahar Levi
2010-10-07 18:20   ` Luciano Coelho
2010-10-08 11:44     ` Luciano Coelho
2010-10-10 10:12     ` Shahar Levi
2010-10-06 18:08 ` [PATCH v2 02/03] wl1271: 11n Support, ACX Commands Shahar Levi
2010-10-07 18:37   ` Luciano Coelho
2010-10-10 10:26     ` Shahar Levi
2010-10-06 18:08 ` [PATCH v2 03/03] wl1271: 11n Support, functionality and configuration ability Shahar Levi
2010-10-06 18:21   ` Johannes Berg
2010-10-06 19:38     ` Levi, Shahar
2010-10-06 19:45       ` Johannes Berg
2010-10-08  9:05   ` Luciano Coelho
2010-10-10 15:24     ` Shahar Levi
2010-10-11 13:55       ` Luciano Coelho [this message]
2010-10-11 14:28         ` Shahar Levi

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=1286805356.24158.3.camel@chilepepper \
    --to=luciano.coelho@nokia.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).