From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>,
Andy Gross <andy.gross@linaro.org>,
David Brown <david.brown@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Stephen Boyd <swboyd@chromium.org>,
Doug Anderson <dianders@chromium.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/2] arm64: dts: qcom: sdm845: Fix DMA allocations for devices with IOMMU
Date: Fri, 18 Jan 2019 13:05:31 +0000 [thread overview]
Message-ID: <7e662602-73dd-2ac6-4e49-ce92f1d157d2@linaro.org> (raw)
In-Reply-To: <20190117042940.25487-1-bjorn.andersson@linaro.org>
On 17/01/2019 04:29, Bjorn Andersson wrote:
> These patches extends the size cells of the soc bus and define the dma-ranges,
> so that DMA allocations for devices with IOMMU attached will get valid IOVAs.
>
> Changes since v3:
> - Split patch in two
> - Rewrote commit message from scratch
>
> Bjorn Andersson (2):
> arm64: dts: qcom: sdm845: Increase address and size cells for soc
> arm64: dts: qcom: sdm845: Extend ranges and describe DMA space
>
> arch/arm64/boot/dts/qcom/sdm845.dtsi | 301 ++++++++++++++-------------
> 1 file changed, 151 insertions(+), 150 deletions(-)
>
Thanks for the fix, finally managed to get both fastrpc and ufs working
together with iommu!
Tested-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
prev parent reply other threads:[~2019-01-18 13:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 4:29 [PATCH v4 0/2] arm64: dts: qcom: sdm845: Fix DMA allocations for devices with IOMMU Bjorn Andersson
2019-01-17 4:29 ` [PATCH v4 1/2] arm64: dts: qcom: sdm845: Increase address and size cells for soc Bjorn Andersson
2019-01-17 17:47 ` Doug Anderson
2019-01-17 18:05 ` Stephen Boyd
2019-01-17 4:29 ` [PATCH v4 2/2] arm64: dts: qcom: sdm845: Extend ranges and describe DMA space Bjorn Andersson
2019-01-17 17:47 ` Doug Anderson
2019-01-17 18:22 ` Stephen Boyd
2019-01-18 13:05 ` Srinivas Kandagatla [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=7e662602-73dd-2ac6-4e49-ce92f1d157d2@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=swboyd@chromium.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).