From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Roopni Devanathan <quic_rdevanat@quicinc.com>,
ath12k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org,
Sowmiya Sree Elavalagan <quic_ssreeela@quicinc.com>,
Ramya Gnanasekar <quic_rgnanase@quicinc.com>
Subject: Re: [PATCH v5 1/2] wifi: ath12k: Add Support to Parse TPC Event from Firmware
Date: Wed, 29 Jan 2025 17:31:15 -0800 [thread overview]
Message-ID: <904c2c6e-c21b-4718-b60e-c29c60d80aa2@oss.qualcomm.com> (raw)
In-Reply-To: <20250128111059.1690113-2-quic_rdevanat@quicinc.com>
On 1/28/2025 3:10 AM, Roopni Devanathan wrote:
...
> +struct wmi_max_reg_power_allowed_params {
this seems to be misnamed. per the wmi naming convention _params are structs
passed from firmware. you cannot pass a pointer to an array from firmware to
host, you can only pass the array contents. hence seems this is a host-only
struct and should be named _arg
> + struct wmi_max_reg_power_fixed_params tpc_reg_pwr;
> + s16 *reg_pwr_array;
> +};
> +
> +struct wmi_tpc_rates_array_fixed_params {
> + __le32 rate_array_type;
> + __le32 rate_array_len;
> +} __packed;
> +
> +struct wmi_tpc_rates_array_params {
again seems this should be _arg
> + struct wmi_tpc_rates_array_fixed_params tpc_rates_array;
> + s16 *rate_array;
> +};
> +
> +struct wmi_tpc_ctl_pwr_fixed_params {
> + __le32 ctl_array_type;
> + __le32 ctl_array_len;
> + __le32 end_of_ctl_pwr;
> + __le32 ctl_pwr_count;
> + __le32 d1;
> + __le32 d2;
> + __le32 d3;
> + __le32 d4;
> +} __packed;
> +
> +struct wmi_tpc_ctl_pwr_table_params {
again seems this should be _arg
> + struct wmi_tpc_ctl_pwr_fixed_params tpc_ctl_pwr;
> + s8 *ctl_pwr_table;
> +};
> +
> +struct wmi_tpc_stats_info {
same here
> + u32 pdev_id;
> + u32 event_count;
> + u32 end_of_event;
> + u32 tlvs_rcvd;
> + struct wmi_max_reg_power_allowed_params max_reg_allowed_power;
> + struct wmi_tpc_rates_array_params rates_array1;
> + struct wmi_tpc_rates_array_params rates_array2;
> + struct wmi_tpc_config_params tpc_config;
> + struct wmi_tpc_ctl_pwr_table_params ctl_array;
> +};
reminder from the top of the file:
/* Naming conventions for structures:
*
* _cmd means that this is a firmware command sent from host to firmware.
*
* _event means that this is a firmware event sent from firmware to host
*
* _params is a structure which is embedded either into _cmd or _event (or
* both), it is not sent individually.
*
* _arg is used inside the host, the firmware does not see that at all.
*/
next prev parent reply other threads:[~2025-01-30 1:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-28 11:10 [PATCH v5 0/2] wifi: ath12k: Support Transmit Power Control Stats Roopni Devanathan
2025-01-28 11:10 ` [PATCH v5 1/2] wifi: ath12k: Add Support to Parse TPC Event from Firmware Roopni Devanathan
2025-01-28 14:49 ` Aditya Kumar Singh
2025-01-30 1:31 ` Jeff Johnson [this message]
2025-01-30 6:15 ` Roopni Devanathan
2025-01-28 11:10 ` [PATCH v5 2/2] wifi: ath12k: Add Support to Calculate and Display TPC Values Roopni Devanathan
2025-01-28 14:53 ` Aditya Kumar Singh
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=904c2c6e-c21b-4718-b60e-c29c60d80aa2@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_rgnanase@quicinc.com \
--cc=quic_ssreeela@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