From: "Owen Mesh." <owen.mesh@gmail.com>
To: Jeff Johnson <quic_jjohnson@quicinc.com>
Cc: Lingbo Kong <quic_lingbok@quicinc.com>,
ath12k@lists.infradead.org, Kalle Valo <kvalo@kernel.org>
Subject: Re: ath12k: driver does not show tx bitrate
Date: Thu, 21 Mar 2024 19:47:14 +0100 [thread overview]
Message-ID: <CAHohoUjWa8wNhdVTr_Vy8TxsMYqMKkabTuBPH8HhCjgnpciS5A@mail.gmail.com> (raw)
In-Reply-To: <f077d1cb-2704-42fe-a77d-b23d0d38a8fa@quicinc.com>
Yes, please!
On Thu, Mar 21, 2024 at 7:12 PM Jeff Johnson <quic_jjohnson@quicinc.com> wrote:
>
> On 3/20/2024 11:33 PM, Owen Mesh. wrote:
> > Thanks!
> >
> > I applied this patch.
> > It looks great for my configuration/platform!
> >
> > iw now shows 802.11be tx and rx bitrates:
> >
> > iw dev wlp6s0 link
> > Connected to d4:da:21:a8:06:7e (on wlp6s0)
> > SSID: NETGEAR65
> > freq: 5805.0
> > RX: 36791 bytes (185 packets)
> > TX: 9111 bytes (73 packets)
> > signal: -27 dBm
> > rx bitrate: 1801.4 MBit/s 80MHz EHT-MCS 11 EHT-NSS 3 EHT-GI 0
> > tx bitrate: 1200.9 MBit/s 80MHz EHT-MCS 11 EHT-NSS 2 EHT-GI 0
> >
> > bss flags: short-slot-time
> > dtim period: 1
> > beacon int: 100
> >
> > Best regards
>
> Is it OK to add the following to the final commit:
> Tested-by: Owen Mesh <owen.mesh@gmail.com>
>
prev parent reply other threads:[~2024-03-21 18:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-20 15:47 ath12k: driver does not show tx bitrate Owen Mesh.
2024-03-20 16:21 ` Kalle Valo
2024-03-20 16:36 ` Owen Mesh.
2024-03-20 17:08 ` Owen Mesh.
2024-03-20 17:43 ` Owen Mesh.
2024-03-21 2:32 ` Lingbo Kong
2024-03-21 6:33 ` Owen Mesh.
2024-03-21 18:12 ` Jeff Johnson
2024-03-21 18:47 ` Owen Mesh. [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=CAHohoUjWa8wNhdVTr_Vy8TxsMYqMKkabTuBPH8HhCjgnpciS5A@mail.gmail.com \
--to=owen.mesh@gmail.com \
--cc=ath12k@lists.infradead.org \
--cc=kvalo@kernel.org \
--cc=quic_jjohnson@quicinc.com \
--cc=quic_lingbok@quicinc.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).