From: Jeff Johnson <quic_jjohnson@quicinc.com>
To: Nicolas Escande <nico.escande@gmail.com>, Kalle Valo <kvalo@kernel.org>
Cc: <linux-wireless@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<ath11k@lists.infradead.org>
Subject: Re: [PATCH] wifi: ath11k: fix layout of scan_flags in struct scan_req_params
Date: Mon, 27 Nov 2023 10:38:24 -0800 [thread overview]
Message-ID: <bdcdbd06-e9bd-4a92-b27b-d94b2d8fb52d@quicinc.com> (raw)
In-Reply-To: <20231127180559.1696041-1-nico.escande@gmail.com>
On 11/27/2023 10:05 AM, Nicolas Escande wrote:
> The is a layout mismatch between the bitfield representing scan_flags in
> struct scan_req_params & the bits as defined in the WMI_SCAN_XXX macros.
> Lets fix it by making the struct match the #defines.
>
> I tried to correct it by making the struct match the #define and it
> worked for WMI_SCAN_FLAG_FORCE_ACTIVE_ON_DFS / scan_f_force_active_dfs_chn
> so I'm assuming this is the right thing to do.
>
> Tested-on: QCN9074 hw1.0 PCI WLAN.HK.2.7.0.1-01744-QCAHKSWPL_SILICONZ-1
>
> Signed-off-by: Nicolas Escande <nico.escande@gmail.com>
> ---
> drivers/net/wireless/ath/ath11k/wmi.h | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/net/wireless/ath/ath11k/wmi.h b/drivers/net/wireless/ath/ath11k/wmi.h
> index 100bb816b592..0b4e6c2f7860 100644
> --- a/drivers/net/wireless/ath/ath11k/wmi.h
> +++ b/drivers/net/wireless/ath/ath11k/wmi.h
> @@ -3348,17 +3348,17 @@ struct scan_req_params {
> scan_f_filter_prb_req:1,
> scan_f_bypass_dfs_chn:1,
> scan_f_continue_on_err:1,
> + scan_f_promisc_mode:1,
> + scan_f_force_active_dfs_chn:1,
> + scan_f_add_tpc_ie_in_probe:1,
> + scan_f_add_ds_ie_in_probe:1,
> + scan_f_add_spoofed_mac_in_probe:1,
> scan_f_offchan_mgmt_tx:1,
> scan_f_offchan_data_tx:1,
> - scan_f_promisc_mode:1,
> scan_f_capture_phy_err:1,
> scan_f_strict_passive_pch:1,
> scan_f_half_rate:1,
> scan_f_quarter_rate:1,
> - scan_f_force_active_dfs_chn:1,
> - scan_f_add_tpc_ie_in_probe:1,
> - scan_f_add_ds_ie_in_probe:1,
> - scan_f_add_spoofed_mac_in_probe:1,
> scan_f_add_rand_seq_in_probe:1,
> scan_f_en_ie_whitelist_in_probe:1,
> scan_f_forced:1,
You are convoluting two different data structures.
struct scan_req_params is used to represent a scan request within the
host driver. This does not use the WMI_SCAN_XXX macros.
struct wmi_start_scan_cmd is used to represent the scan request command
sent to firmware. This struct uses the WMI_SCAN_XXX macros to fill some
members of this struct in ath11k_wmi_copy_scan_event_cntrl_flags().
So your change has no effect on the driver operation and incorrectly
tries to foist the firmware definition upon the host internal
representation.
So NAK to this patch.
/jeff
next prev parent reply other threads:[~2023-11-27 18:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 18:05 Nicolas Escande
2023-11-27 18:38 ` Jeff Johnson [this message]
2023-11-27 22:54 ` Nicolas Escande
2023-11-28 0:57 ` Jeff Johnson
2023-11-30 8:24 ` Nicolas Escande
2024-01-15 13:09 ` Nicolas Escande
2024-01-18 11:14 ` 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=bdcdbd06-e9bd-4a92-b27b-d94b2d8fb52d@quicinc.com \
--to=quic_jjohnson@quicinc.com \
--cc=ath11k@lists.infradead.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nico.escande@gmail.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
all inboxes | Powered by JetHome®