[PATCH v3 3/3] arm64: dts: Enabled MHI device over PCIe
Kalle Valo
kvalo at codeaurora.org
Fri Oct 9 07:27:41 EDT 2020
+ ath11k list
Manivannan Sadhasivam <manivannan.sadhasivam at linaro.org> writes:
> On Thu, Oct 08, 2020 at 11:03:42PM +0530, gokulsri at codeaurora.org wrote:
>> On 2020-10-08 18:41, Manivannan Sadhasivam wrote:
>> > Hi,
>> >
>> > On Thu, Oct 08, 2020 at 06:02:24PM +0530, Gokul Sriram Palanisamy wrote:
>> > > Enabled MHI device support over PCIe and added memory
>> > > reservation required for MHI enabled QCN9000 PCIe card.
>> > >
>> > > Signed-off-by: Gokul Sriram Palanisamy <gokulsri at codeaurora.org>
>> > > ---
>> > > arch/arm64/boot/dts/qcom/ipq8074-hk10.dtsi | 47
>> > > ++++++++++++++++++++++++++++++
>> > > 1 file changed, 47 insertions(+)
>> > >
>> > > diff --git a/arch/arm64/boot/dts/qcom/ipq8074-hk10.dtsi
>> > > b/arch/arm64/boot/dts/qcom/ipq8074-hk10.dtsi
>> > > index 0827055..e5c1ec0 100644
>> > > --- a/arch/arm64/boot/dts/qcom/ipq8074-hk10.dtsi
>> > > +++ b/arch/arm64/boot/dts/qcom/ipq8074-hk10.dtsi
>
> [...]
>
>> > > + pcie0_rp: pcie0_rp {
>> > > + reg = <0 0 0 0 0>;
>> > > +
>> > > + status = "ok";
>> > > + mhi_0: qcom,mhi at 0 {
>> >
>> > MHI doesn't support devicetree as of now so how is this supposed to
>> > work?
>> > Have you tested this series with mainline?
>> >
>> > Thanks,
>> > Mani
>> >
>>
>> Hi Mani,
>> This node entries will be consumed by ath11k driver and is not supposed to
>> be consumed by mhi driver.
>> And yes, it is tested on Mainline.
Upstream ath11k does not yet support QCN9074 so I don't see how this is
tested with mainline ath11k. You must be using some out-of-tree
_unofficial_ ath11k patches.
> Can you please point me to the relevant binding or the code which consumes this
> change?
>
> Also please explain what it does! For enabling MHI support over PCIe you don't
> need this node at all. You just need to define the PCIe device ID in the ath11k
> driver and that's it.
>
> Adding Kalle to this thread...
So currently QCN9074 firmware needs 55 MB of contiguous host memory and
I suspect one reason for these DT entries is an ugly hack to provide
that memory range to the firmware.
We are currently preparing QCN9074 patches for ath11k and finding a
solution how to implement these properly in ath11k. Hopefully there's no
need for hacks like this, we know more once we get the ath11k QCN9074
patches ready. Please drop this patch.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
More information about the ath11k
mailing list