+ mani Govind Singh <govinds@xxxxxxxxxxxxxx> writes: > MHI is a communication protocol to communicate with external > Qualcomm modems and Wi-Fi chipsets over high speed peripheral buses. Even > though MHI doesn’t dictate underlying physical layer, protocol and mhi stack > is structured for PCIe based devices. > > Register directly with mhi core layer as a mhi device driver for > firmware download. > > Tested QCA6390 on X86 platform. > Tested firmware WLAN.HST.1.0.1.c1-00440-QCAHSTSWPLZ_V2_TO_X86-1. > > Signed-off-by: Govind Singh <govinds@xxxxxxxxxxxxxx> [...] > --- a/drivers/net/wireless/ath/ath11k/Kconfig > +++ b/drivers/net/wireless/ath/ath11k/Kconfig > @@ -2,7 +2,6 @@ > config ATH11K > tristate "Qualcomm Technologies 802.11ax chipset support" > depends on MAC80211 && HAS_DMA > - depends on REMOTEPROC > depends on CRYPTO_MICHAEL_MIC > depends on ARCH_QCOM || COMPILE_TEST > select ATH_COMMON > @@ -15,13 +14,13 @@ config ATH11K > > config ATH11K_AHB > tristate "Qualcomm Technologies 802.11ax chipset AHB support" > - depends on ATH11K > + depends on ATH11K && REMOTEPROC > ---help--- > This module adds support for AHB bus > > config ATH11K_PCI > tristate "Qualcomm Technologies 802.11ax chipset PCI support" > - depends on ATH11K && PCI > + depends on ATH11K && PCI && MHI_BUS > ---help--- > This module adds support for PCIE bus Currently ATH11K_PCI is not visible if MHI_BUS is disabled, which I'm worried will confuse the users. I wonder if we should use 'select MHI_BUS' instead? That way ATH11K_PCI would be visible even if MHI_BUS is disabled. And what about QRTR_MHI? Mani, any suggestions? -- https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
