From: Sai Prakash Ranjan <quic_saipraka@quicinc.com>
To: Abel Vesa <abel.vesa@linaro.org>, Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Neil Armstrong <neil.armstrong@linaro.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH v6 02/10] arm64: dts: qcom: Add base SM8550 dtsi
Date: Tue, 6 Dec 2022 21:57:17 +0530 [thread overview]
Message-ID: <03048338-449d-6d4b-dfa9-d4eccba5cabb@quicinc.com> (raw)
In-Reply-To: <20221206131252.977369-3-abel.vesa@linaro.org>
Hi Abel,
On 12/6/2022 6:42 PM, Abel Vesa wrote:
> Add base dtsi for SM8550 SoC and includes base description of
> CPUs, GCC, RPMHCC, UART, interrupt controller, TLMM, reserved
> memory, RPMh PD, TCSRCC, ITS, IPCC, AOSS QMP, LLCC, cpufreq,
> interconnect, thermal sensor, cpu cooling maps and SMMU nodes
> which helps boot to shell with console on boards with this SoC.
>
> Co-developed-by: Neil Armstrong <neil.armstrong@linaro.org>
> Signed-off-by: Neil Armstrong <neil.armstrong@linaro.org>
> Signed-off-by: Abel Vesa <abel.vesa@linaro.org>
> Reviewed-by: Konrad Dybcio <konrad.dybcio@linaro.org>
> ---
>
> Changes since v5:
> * changed the include of qcom,sm8550-tcsrcc.h to qcom,sm8550-tcsr.h
>
<snip>...
> + pmu {
> + compatible = "arm,armv8-pmuv3";
> + interrupts = <GIC_PPI 7 IRQ_TYPE_LEVEL_HIGH>;
This should be IRQ_TYPE_LEVEL_LOW
> +
> + intc: interrupt-controller@17100000 {
> + compatible = "arm,gic-v3";
> + reg = <0 0x17100000 0 0x10000>, /* GICD */
> + <0 0x17180000 0 0x200000>; /* GICR * 8 */
> + ranges;
> + #interrupt-cells = <3>;
> + interrupt-controller;
> + #redistributor-regions = <1>;
> + redistributor-stride = <0 0x40000>;
> + interrupts = <GIC_PPI 9 IRQ_TYPE_LEVEL_HIGH>;
And here as well, IRQ_TYPE_LEVEL_LOW
With these 2 corrections,
Reviewed-by: Sai Prakash Ranjan <quic_saipraka@quicinc.com>
Thanks,
Sai
next prev parent reply other threads:[~2022-12-06 16:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 13:12 [PATCH v6 00/10] arm64: dts: Add base device tree files for SM8550 Abel Vesa
2022-12-06 13:12 ` [PATCH v6 01/10] dt-bindings: arm: qcom: Document SM8550 SoC and boards Abel Vesa
2022-12-06 13:12 ` [PATCH v6 02/10] arm64: dts: qcom: Add base SM8550 dtsi Abel Vesa
2022-12-06 16:27 ` Sai Prakash Ranjan [this message]
2022-12-06 13:12 ` [PATCH v6 03/10] arm64: dts: qcom: Add pm8010 pmic dtsi Abel Vesa
2022-12-06 13:12 ` [PATCH v6 04/10] arm64: dts: qcom: Add PM8550 " Abel Vesa
2022-12-06 13:12 ` [PATCH v6 05/10] arm64: dts: qcom: Add PM8550b " Abel Vesa
2022-12-06 13:12 ` [PATCH v6 06/10] arm64: dts: qcom: Add PM8550ve " Abel Vesa
2022-12-06 13:12 ` [PATCH v6 07/10] arm64: dts: qcom: Add PM8550vs " Abel Vesa
2022-12-06 13:12 ` [PATCH v6 08/10] arm64: dts: qcom: Add PMK8550 " Abel Vesa
2022-12-06 13:12 ` [PATCH v6 09/10] arm64: dts: qcom: Add PMR735d " Abel Vesa
2022-12-06 13:12 ` [PATCH v6 10/10] arm64: dts: qcom: Add base SM8550 MTP dts Abel Vesa
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=03048338-449d-6d4b-dfa9-d4eccba5cabb@quicinc.com \
--to=quic_saipraka@quicinc.com \
--cc=abel.vesa@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.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=neil.armstrong@linaro.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