From: Kalle Valo <kvalo@codeaurora.org> To: Bjorn Andersson <bjorn.andersson@linaro.org> Cc: Rakesh Pillai <pillair@codeaurora.org>, ath10k@lists.infradead.org, linux-wireless@vger.kernel.org Subject: Re: [PATCH v2] ath10k: Set DMA address mask to 35 bit for WCN3990 Date: Thu, 31 Jan 2019 15:51:30 +0200 [thread overview] Message-ID: <871s4tj5p9.fsf@kamboji.qca.qualcomm.com> (raw) In-Reply-To: <20190130185721.GT31919@minitux> (Bjorn Andersson's message of "Wed, 30 Jan 2019 10:57:22 -0800") Bjorn Andersson <bjorn.andersson@linaro.org> writes: > On Mon 03 Sep 09:37 PDT 2018, Rakesh Pillai wrote: > >> WCN3990 is a 37-bit target but can address memory range >> only upto 35 bits. The 36th bit is used to control the >> smmu/iommu translation and the 37th bit is used by the >> internal bus masters to access the wifi subsystem internal >> SRAM. With the DMA mask set to 37i-bit, the host driver >> can get 37-bit dma address, which leads to incorrect >> address access in the target. >> >> Hence the host driver can used addresses upto 35-bit >> for WCN3990. Fix the dma mask for wcn3990 to 35-bit, >> instead of 37-bit. >> >> Tested HW: WCN3990 >> Tested FW: WLAN.HL.2.0-01188-QCAHLSWMTPLZ-1 >> >> Signed-off-by: Rakesh Pillai <pillair@codeaurora.org> > > This solves the problem I'm seeing on my SDM845, where I see a > translation fault on a 32-bit address from the IOMMU, which we > previously mapped the 36 bit version of (my dma-ranges is set to 36 > bits). > > So: > > Tested-by: Bjorn Andersson <bjorn.andersson@linaro.org> Thanks for the reminder. This got piled up in my deferred queue in patchwork and I hadn't looked at it yet. I'll queue this for -next. > However, some of the changes in this patch and the fact that I get a > translation error on the lower 32 bits of the mapped iova, makes me > suspect that while the hardware is capable of 37 bits, the driver only > dealt with the lower 32. And if that's the case I would like to see > that mentioned in the commit message. Rakesh mentioned that it's actually 35 bits. Should something changed in the commit log still? I can do that if needed. -- Kalle Valo
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@codeaurora.org> To: Bjorn Andersson <bjorn.andersson@linaro.org> Cc: linux-wireless@vger.kernel.org, Rakesh Pillai <pillair@codeaurora.org>, ath10k@lists.infradead.org Subject: Re: [PATCH v2] ath10k: Set DMA address mask to 35 bit for WCN3990 Date: Thu, 31 Jan 2019 15:51:30 +0200 [thread overview] Message-ID: <871s4tj5p9.fsf@kamboji.qca.qualcomm.com> (raw) In-Reply-To: <20190130185721.GT31919@minitux> (Bjorn Andersson's message of "Wed, 30 Jan 2019 10:57:22 -0800") Bjorn Andersson <bjorn.andersson@linaro.org> writes: > On Mon 03 Sep 09:37 PDT 2018, Rakesh Pillai wrote: > >> WCN3990 is a 37-bit target but can address memory range >> only upto 35 bits. The 36th bit is used to control the >> smmu/iommu translation and the 37th bit is used by the >> internal bus masters to access the wifi subsystem internal >> SRAM. With the DMA mask set to 37i-bit, the host driver >> can get 37-bit dma address, which leads to incorrect >> address access in the target. >> >> Hence the host driver can used addresses upto 35-bit >> for WCN3990. Fix the dma mask for wcn3990 to 35-bit, >> instead of 37-bit. >> >> Tested HW: WCN3990 >> Tested FW: WLAN.HL.2.0-01188-QCAHLSWMTPLZ-1 >> >> Signed-off-by: Rakesh Pillai <pillair@codeaurora.org> > > This solves the problem I'm seeing on my SDM845, where I see a > translation fault on a 32-bit address from the IOMMU, which we > previously mapped the 36 bit version of (my dma-ranges is set to 36 > bits). > > So: > > Tested-by: Bjorn Andersson <bjorn.andersson@linaro.org> Thanks for the reminder. This got piled up in my deferred queue in patchwork and I hadn't looked at it yet. I'll queue this for -next. > However, some of the changes in this patch and the fact that I get a > translation error on the lower 32 bits of the mapped iova, makes me > suspect that while the hardware is capable of 37 bits, the driver only > dealt with the lower 32. And if that's the case I would like to see > that mentioned in the commit message. Rakesh mentioned that it's actually 35 bits. Should something changed in the commit log still? I can do that if needed. -- Kalle Valo _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2019-01-31 13:51 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-09-03 16:37 [PATCH v2] ath10k: Set DMA address mask to 35 bit for WCN3990 Rakesh Pillai 2018-09-03 16:37 ` Rakesh Pillai 2019-01-30 18:57 ` Bjorn Andersson 2019-01-30 18:57 ` Bjorn Andersson 2019-01-31 7:36 ` Rakesh Pillai 2019-01-31 7:36 ` Rakesh Pillai 2019-01-31 13:51 ` Kalle Valo [this message] 2019-01-31 13:51 ` Kalle Valo 2019-01-31 15:35 ` Bjorn Andersson 2019-01-31 15:35 ` Bjorn Andersson 2019-02-04 15:49 ` Kalle Valo 2019-02-04 15:49 ` Kalle Valo
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=871s4tj5p9.fsf@kamboji.qca.qualcomm.com \ --to=kvalo@codeaurora.org \ --cc=ath10k@lists.infradead.org \ --cc=bjorn.andersson@linaro.org \ --cc=linux-wireless@vger.kernel.org \ --cc=pillair@codeaurora.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.