[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-wireless
Subject:    Re: [PATCH v3 00/12] add support for WCN6750
From:       Kalle Valo <kvalo () kernel ! org>
Date:       2022-03-30 7:59:04
Message-ID: 87tubfx453.fsf () kernel ! org
[Download RAW message or body]

Manikanta Pubbisetty <quic_mpubbise@quicinc.com> writes:

> On 3/28/2022 11:39 AM, Manikanta Pubbisetty wrote:
> > 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
> > ---
> > Note:
> > *	Remoteproc driver changes for WCN6750 which takes care of
> > 	downloading the FW and booting of Q6 processor are under
> > 	upstream review.
> > 	Link: https://patchwork.kernel.org/project/linux-remoteproc/cover/1643712724-12436-1-git-send-email-quic_mpubbise@quicinc.com/
> > 
> 
> Hi Kalle,
> 
> It looks like the remoteproc changes have landed in linux-next tree.
> Shall I remove this dependency and resend the series?

Please wait, I want to look at the patchset first and provide comments.

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

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


[prev in list] [next in list] [prev in thread] [next in thread]