linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Francesco Dolcini <francesco@dolcini.it>
To: Jeff Chen <jeff.chen_1@nxp.com>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
	briannorris@chromium.org, kvalo@kernel.org, francesco@dolcini.it,
	tsung-hsien.hsieh@nxp.com, s.hauer@pengutronix.de
Subject: Re: [PATCH 2/2] wifi: mwifiex: Fix the wrong hardware setting for HT40.
Date: Mon, 20 Jan 2025 12:12:15 +0100	[thread overview]
Message-ID: <Z44vj59nWIiswq7s@gaggiata.pivistrello.it> (raw)
In-Reply-To: <20250120074011.720358-2-jeff.chen_1@nxp.com>

Hello Jeff,
thanks for the patch.

On Mon, Jan 20, 2025 at 03:40:11PM +0800, Jeff Chen wrote:
> Add the missing bandwidth configuration for HT40.

Can you expand this a little bit?

- Is this a regression?
- What is the impact of this missing configuration? It's not working at all?
  It's working in some unexpected way (please explain)?
- Should this backported to stable (probably given the answer before it should
  be obvious the answer to this question)?

Anything else worth mentioning?

> 
> Signed-off-by: Jeff Chen <jeff.chen_1@nxp.com>
> ---
>  drivers/net/wireless/marvell/mwifiex/11n.c | 18 ++++++++++--------
>  1 file changed, 10 insertions(+), 8 deletions(-)
> 
> diff --git a/drivers/net/wireless/marvell/mwifiex/11n.c b/drivers/net/wireless/marvell/mwifiex/11n.c
> index 66f0f5377ac1..4ae0b4aaa09a 100644
> --- a/drivers/net/wireless/marvell/mwifiex/11n.c
> +++ b/drivers/net/wireless/marvell/mwifiex/11n.c
> @@ -308,7 +308,7 @@ mwifiex_cmd_append_11n_tlv(struct mwifiex_private *priv,
>  	int ret_len = 0;
>  	struct ieee80211_supported_band *sband;
>  	struct ieee_types_header *hdr;
> -	u8 radio_type;
> +	u8 radio_type, secch_offset;
>  
>  	if (!buffer || !*buffer)
>  		return ret_len;
> @@ -401,13 +401,15 @@ mwifiex_cmd_append_11n_tlv(struct mwifiex_private *priv,
>  		chan_list->chan_scan_param[0].radio_type =
>  			mwifiex_band_to_radio_type((u8) bss_desc->bss_band);
>  
> -		if (sband->ht_cap.cap & IEEE80211_HT_CAP_SUP_WIDTH_20_40 &&
> -		    bss_desc->bcn_ht_oper->ht_param &
> -		    IEEE80211_HT_PARAM_CHAN_WIDTH_ANY)
> -			SET_SECONDARYCHAN(chan_list->chan_scan_param[0].
> -					  radio_type,
> -					  (bss_desc->bcn_ht_oper->ht_param &
> -					  IEEE80211_HT_PARAM_CHA_SEC_OFFSET));
> +		if (sband->ht_cap.cap & IEEE80211_HT_CAP_SUP_WIDTH_20_40) {
> +			if (bss_desc->bcn_ht_oper->ht_param & IEEE80211_HT_PARAM_CHAN_WIDTH_ANY) {
> +				chan_list->chan_scan_param[0].radio_type |= (CHAN_BW_40MHZ << 2);

setting `radio_type |= (CHAN_BW_40MHZ << 2)` seems the only real change on this
patch, correct? Anything else is cosmetic, correct?

would doing just this change be equivalent, right?

	SET_SECONDARYCHAN(chan_list->chan_scan_param[0].
			  radio_type | (CHAN_BW_40MHZ << 2),
			  (bss_desc->bcn_ht_oper->ht_param &
			  IEEE80211_HT_PARAM_CHA_SEC_OFFSET));


Francesco


  reply	other threads:[~2025-01-20 11:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-20  7:40 [PATCH] wifi: mwifiex: Resolve the failure in downloading calibration data Jeff Chen
2025-01-20  7:40 ` [PATCH 2/2] wifi: mwifiex: Fix the wrong hardware setting for HT40 Jeff Chen
2025-01-20 11:12   ` Francesco Dolcini [this message]
2025-01-21 17:17     ` [EXT] " Jeff Chen
2025-03-14  6:04     ` Jeff Chen
2025-01-20 12:30 ` [PATCH] wifi: mwifiex: Resolve the failure in downloading calibration data Kalle Valo
2025-01-21 17:22   ` [EXT] " Jeff Chen

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=Z44vj59nWIiswq7s@gaggiata.pivistrello.it \
    --to=francesco@dolcini.it \
    --cc=briannorris@chromium.org \
    --cc=jeff.chen_1@nxp.com \
    --cc=kvalo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=tsung-hsien.hsieh@nxp.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 NNTP newsgroup(s).