All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Maxime Bizon <mbizon@freebox.fr>
Cc: ath10k@lists.infradead.org,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] ath10k: fix misreported tx bandwidth for 160Mhz
Date: Mon, 16 May 2022 19:11:53 +0300	[thread overview]
Message-ID: <87o7zx4fue.fsf@kernel.org> (raw)
In-Reply-To: <cd2735a40da7f4fcc5323e3fca3775e7b5402ece.camel@freebox.fr> (Maxime Bizon's message of "Mon, 16 May 2022 17:23:43 +0200")

Maxime Bizon <mbizon@freebox.fr> writes:

> Because of this missing switch case, 160Mhz transmit was reported as
> 20Mhz, leading to wrong airtime calculation and AQL limiting max
> throughput.
>
> Signed-off-by: Maxime Bizon <mbizon@freebox.fr>

On what ath10k hardware and afirmware version did you test this? I can
add that to the commit log.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@kernel.org>
To: Maxime Bizon <mbizon@freebox.fr>
Cc: ath10k@lists.infradead.org,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] ath10k: fix misreported tx bandwidth for 160Mhz
Date: Mon, 16 May 2022 19:11:53 +0300	[thread overview]
Message-ID: <87o7zx4fue.fsf@kernel.org> (raw)
In-Reply-To: <cd2735a40da7f4fcc5323e3fca3775e7b5402ece.camel@freebox.fr> (Maxime Bizon's message of "Mon, 16 May 2022 17:23:43 +0200")

Maxime Bizon <mbizon@freebox.fr> writes:

> Because of this missing switch case, 160Mhz transmit was reported as
> 20Mhz, leading to wrong airtime calculation and AQL limiting max
> throughput.
>
> Signed-off-by: Maxime Bizon <mbizon@freebox.fr>

On what ath10k hardware and afirmware version did you test this? I can
add that to the commit log.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

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

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

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-16 15:23 [PATCH] ath10k: fix misreported tx bandwidth for 160Mhz Maxime Bizon
2022-05-16 15:23 ` Maxime Bizon
2022-05-16 16:11 ` Kalle Valo [this message]
2022-05-16 16:11   ` Kalle Valo
2022-05-16 16:23   ` Maxime Bizon
2022-05-16 16:23     ` Maxime Bizon
2022-05-16 16:35     ` Kalle Valo
2022-05-16 16:35       ` Kalle Valo
2022-05-22 12:28 ` Kalle Valo
2022-05-22 12:28   ` 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=87o7zx4fue.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=ath10k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mbizon@freebox.fr \
    /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.