From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Vasanthakumar Thiagarajan
<vasanthakumar.thiagarajan@oss.qualcomm.com>,
Roopni Devanathan <quic_rdevanat@quicinc.com>,
ath12k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org,
Saleemuddin Shaik <quic_saleemud@quicinc.com>
Subject: Re: [PATCH ath-next v2] wifi: ath12k: Add support for transmit histogram stats
Date: Thu, 26 Jun 2025 11:25:29 -0700 [thread overview]
Message-ID: <fca2def0-227b-4208-8104-abc40368f7fb@oss.qualcomm.com> (raw)
In-Reply-To: <cab5daaf-bafb-4df3-9e44-1d0e6dda0341@oss.qualcomm.com>
On 6/26/2025 11:18 AM, Jeff Johnson wrote:
> On 6/26/2025 10:20 AM, Vasanthakumar Thiagarajan wrote:
>> On 6/17/2025 4:51 PM, Roopni Devanathan wrote:
>>> From: Saleemuddin Shaik <quic_saleemud@quicinc.com>
>>> +struct ath12k_htt_tx_histogram_stats_tlv {
>>> + __le32 rate_retry_mcs_drop_cnt;
>>> + __le32 mcs_drop_rate[ATH12K_HTT_TX_PDEV_STATS_NUM_MCS_DROP_COUNTERS];
>>> + __le32 per_histogram_cnt[ATH12K_HTT_TX_PDEV_STATS_NUM_PER_COUNTERS];
>>> + __le32 low_latency_rate_cnt;
>>> + __le32 su_burst_rate_drop_cnt;
>>> + __le32 su_burst_rate_drop_fail_cnt;
>>> +};
>>
>> Since this strcuture represents the message format used between host and firmware, pls add
>> __packed annotation even though it may not have any effect in this case.
>
> looks like I missed this in a few other structs as well, at least:
> ath12k_htt_tx_pdev_rate_stats_tlv
> ath12k_htt_rx_pdev_rate_ext_stats_tlv
>
> perhaps i'll take this as-is and then have another patch that adds __packed to
> all _tlv structs that are missing it?
actually let me fix this instance in pending, and we can fix other existing
ones separately
/jeff
next prev parent reply other threads:[~2025-06-26 18:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 11:21 [PATCH ath-next v2] wifi: ath12k: Add support for transmit histogram stats Roopni Devanathan
2025-06-26 17:20 ` Vasanthakumar Thiagarajan
2025-06-26 18:18 ` Jeff Johnson
2025-06-26 18:25 ` Jeff Johnson [this message]
2025-06-27 3:44 ` Vasanthakumar Thiagarajan
2025-06-26 23:15 ` Jeff Johnson
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=fca2def0-227b-4208-8104-abc40368f7fb@oss.qualcomm.com \
--to=jeff.johnson@oss.qualcomm.com \
--cc=ath12k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_rdevanat@quicinc.com \
--cc=quic_saleemud@quicinc.com \
--cc=vasanthakumar.thiagarajan@oss.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox