From: Konrad Dybcio <konrad.dybcio@somainline.org>
To: Martin Botka <martin.botka@somainline.org>, martin.botka1@gmail.com
Cc: ~postmarketos/upstreaming@lists.sr.ht,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@somainline.org>,
Marijn Suijten <marijn.suijten@somainline.org>,
Jami Kettunen <jamipkettunen@somainline.org>,
Paul Bouchara <paul.bouchara@somainline.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] arm64: dts: qcom: sm6125: Use qcom,arm-v2 for MMU
Date: Sat, 1 Oct 2022 22:17:45 +0200 [thread overview]
Message-ID: <9498f220-3bdb-d21a-6b36-4714fb0baf30@somainline.org> (raw)
In-Reply-To: <20221001185750.495874-1-martin.botka@somainline.org>
On 1.10.2022 20:57, Martin Botka wrote:
> Signed-off-by: Martin Botka <martin.botka@somainline.org>
Add a commit message explaining that it was broken from the start and
this is required for it to function properly.
Konrad
> ---
> arch/arm64/boot/dts/qcom/sm6125.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm64/boot/dts/qcom/sm6125.dtsi b/arch/arm64/boot/dts/qcom/sm6125.dtsi
> index 7e135041bd42..b27cf52c6fba 100644
> --- a/arch/arm64/boot/dts/qcom/sm6125.dtsi
> +++ b/arch/arm64/boot/dts/qcom/sm6125.dtsi
> @@ -1482,7 +1482,7 @@ spmi_bus: spmi@1c40000 {
> };
>
> apps_smmu: iommu@c600000 {
> - compatible = "qcom,sm6125-smmu-500", "arm,mmu-500";
> + compatible = "qcom,sm6125-smmu-500", "qcom,smmu-v2";
> reg = <0xc600000 0x80000>;
> #iommu-cells = <2>;
> #global-interrupts = <1>;
next prev parent reply other threads:[~2022-10-01 20:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-01 18:57 [PATCH 1/1] arm64: dts: qcom: sm6125: Use qcom,arm-v2 for MMU Martin Botka
2022-10-01 20:17 ` Konrad Dybcio [this message]
2022-10-02 13:38 ` Slade Watkins
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=9498f220-3bdb-d21a-6b36-4714fb0baf30@somainline.org \
--to=konrad.dybcio@somainline.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=angelogioacchino.delregno@somainline.org \
--cc=devicetree@vger.kernel.org \
--cc=jamipkettunen@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=martin.botka1@gmail.com \
--cc=martin.botka@somainline.org \
--cc=paul.bouchara@somainline.org \
--cc=robh+dt@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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).