From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Janusz Dziedzic <janusz.dziedzic@tieto.com>
Cc: Tomasz Tajmajer <tt@elnovel.com>, ath10k@lists.infradead.org
Subject: Re: [BUG] QWLE900V5-18 - cannot achievie 3 spatial streams link
Date: Mon, 9 Dec 2013 11:04:56 +0200 [thread overview]
Message-ID: <874n6i1jk7.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CALhHN=qPRgc-FaKbazdAmmxvi+YXxoFOp2Ax=x0iDp0LXknjHA@mail.gmail.com> (Janusz Dziedzic's message of "Fri, 6 Dec 2013 18:32:52 +0100")
Janusz Dziedzic <janusz.dziedzic@tieto.com> writes:
> On 6 December 2013 17:33, Tomasz Tajmajer <tt@elnovel.com> wrote:
>> Hi,
>>
>> Recently, I've been making quite a lot of tests with two QWLE900V5-18 cards.
>> I had some issues with the drivers (e.g. regarding the regulatory domain),
>> but I've managed to fix them on my own. However, there is one issue that I
>> cannot deal with.
>> I'm trying to get the highest throughput possible using 3x3 MIMO. The
>> problem is that the wifi card does not set higher rates than 2x433.3Mbps
>> (MCS 9, VHT-NSS 2). The specification says that it should be possible to
>> have 3 spatial streams.
>> First, I thought it is a problem with some options of hostapd, but hostapd
>> even does not allows me to set the [RX-STBC-12] or [RX-STBC-123] options.
>> Only [RX-STBC-1] may be set in the configuration (what in fact, does not
>> disallows the 2x433.3Mbps link, which is another issue).
>> Driver info shows that the driver should support 3 spatial streams.
>> I am not sure where is the problem, is it some bug in hostapd, which forces
>> the card to use 2 spatial streams only or is it the driver, which does not
>> enable 3 streams when it is possible. The physical connectivity (antennas
>> etc.) is not the problem AFAIK.
>>
>
> When sta assoc to ap you will get dbg mesg (you can enable this eg.
> when loading ath10k_core module with param - debug_mask).
> "mac ht peer %pM mcs cnt %d nss %d\n" - nss is interesting here
This debug message is enabled with ATH10K_DBG_MAC. More info here:
http://wireless.kernel.org/en/users/Drivers/ath10k/debug
> Also rx_mcs_set for STA from ath10k_peer_assoc_h_vht() could be
> interesting - unfortunetly we don't print this. But you can print
> this.
Indeed, we should include that to the message as well.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2013-12-09 9:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-06 16:33 [BUG] QWLE900V5-18 - cannot achievie 3 spatial streams link Tomasz Tajmajer
2013-12-06 17:25 ` Adrian Chadd
2013-12-06 17:32 ` Janusz Dziedzic
2013-12-09 9:04 ` Kalle Valo [this message]
2013-12-09 10:03 ` Tomasz Tajmajer
2013-12-09 10:13 ` Michal Kazior
2013-12-09 11:29 ` Tomasz Tajmajer
2013-12-09 12:10 ` Tomasz Tajmajer
2013-12-11 12:19 ` Tomasz Tajmajer
2013-12-11 19:43 ` Janusz Dziedzic
2013-12-11 19:51 ` Janusz Dziedzic
2013-12-12 11:42 ` Tomasz Tajmajer
2013-12-12 15:01 ` Tomasz Tajmajer
2013-12-13 6:17 ` Michal Kazior
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=874n6i1jk7.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=janusz.dziedzic@tieto.com \
--cc=tt@elnovel.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