linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Aloka Dixit <quic_alokad@quicinc.com>
Cc: <ath12k@lists.infradead.org>, <linux-wireless@vger.kernel.org>,
	Pradeep Kumar Chitrapu <quic_pradeepc@quicinc.com>,
	Wen Gong <quic_wgong@quicinc.com>
Subject: Re: [PATCH v4 03/11] wifi: ath12k: WMI support to process EHT capabilities
Date: Thu, 15 Jun 2023 14:49:08 +0300	[thread overview]
Message-ID: <87ttv9aqtn.fsf@kernel.org> (raw)
In-Reply-To: <20230602235820.23912-4-quic_alokad@quicinc.com> (Aloka Dixit's message of "Fri, 2 Jun 2023 16:58:12 -0700")

Aloka Dixit <quic_alokad@quicinc.com> writes:

> Add WMI support to process the EHT capabilities passed by
> the firmware. Add required EHT specific definitions in
> structures ath12k_band_cap and ath12k_wmi_svc_rdy_ext_parse.
>
> For single_pdev chip such as WCN7850, only one pdev is created
> and only one hardware is registered to mac80211. This one pdev
> manages both 2.4 GHz radio and 5 GHz/6 GHz radio.
>
> Tested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.0.1-00029-QCAHKSWPL_SILICONZ-1
> Tested-on: WCN7850 hw2.0 PCI WLAN.HMT.1.0-03427-QCAHMTSWPL_V1.0_V2.0_SILICONZ-1.15378.4
> Signed-off-by: Aloka Dixit <quic_alokad@quicinc.com>
> Co-developed-by: Pradeep Kumar Chitrapu <quic_pradeepc@quicinc.com>
> Signed-off-by: Pradeep Kumar Chitrapu <quic_pradeepc@quicinc.com>
> Co-developed-by: Wen Gong <quic_wgong@quicinc.com>
> Signed-off-by: Wen Gong <quic_wgong@quicinc.com>

[...]

> +struct ath12k_fw_pdev {
> +	u32 pdev_id;
> +	u32 phy_id;
> +	u32 supported_bands;
> +};

So we have now two very similar structures, ath12k_pdev and
ath12k_fw_pdev. It would be good to document above the structs their
purpose. Any ideas what I could add?

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

  reply	other threads:[~2023-06-15 11:56 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-02 23:58 [PATCH v4 00/11] wifi: ath12k: (v4) EHT support Aloka Dixit
2023-06-02 23:58 ` [PATCH v4 01/11] wifi: ath12k: rename HE capabilities setup/copy functions Aloka Dixit
2023-06-02 23:58 ` [PATCH v4 02/11] wifi: ath12k: move HE capabilities processing to a new function Aloka Dixit
2023-06-02 23:58 ` [PATCH v4 03/11] wifi: ath12k: WMI support to process EHT capabilities Aloka Dixit
2023-06-15 11:49   ` Kalle Valo [this message]
2023-06-16 10:50     ` Wen Gong
2023-07-24 17:42       ` Aloka Dixit
2023-07-25 10:51     ` Wen Gong
2023-07-25 19:44       ` Aloka Dixit
2023-06-02 23:58 ` [PATCH v4 04/11] wifi: ath12k: propagate EHT capabilities to userspace Aloka Dixit
2023-06-15 11:51   ` Kalle Valo
2023-07-24 18:11     ` Aloka Dixit
2023-06-02 23:58 ` [PATCH v4 05/11] wifi: ath12k: add EHT PHY modes Aloka Dixit
2023-06-02 23:58 ` [PATCH v4 06/11] wifi: ath12k: prepare EHT peer assoc parameters Aloka Dixit
2023-07-24 10:16   ` Wen Gong
2023-07-24 18:24     ` Aloka Dixit
2023-07-25 10:07       ` Wen Gong
2023-07-25 22:44         ` Aloka Dixit
2023-06-02 23:58 ` [PATCH v4 07/11] wifi: ath12k: add WMI support for EHT peer Aloka Dixit
2023-06-02 23:58 ` [PATCH v4 08/11] wifi: ath12k: peer assoc for 320 MHz Aloka Dixit
2023-06-02 23:58 ` [PATCH v4 09/11] wifi: ath12k: add MLO header in peer association Aloka Dixit
2023-06-02 23:58 ` [PATCH v4 10/11] wifi: ath12k: parse WMI service ready ext2 event Aloka Dixit
2023-06-02 23:58 ` [PATCH v4 11/11] wifi: ath12k: configure puncturing bitmap Aloka Dixit
2023-06-15 11:47 ` [PATCH v4 00/11] wifi: ath12k: (v4) EHT support Kalle Valo
2023-07-24 17:43   ` Aloka Dixit

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=87ttv9aqtn.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=ath12k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=quic_alokad@quicinc.com \
    --cc=quic_pradeepc@quicinc.com \
    --cc=quic_wgong@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;
as well as URLs for NNTP newsgroup(s).