All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven.eckelmann@openmesh.com>
To: akolli@codeaurora.org
Cc: Anilkumar Kolli <akolli@qti.qualcomm.com>,
	linux-wireless@vger.kernel.org, ath10k@lists.infradead.org,
	Kalle Valo <kvalo@qca.qualcomm.com>,
	Sebastian Gottschall <s.gottschall@dd-wrt.com>,
	Peter Oh <peter.oh@bowerswilkins.com>
Subject: Re: ath10k: Fix reported HT MCS rates with NSS > 1
Date: Tue, 05 Dec 2017 10:16:03 +0100	[thread overview]
Message-ID: <1552472.kPg8TR0KAa@bentobox> (raw)
In-Reply-To: <bcebd30e279840a62b53043865d4db29@codeaurora.org>


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

On Dienstag, 21. November 2017 11:43:36 CET akolli@codeaurora.org wrote:
[...]
> > I think we should add a special case to not print the warning if mcs ==
> > 15 until we figure out what it means.
> 
> Fix identified in Firmware and will push ASAP.

Is it known when this will be released and for which firmware/HW versions? And 
will this also fix the legacy rate reports? At least in the moment, 
ath10k_htt_fetch_peer_stats seems to generate following on QCA4019 for some 
clients:

    [ 1627.720177] ath10k_ahb a800000.wifi: Invalid legacy rate 26 peer stats
    [ 1632.010290] ath10k_ahb a800000.wifi: Invalid legacy rate 26 peer stats

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 --]

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

WARNING: multiple messages have this Message-ID (diff)
From: Sven Eckelmann <sven.eckelmann@openmesh.com>
To: akolli@codeaurora.org
Cc: Kalle Valo <kvalo@qca.qualcomm.com>,
	Peter Oh <peter.oh@bowerswilkins.com>,
	Sebastian Gottschall <s.gottschall@dd-wrt.com>,
	ath10k@lists.infradead.org,
	Anilkumar Kolli <akolli@qti.qualcomm.com>,
	linux-wireless@vger.kernel.org
Subject: Re: ath10k: Fix reported HT MCS rates with NSS > 1
Date: Tue, 05 Dec 2017 10:16:03 +0100	[thread overview]
Message-ID: <1552472.kPg8TR0KAa@bentobox> (raw)
In-Reply-To: <bcebd30e279840a62b53043865d4db29@codeaurora.org>

[-- Attachment #1: Type: text/plain, Size: 662 bytes --]

On Dienstag, 21. November 2017 11:43:36 CET akolli@codeaurora.org wrote:
[...]
> > I think we should add a special case to not print the warning if mcs ==
> > 15 until we figure out what it means.
> 
> Fix identified in Firmware and will push ASAP.

Is it known when this will be released and for which firmware/HW versions? And 
will this also fix the legacy rate reports? At least in the moment, 
ath10k_htt_fetch_peer_stats seems to generate following on QCA4019 for some 
clients:

    [ 1627.720177] ath10k_ahb a800000.wifi: Invalid legacy rate 26 peer stats
    [ 1632.010290] ath10k_ahb a800000.wifi: Invalid legacy rate 26 peer stats

Kind regards,
	Sven

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

  reply	other threads:[~2017-12-05  9:16 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-11  9:09 [PATCH] ath10k: Fix reported HT MCS rates with NSS > 1 Sven Eckelmann
2017-05-11  9:09 ` Sven Eckelmann
2017-05-11  9:39 ` Arend Van Spriel
2017-05-11  9:39   ` Arend Van Spriel
2017-05-11 10:08   ` Sven Eckelmann
2017-05-11 10:08     ` Sven Eckelmann
2017-05-23 15:28 ` Kalle Valo
2017-05-23 15:28   ` Kalle Valo
2017-11-05  9:22   ` Sebastian Gottschall
2017-11-05  9:22     ` Sebastian Gottschall
2017-11-06  8:23     ` Sven Eckelmann
2017-11-06  8:23       ` Sven Eckelmann
2017-11-06  8:28       ` Sebastian Gottschall
2017-11-06  8:28         ` Sebastian Gottschall
2017-11-06  9:02         ` Sven Eckelmann
2017-11-06  9:02           ` Sven Eckelmann
2017-11-06 21:25           ` Peter Oh
2017-11-06 21:25             ` Peter Oh
2017-11-20 12:10             ` Kalle Valo
2017-11-20 12:10               ` Kalle Valo
2017-11-21  6:13               ` akolli
2017-11-21  6:13                 ` akolli
2017-12-05  9:16                 ` Sven Eckelmann [this message]
2017-12-05  9:16                   ` Sven Eckelmann

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=1552472.kPg8TR0KAa@bentobox \
    --to=sven.eckelmann@openmesh.com \
    --cc=akolli@codeaurora.org \
    --cc=akolli@qti.qualcomm.com \
    --cc=ath10k@lists.infradead.org \
    --cc=kvalo@qca.qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=peter.oh@bowerswilkins.com \
    --cc=s.gottschall@dd-wrt.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 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.