From: Manivannan Sadhasivam <mani@kernel.org>
To: Konrad Dybcio <konrad.dybcio@linaro.org>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
"Borislav Petkov (AMD)" <bp@alien8.de>,
Marijn Suijten <marijn.suijten@somainline.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: qcom: sm8550: Use the correct LLCC register scheme
Date: Wed, 17 May 2023 11:17:31 +0530 [thread overview]
Message-ID: <20230517054731.GI4868@thinkpad> (raw)
In-Reply-To: <20230517-topic-kailua-llcc-v1-2-d57bd860c43e@linaro.org>
On Wed, May 17, 2023 at 04:18:50AM +0200, Konrad Dybcio wrote:
> During the ABI-breaking (for good reasons) conversion of the LLCC
> register description, SM8550 was not taken into account, resulting
> in LLCC being broken on any kernel containing the patch referenced
> in the fixes tag.
>
> Fix it by describing the regions properly.
>
> Fixes: ee13b5008707 ("qcom: llcc/edac: Fix the base address used for accessing LLCC banks")
Same comment about the Fixes tag.
> Signed-off-by: Konrad Dybcio <konrad.dybcio@linaro.org>
I do not have access to the SM8550 documentation to confirm the base address but
I hope that it has been taken care of.
Acked-by: Manivannan Sadhasivam <mani@kernel.org>
- Mani
> ---
> arch/arm64/boot/dts/qcom/sm8550.dtsi | 11 +++++++++--
> 1 file changed, 9 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/qcom/sm8550.dtsi b/arch/arm64/boot/dts/qcom/sm8550.dtsi
> index 6e9bad8f6f33..70ae7e2e900a 100644
> --- a/arch/arm64/boot/dts/qcom/sm8550.dtsi
> +++ b/arch/arm64/boot/dts/qcom/sm8550.dtsi
> @@ -3762,9 +3762,16 @@ gem_noc: interconnect@24100000 {
>
> system-cache-controller@25000000 {
> compatible = "qcom,sm8550-llcc";
> - reg = <0 0x25000000 0 0x800000>,
> + reg = <0 0x25000000 0 0x200000>,
> + <0 0x25200000 0 0x200000>,
> + <0 0x25400000 0 0x200000>,
> + <0 0x25600000 0 0x200000>,
> <0 0x25800000 0 0x200000>;
> - reg-names = "llcc_base", "llcc_broadcast_base";
> + reg-names = "llcc0_base",
> + "llcc1_base",
> + "llcc2_base",
> + "llcc3_base",
> + "llcc_broadcast_base";
> interrupts = <GIC_SPI 266 IRQ_TYPE_LEVEL_HIGH>;
> };
>
>
> --
> 2.40.1
>
--
மணிவண்ணன் சதாசிவம்
next prev parent reply other threads:[~2023-05-17 5:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 2:18 [PATCH 0/2] Fix SM8550 LLCC Konrad Dybcio
2023-05-17 2:18 ` [PATCH 1/2] dt-bindings: cache: qcom,llcc: Fix SM8550 description Konrad Dybcio
2023-05-17 5:44 ` Manivannan Sadhasivam
2023-05-17 13:20 ` Konrad Dybcio
2023-05-17 7:52 ` Krzysztof Kozlowski
2023-05-17 8:46 ` Krzysztof Kozlowski
2023-05-17 2:18 ` [PATCH 2/2] arm64: dts: qcom: sm8550: Use the correct LLCC register scheme Konrad Dybcio
2023-05-17 5:47 ` Manivannan Sadhasivam [this message]
2023-05-25 4:53 ` (subset) [PATCH 0/2] Fix SM8550 LLCC 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=20230517054731.GI4868@thinkpad \
--to=mani@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=bp@alien8.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=robh+dt@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).