From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Johan Hovold <johan+linaro@kernel.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
Avri Altman <avri.altman@wdc.com>, Andy Gross <agross@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Bart Van Assche <bvanassche@acm.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-scsi@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: qcom: sc8280xp: fix UFS DMA coherency
Date: Mon, 5 Dec 2022 17:31:48 +0530 [thread overview]
Message-ID: <20221205120148.GB20192@thinkpad> (raw)
In-Reply-To: <20221205100837.29212-3-johan+linaro@kernel.org>
On Mon, Dec 05, 2022 at 11:08:37AM +0100, Johan Hovold wrote:
> The SC8280XP UFS controllers are cache coherent and must be marked as
> such in the devicetree to avoid potential data corruption.
>
> Fixes: 152d1faf1e2f ("arm64: dts: qcom: add SC8280XP platform")
> Cc: stable@vger.kernel.org # 6.0
> Signed-off-by: Johan Hovold <johan+linaro@kernel.org>
Reviewed-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Thanks,
Mani
> ---
> arch/arm64/boot/dts/qcom/sc8280xp.dtsi | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/qcom/sc8280xp.dtsi b/arch/arm64/boot/dts/qcom/sc8280xp.dtsi
> index c4947c563099..23d1f51527aa 100644
> --- a/arch/arm64/boot/dts/qcom/sc8280xp.dtsi
> +++ b/arch/arm64/boot/dts/qcom/sc8280xp.dtsi
> @@ -1430,6 +1430,7 @@ ufs_mem_hc: ufs@1d84000 {
> required-opps = <&rpmhpd_opp_nom>;
>
> iommus = <&apps_smmu 0xe0 0x0>;
> + dma-coherent;
>
> clocks = <&gcc GCC_UFS_PHY_AXI_CLK>,
> <&gcc GCC_AGGRE_UFS_PHY_AXI_CLK>,
> @@ -1491,6 +1492,7 @@ ufs_card_hc: ufs@1da4000 {
> power-domains = <&gcc UFS_CARD_GDSC>;
>
> iommus = <&apps_smmu 0x4a0 0x0>;
> + dma-coherent;
>
> clocks = <&gcc GCC_UFS_CARD_AXI_CLK>,
> <&gcc GCC_AGGRE_UFS_CARD_AXI_CLK>,
> --
> 2.37.4
>
--
மணிவண்ணன் சதாசிவம்
next prev parent reply other threads:[~2022-12-05 12:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 10:08 [PATCH 0/2] arm64: dts: qcom: sc8280xp: fix UFS DMA coherency Johan Hovold
2022-12-05 10:08 ` [PATCH 1/2] dt-bindings: ufs: qcom: allow 'dma-coherent' property Johan Hovold
2022-12-05 11:59 ` Manivannan Sadhasivam
2022-12-05 12:07 ` Johan Hovold
2022-12-05 12:20 ` Manivannan Sadhasivam
2022-12-05 12:27 ` Johan Hovold
2022-12-05 13:00 ` Manivannan Sadhasivam
2022-12-05 13:12 ` Johan Hovold
2022-12-05 13:37 ` Manivannan Sadhasivam
2022-12-06 8:14 ` Krzysztof Kozlowski
2022-12-06 9:17 ` Manivannan Sadhasivam
2022-12-05 22:35 ` Rob Herring
2022-12-06 7:49 ` Johan Hovold
2022-12-05 22:35 ` Rob Herring
2022-12-05 23:07 ` Bjorn Andersson
2022-12-06 7:55 ` Johan Hovold
2022-12-05 10:08 ` [PATCH 2/2] arm64: dts: qcom: sc8280xp: fix UFS DMA coherency Johan Hovold
2022-12-05 11:37 ` Konrad Dybcio
2022-12-05 12:01 ` Manivannan Sadhasivam [this message]
2022-12-06 18:18 ` (subset) [PATCH 0/2] " Bjorn Andersson
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=20221205120148.GB20192@thinkpad \
--to=manivannan.sadhasivam@linaro.org \
--cc=agross@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=andersson@kernel.org \
--cc=avri.altman@wdc.com \
--cc=bvanassche@acm.org \
--cc=devicetree@vger.kernel.org \
--cc=johan+linaro@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=stable@vger.kernel.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).