From: Wen Gong <quic_wgong@quicinc.com>
To: Kalle Valo <kvalo@kernel.org>, Aloka Dixit <quic_alokad@quicinc.com>
Cc: <ath12k@lists.infradead.org>, <linux-wireless@vger.kernel.org>,
"Pradeep Kumar Chitrapu" <quic_pradeepc@quicinc.com>
Subject: Re: [PATCH v4 03/11] wifi: ath12k: WMI support to process EHT capabilities
Date: Tue, 25 Jul 2023 18:51:18 +0800 [thread overview]
Message-ID: <dc0ae263-e5f6-b876-842a-7b598caf68fa@quicinc.com> (raw)
In-Reply-To: <87ttv9aqtn.fsf@kernel.org>
On 6/15/2023 7:49 PM, Kalle Valo wrote:
> Aloka Dixit <quic_alokad@quicinc.com> writes:
>
[...]
> [...]
>
>> +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?
Currently ath12k has single_pdev parameter, it impact the interface
number of wifi.
For single_pdev=ture, ab->num_radios is set to 1 and all capbility of
2.4 GHz/
5 GHz/6 GHz is saved into ab->pdevs[0] in
ath12k_wmi_ext_soc_hal_reg_caps_parse().
ath12k_mac_register() will call only one time into
__ath12k_mac_register(), and
ieee80211_register_hw() is called only one time, and only one wifi
interface in
the result of "iw dev/ifconfig", the interface support 2.4 GHz/5 GHz/6
GHz. Actually
there hare more than one PHY in firmware, firmware maintain the all PHY
data and
provide a single pdev/soc interface to ath12k, then ath12k do not need
to consider
the PHY info such as channel/BAND<->PHY mapping relationship, it is
convenient for
ath12k to support 2.4 GHz/5 GHz/6 GHz.
For single_pdev=false, ab->num_radios is more than 1, ab->pdevs[] has
muti valid
element, each element only support one BAND. Firmware do not provide a
single
pdev/soc interface, so ath12k need to maintain the PHY data such as
channel/BAND<->
PHY mapping relationship, and ath12k_mac_register() will call muti-time
into
__ath12k_mac_register(), and ieee80211_register_hw() is called
muti-time, and muti
wifi interface in the result of "iw dev/ifconfig", and each interface
only support
one BAND, for example, wlan0 only support 2.4 GHz, wlan1 only support 5
GHz, and
wlan2 only support 6 GHz.
For single_pdev=ture, ath12k also need to know some info about the PHYs
sush as
pdev_id/phy_id/supported_bands in this patch, so ab->fw_pdev is used to
store the
PHY data.
--
ath12k mailing list
ath12k@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/ath12k
next prev parent reply other threads:[~2023-07-25 10:51 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
2023-06-16 10:50 ` Wen Gong
2023-07-24 17:42 ` Aloka Dixit
2023-07-25 10:51 ` Wen Gong [this message]
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=dc0ae263-e5f6-b876-842a-7b598caf68fa@quicinc.com \
--to=quic_wgong@quicinc.com \
--cc=ath12k@lists.infradead.org \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_alokad@quicinc.com \
--cc=quic_pradeepc@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