All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: greearb@candelatech.com
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH v2 05/10] ath10k: apply chainmask settings to vdev on creation.
Date: Wed, 26 Nov 2014 08:25:37 +0200	[thread overview]
Message-ID: <87bnnuzdem.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1411507045-18973-5-git-send-email-greearb@candelatech.com> (greearb@candelatech.com's message of "Tue, 23 Sep 2014 14:17:20 -0700")

greearb@candelatech.com writes:

> From: Ben Greear <greearb@candelatech.com>
>
> It appears it takes more than just setting the
> hardware's chainmask to make things work well.  Without
> this patch, a vdev would only use 1x1 rates when chainmask
> was set to 0x3.
>
> Setting the 'nss' (number of spatial streams) on the vdev
> helps the firmware's rate-control algorithm work properly.
>
> Tested on CT firmware, but probably this works (and
> is required) on normal firmware.
>
> Signed-off-by: Ben Greear <greearb@candelatech.com>
> ---
>
> v2:  Add warning if chainmask is set to probably-invalid configuration.
>   Also, from a quick test, it appears you cannot even set the chainmask
>   using 'iw' when vdevs are active.

Thanks, applied.

-- 
Kalle Valo

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: <greearb@candelatech.com>
Cc: <linux-wireless@vger.kernel.org>, <ath10k@lists.infradead.org>
Subject: Re: [PATCH v2 05/10] ath10k: apply chainmask settings to vdev on creation.
Date: Wed, 26 Nov 2014 08:25:37 +0200	[thread overview]
Message-ID: <87bnnuzdem.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1411507045-18973-5-git-send-email-greearb@candelatech.com> (greearb@candelatech.com's message of "Tue, 23 Sep 2014 14:17:20 -0700")

greearb@candelatech.com writes:

> From: Ben Greear <greearb@candelatech.com>
>
> It appears it takes more than just setting the
> hardware's chainmask to make things work well.  Without
> this patch, a vdev would only use 1x1 rates when chainmask
> was set to 0x3.
>
> Setting the 'nss' (number of spatial streams) on the vdev
> helps the firmware's rate-control algorithm work properly.
>
> Tested on CT firmware, but probably this works (and
> is required) on normal firmware.
>
> Signed-off-by: Ben Greear <greearb@candelatech.com>
> ---
>
> v2:  Add warning if chainmask is set to probably-invalid configuration.
>   Also, from a quick test, it appears you cannot even set the chainmask
>   using 'iw' when vdevs are active.

Thanks, applied.

-- 
Kalle Valo

  reply	other threads:[~2014-11-26  6:26 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-23 21:17 [PATCH v2 01/10] ath10k: use 64-bit vdev map greearb
2014-09-23 21:17 ` greearb
2014-09-23 21:17 ` [PATCH v2 02/10] ath10k: add helper method to grab debug stats greearb
2014-09-23 21:17   ` greearb
2014-09-23 21:17 ` [PATCH v2 03/10] ath10k: support ethtool stats greearb
2014-09-23 21:17   ` greearb
2014-09-24  7:44   ` Michal Kazior
2014-09-24  7:44     ` Michal Kazior
2014-09-24 14:37     ` Ben Greear
2014-09-24 14:37       ` Ben Greear
2014-09-29  8:21       ` Kalle Valo
2014-09-29  8:21         ` Kalle Valo
2014-09-29 16:07         ` Ben Greear
2014-09-29 16:07           ` Ben Greear
2014-09-23 21:17 ` [PATCH v2 04/10] ath10k: make firmware text debug messages more verbose greearb
2014-09-23 21:17   ` greearb
2014-11-22 15:28   ` Kalle Valo
2014-11-22 15:28     ` Kalle Valo
2014-11-22 16:07     ` Ben Greear
2014-11-22 16:07       ` Ben Greear
2014-11-24 15:18       ` Kalle Valo
2014-11-24 15:18         ` Kalle Valo
2014-11-24 14:19   ` Kalle Valo
2014-11-24 14:19     ` Kalle Valo
2014-09-23 21:17 ` [PATCH v2 05/10] ath10k: apply chainmask settings to vdev on creation greearb
2014-09-23 21:17   ` greearb
2014-11-26  6:25   ` Kalle Valo [this message]
2014-11-26  6:25     ` Kalle Valo
2014-09-23 21:17 ` [PATCH v2 06/10] ath10k: use configured nss instead of max nss greearb
2014-09-23 21:17   ` greearb
2014-11-04 19:55   ` Ben Greear
2014-11-04 19:55     ` Ben Greear
2014-11-13 13:22     ` Kalle Valo
2014-11-13 13:22       ` Kalle Valo
2014-11-26  6:26   ` Kalle Valo
2014-11-26  6:26     ` Kalle Valo
2014-09-23 21:17 ` [PATCH v2 07/10] ath10k: add fw-powerup-fail to ethtool stats greearb
2014-09-23 21:17   ` greearb
2014-09-29  8:24   ` Kalle Valo
2014-09-29  8:24     ` Kalle Valo
2014-09-29 16:05     ` Ben Greear
2014-09-29 16:05       ` Ben Greear
2014-09-30 12:27       ` Michal Kazior
2014-09-30 12:27         ` Michal Kazior
2014-09-30 15:53         ` Ben Greear
2014-09-30 15:53           ` Ben Greear
2014-09-23 21:17 ` [PATCH v2 08/10] ath10k: support CT firmware flag greearb
2014-09-23 21:17   ` greearb
2014-09-23 21:17 ` [PATCH v2 09/10] ath10k: always request htc tx replenishment greearb
2014-09-23 21:17   ` greearb
2014-09-23 21:17 ` [PATCH v2 10/10] ath10k: request firmware flush in ath10k_flush greearb
2014-09-23 21:17   ` greearb
2014-10-01  8:22 ` [PATCH v2 01/10] ath10k: use 64-bit vdev map Kalle Valo
2014-10-01  8:22   ` Kalle Valo

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=87bnnuzdem.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath10k@lists.infradead.org \
    --cc=greearb@candelatech.com \
    --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 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.