From: Rajkumar Manoharan <rmanohar@codeaurora.org>
To: John Crispin <john@phrozen.org>
Cc: Rajkumar Manoharan <rmanohar@qti.qualcomm.com>,
ath11k@lists.infradead.org
Subject: Re: [RFC] ath11k: add HE rate reporting
Date: Thu, 30 May 2019 00:56:01 -0700 [thread overview]
Message-ID: <96d5a27d4ec109ef51301f280a0d227f@codeaurora.org> (raw)
In-Reply-To: <db697dab-7011-f550-d995-89cefd346369@phrozen.org>
On 2019-05-23 03:49, John Crispin wrote:
> On 23/05/2019 12:47, John Crispin wrote:
>> We need to figure out how to read the ru_alloc and DCM values from FW.
>
> Hi Rajkumar,
>
> could you help me figure out how to get the DCM/RU values in the FW
> reporting ? I have marked places them with TODO tags in the code
>
John,
Thanks for the patch. I dig further for DCM/RU. The HE information
can be retrieved only through PPDU stats.
Tx PPDU stats are processed through HTT event
(HTT_PPDU_STATS_USR_RATE_TLV).
Rx PPDU stats through monitor status ring
(ath11k_hal_rx_parse_mon_status_tlv).
Need to handle HAL_PHYRX_HE_SIG_A_SU, HAL_PHYRX_HE_SIG_B1_MU cases.
he info will be reported out of bound data path. Hope sta_statistics
will be
enough to populate to user application.
-Rajkumar
_______________________________________________
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
prev parent reply other threads:[~2019-05-30 7:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 10:47 [RFC] ath11k: add HE rate reporting John Crispin
2019-05-23 10:49 ` John Crispin
2019-05-30 7:56 ` Rajkumar Manoharan [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=96d5a27d4ec109ef51301f280a0d227f@codeaurora.org \
--to=rmanohar@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=john@phrozen.org \
--cc=rmanohar@qti.qualcomm.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.