All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	ath10k <ath10k@lists.infradead.org>
Subject: VHT 160Mhz and nss related config.
Date: Fri, 10 Feb 2017 14:58:31 -0800	[thread overview]
Message-ID: <0082a9e3-83f3-9bc3-af43-b890b91cfd93@candelatech.com> (raw)

So, it appears that the ath10k QCA9984 4x4 160Mhz chip can do 4x4 MIMO at VHT80, but
it can do only 2x2 MIMO at VHT160/80+80.

When configuring a peer, we need to tell the firmware the number of spatial streams
of the peer at VHT160 and at VHT80 and lower.  They are not the same value.

I cannot think of any standard way to get this information based on VHT capabilities
and such.  Currently, one could just assume VHT160 NSS is 1/2 of the VHT80 NSS,
but that is unlikely to be true for all vendors.

Any ideas?

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

WARNING: multiple messages have this Message-ID (diff)
From: Ben Greear <greearb@candelatech.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	ath10k <ath10k@lists.infradead.org>
Subject: VHT 160Mhz and nss related config.
Date: Fri, 10 Feb 2017 14:58:31 -0800	[thread overview]
Message-ID: <0082a9e3-83f3-9bc3-af43-b890b91cfd93@candelatech.com> (raw)

So, it appears that the ath10k QCA9984 4x4 160Mhz chip can do 4x4 MIMO at VHT80, but
it can do only 2x2 MIMO at VHT160/80+80.

When configuring a peer, we need to tell the firmware the number of spatial streams
of the peer at VHT160 and at VHT80 and lower.  They are not the same value.

I cannot think of any standard way to get this information based on VHT capabilities
and such.  Currently, one could just assume VHT160 NSS is 1/2 of the VHT80 NSS,
but that is unlikely to be true for all vendors.

Any ideas?

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


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

             reply	other threads:[~2017-02-10 22:58 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-10 22:58 Ben Greear [this message]
2017-02-10 22:58 ` VHT 160Mhz and nss related config Ben Greear
     [not found] ` <CAJ-Vmo=-JBrkmUPcYrRbARYuWv_=-MeQpPwAN_0J3v8pA5mPnw@mail.gmail.com>
2017-02-10 23:26   ` Ben Greear
2017-02-10 23:26     ` Ben Greear
2017-02-11  4:22 ` Sebastian Gottschall
2017-02-11  4:22   ` Sebastian Gottschall
2017-02-11  4:37   ` Adrian Chadd
2017-02-11  4:37     ` Adrian Chadd
2017-02-11 17:58     ` Ben Greear
2017-02-11 17:58       ` Ben Greear
2017-02-11 18:21       ` Sebastian Gottschall
2017-02-11 18:21         ` Sebastian Gottschall
2017-02-11 19:38         ` Ben Greear
2017-02-11 19:38           ` Ben Greear
2017-02-12 10:56           ` Sebastian Gottschall
2017-02-12 10:56             ` Sebastian Gottschall
2017-02-12 16:05             ` Ben Greear
2017-02-12 16:05               ` Ben Greear
2017-02-12 20:21               ` Sebastian Gottschall
2017-02-12 20:21                 ` Sebastian Gottschall
2017-02-13 19:56         ` Ben Greear
2017-02-13 19:56           ` Ben Greear
2017-02-13 21:19           ` Sebastian Gottschall
2017-02-13 21:19             ` Sebastian Gottschall
2017-02-13 22:48           ` Sebastian Gottschall
2017-02-13 22:48             ` Sebastian Gottschall
2017-02-13 23:12             ` Ben Greear
2017-02-13 23:12               ` Ben Greear
2017-02-14 10:19               ` Sebastian Gottschall
2017-02-14 10:19                 ` Sebastian Gottschall
2017-02-13  7:06 ` Johannes Berg
2017-02-13  7:06   ` Johannes Berg
2017-02-13 19:21   ` Ben Greear
2017-02-13 19:21     ` Ben Greear
2017-02-13 19:27     ` Adrian Chadd
2017-02-13 19:27       ` Adrian Chadd
2017-02-13 19:37     ` Johannes Berg
2017-02-13 19:37       ` Johannes Berg
2017-02-13 19:42       ` Ben Greear
2017-02-13 19:42         ` Ben Greear
2017-02-13 19:51         ` Johannes Berg
2017-02-13 19:51           ` 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=0082a9e3-83f3-9bc3-af43-b890b91cfd93@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ath10k@lists.infradead.org \
    --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.