From: Manikanta Pubbisetty <quic_mpubbise@quicinc.com>
To: Kalle Valo <kvalo@kernel.org>
Cc: <ath11k@lists.infradead.org>, <linux-wireless@vger.kernel.org>,
<devicetree@vger.kernel.org>, <robh@kernel.org>,
<mka@chromium.org>
Subject: Re: [PATCH v4 00/12] add support for WCN6750
Date: Wed, 27 Apr 2022 11:28:38 +0530 [thread overview]
Message-ID: <c1d7930e-3796-fb65-2cb9-caed131b51e3@quicinc.com> (raw)
In-Reply-To: <874k2fgjhu.fsf@kernel.org>
On 4/27/2022 11:23 AM, Kalle Valo wrote:
> Manikanta Pubbisetty <quic_mpubbise@quicinc.com> writes:
>
>> WCN6750 is non-DBS 2x2 11AX chipset. Unlike QCA6390/WCN6855 which
>> are DBS (dual band simultaneous) solutions (2 LMACs), WCN6750 has a
>> single LMAC supporting 2G, 5G and 6G bands. It can be operated only
>> on one band at any given point.
>>
>> WCN6750 is a PCIe device. Unlike other supported ATH11K PCIe devices
>> which are directly attached to APSS (Application Processor SubSystem),
>> WCN6750 is not attached to APSS, it is attached to the WPSS
>> (Wireless Processor SubSystem) Q6 processor, the FW which runs on the
>> Q6 processor will enumerate the PCIe device. Since APSS is unaware of
>> such a device, it has to be registered as a platform device(AHB) to the
>> kernel for device probing. Like other AHB devices, remoteproc APIs are
>> used to boot up or shutdown of WCN6750.
>>
>> WCN6750 uses both AHB and PCIe ATH11K APIs for it's operation.
>> It uses AHB APIs for device probe and booting of the remote processor.
>> Once device is booted up, it uses ATH11K PCIe APIs for initialization
>> and register access. Hence, it is referred as hybrid bus device in
>> the rest of this series.
>>
>> Since the chip is enumerated by WPSS Q6, device information like
>> BAR and BAR size is not known to the APSS processor. A new QMI message
>> called device info QMI request will be sent to the target for fetching
>> these details.
>>
>> STA and AP modes are supported; Basic connectivity and ping are
>> verified in both the modes.
>>
>> An important point to note is that though WCN6750 is a PCIe device,
>> it cannot be attached to any other platform except on Qualcomm
>> Snapdragon SoCs due to the aforementioned reasons.
>>
>> Tested-on: WCN6750 hw1.0 AHB WLAN.MSL.1.0.1-00573-QCAMSLSWPLZ-1
>> Tested-on: WCN6855 hw2.0 PCI WLAN.HSP.1.1-01720.1-QCAHSPSWPL_V1_V2_SILICONZ_LITE-1
>> Tested-on: QCN9074 hw1.0 PCI WLAN.HK.2.5.0.1-01100-QCAHKSWPL_SILICONZ-1
>> Tested-on: IPQ8074 hw2.0 AHB WLAN.HK.2.4.0.1-00192-QCAHKSWPL_SILICONZ-1
>>
>> Manikanta Pubbisetty (12):
>> dt: bindings: net: add bindings of WCN6750 for ath11k
>> ath11k: Add HW params for WCN6750
>> ath11k: Add bus params for WCN6750
>> ath11k: Add register access logic for WCN6750
>> ath11k: Fetch device information via QMI for WCN6750
>> ath11k: Add QMI changes for WCN6750
>> ath11k: HAL changes to support WCN6750
>> ath11k: Datapath changes to support WCN6750
>> ath11k: Do not put HW in DBS mode for WCN6750
>> ath11k: WMI changes to support WCN6750
>> ath11k: Update WBM idle ring HP after FW mode on
>> ath11k: Add support for WCN6750 device
>
> Due to the bus_params problem I had to drop most of the patches, but I
> did keep few of them in the pending branch to reduce the patchset size:
>
> 495a15b1969a ath11k: Update WBM idle ring HP after FW mode on
> 8d121dacbe35 ath11k: WMI changes to support WCN6750
> e31091e06011 ath11k: Do not put HW in DBS mode for WCN6750
>
> Please submit v6 only after I have applied these, I'm waiting for some
> build testing first.
>
Sure Kalle, thanks!!
Manikanta
prev parent reply other threads:[~2022-04-27 5:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 9:40 [PATCH v4 00/12] add support for WCN6750 Manikanta Pubbisetty
2022-04-06 9:40 ` [PATCH v4 01/12] dt: bindings: net: add bindings of WCN6750 for ath11k Manikanta Pubbisetty
2022-04-06 15:08 ` Rob Herring
2022-04-07 5:21 ` Manikanta Pubbisetty
2022-04-27 5:13 ` Kalle Valo
2022-04-06 9:40 ` [PATCH v4 02/12] ath11k: Add HW params for WCN6750 Manikanta Pubbisetty
2022-04-27 5:21 ` Kalle Valo
2022-04-27 5:35 ` Manikanta Pubbisetty
2022-04-06 9:40 ` [PATCH v4 03/12] ath11k: Add bus " Manikanta Pubbisetty
2022-04-06 9:40 ` [PATCH v4 04/12] ath11k: Add register access logic " Manikanta Pubbisetty
2022-04-27 5:45 ` Kalle Valo
2022-04-27 5:53 ` Manikanta Pubbisetty
2022-04-29 8:57 ` Kalle Valo
2022-04-06 9:40 ` [PATCH v4 05/12] ath11k: Fetch device information via QMI " Manikanta Pubbisetty
2022-04-06 9:41 ` [PATCH v4 06/12] ath11k: Add QMI changes " Manikanta Pubbisetty
2022-04-06 9:41 ` [PATCH v4 07/12] ath11k: HAL changes to support WCN6750 Manikanta Pubbisetty
2022-04-06 9:41 ` [PATCH v4 08/12] ath11k: Datapath " Manikanta Pubbisetty
2022-04-06 9:41 ` [PATCH v4 09/12] ath11k: Do not put HW in DBS mode for WCN6750 Manikanta Pubbisetty
2022-04-27 7:26 ` Kalle Valo
2022-04-06 9:41 ` [PATCH v4 10/12] ath11k: WMI changes to support WCN6750 Manikanta Pubbisetty
2022-04-06 9:41 ` [PATCH v4 11/12] ath11k: Update WBM idle ring HP after FW mode on Manikanta Pubbisetty
2022-04-06 9:41 ` [PATCH v4 12/12] ath11k: Add support for WCN6750 device Manikanta Pubbisetty
2022-04-27 5:53 ` [PATCH v4 00/12] add support for WCN6750 Kalle Valo
2022-04-27 5:58 ` Manikanta Pubbisetty [this message]
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=c1d7930e-3796-fb65-2cb9-caed131b51e3@quicinc.com \
--to=quic_mpubbise@quicinc.com \
--cc=ath11k@lists.infradead.org \
--cc=devicetree@vger.kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mka@chromium.org \
--cc=robh@kernel.org \
/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).