All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Nicolas Escande" <nico.escande@gmail.com>
To: "Jeff Johnson" <quic_jjohnson@quicinc.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, 15 Jan 2024 14:09:28 +0100	[thread overview]
Message-ID: <CYFAYRP5MWTZ.Q272WWLLE7MW@gmail.com> (raw)
In-Reply-To: <CXC03GYAN4VN.2PQ88Q1S7IL6H@gmail.com>

On Thu Nov 30, 2023 at 9:24 AM CET, Nicolas Escande wrote:
> On Tue Nov 28, 2023 at 1:57 AM CET, Jeff Johnson wrote:
> > On 11/27/2023 2:54 PM, Nicolas Escande wrote:
> [...]
> > > So either we should not use WMI_SCAN_XXX with scan_req_params.scan_flags ever
> > > and only use the bitfield to set scan parameters or if we use WMI_SCAN_XXX with
> > > scan_req_params.scan_flags they need to match the corresponding bitfield.
> >
> > IMO the correct thing to do is to remove the unions from that struct and
> > only leave behind the bitfields and not use the WMI_SCAN_XXX masks
> > except when filling the firmware structure.
> >
> > But don't spin an update to your patches until Kalle has a chance to
> > give his opinion. I'm new to maintaining these drivers and Kalle may
> > have a different opinion on this.
> >
> > /jeff
>
> No problem, I'll wait for Kalle's input on this before doing anything.
> As soon as we decide which way is the right way, I'll work on this. I only care
> that this gets resolved.

Hi Kalle/Jeff,

Any new input on this so I can move forward on fixing this ?
Otherwise I think I'll end up going on with Jeff's proposal of only using the
bitfield for intra driver representation & then converting the bitfields to
their corresponding WMI_SCAN_XXX when transmiting the req to the hw with wmi.


  reply	other threads:[~2024-01-15 13:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-27 18:05 [PATCH] wifi: ath11k: fix layout of scan_flags in struct scan_req_params Nicolas Escande
2023-11-27 18:05 ` Nicolas Escande
2023-11-27 18:38 ` Jeff Johnson
2023-11-27 18:38   ` Jeff Johnson
2023-11-27 22:54   ` Nicolas Escande
2023-11-27 22:54     ` Nicolas Escande
2023-11-28  0:57     ` Jeff Johnson
2023-11-28  0:57       ` Jeff Johnson
2023-11-30  8:24       ` Nicolas Escande
2024-01-15 13:09         ` Nicolas Escande [this message]
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=CYFAYRP5MWTZ.Q272WWLLE7MW@gmail.com \
    --to=nico.escande@gmail.com \
    --cc=ath11k@lists.infradead.org \
    --cc=kvalo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=quic_jjohnson@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 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.