ATH11K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <seckelmann@datto.com>
To: ath11k@lists.infradead.org
Subject: Re: [RFC PATCH v6 2/2] ath11k: Disable SU support in meshpoint mode
Date: Thu, 19 Sep 2019 15:27:10 +0200	[thread overview]
Message-ID: <4859810.gV9nB57MYN@bentobox> (raw)
In-Reply-To: <20190813092726.28074-3-sven@narfation.org>


[-- Attachment #1.1: Type: text/plain, Size: 799 bytes --]

On Tuesday, 13 August 2019 11:27:26 CEST Sven Eckelmann wrote:
> From: Sven Eckelmann <seckelmann@datto.com>
> 
> The firmware WLAN.HK.2.1.0.1-00629-QCAHKSWPL_SILICONZ-1 often stops sending
> data on 5GHz when SU support is advertised. A simple throughput benchmark
> will end up at only a couple hundred kilobytes per second (when finishing
> at all).
> 
> Disabling SU related flags works around this problem and allowed a maximum
> throughput of ~450 MBit/s in a simple test setup with an HK01 over air.
> 
> Signed-off-by: Sven Eckelmann <seckelmann@datto.com>

I've just checked with WLAN.HK.2.0.0.1-00043-QCAHKSWPL_SILICONZ-1 (which is a 
newer version than WLAN.HK.2.1.0.1-00629-QCAHKSWPL_SILICONZ-1) and wasn't able 
anymore to reproduce the SU related problems on 5GHz.

Kind regards,
	Sven

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 146 bytes --]

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

      reply	other threads:[~2019-09-19 13:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-13  9:27 [RFC PATCH v6 0/2] ath11k: HE mesh support Sven Eckelmann
2019-08-13  9:27 ` [RFC PATCH v6 1/2] ath11k: register HE mesh capabilities Sven Eckelmann
2019-08-13  9:27 ` [RFC PATCH v6 2/2] ath11k: Disable SU support in meshpoint mode Sven Eckelmann
2019-09-19 13:27   ` Sven Eckelmann [this message]

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=4859810.gV9nB57MYN@bentobox \
    --to=seckelmann@datto.com \
    --cc=ath11k@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox