From: "Alim Akhtar" <alim.akhtar@samsung.com>
To: "'Krzysztof Kozlowski'" <krzysztof.kozlowski@canonical.com>,
"'Daniel Lezcano'" <daniel.lezcano@linaro.org>,
"'Thomas Gleixner'" <tglx@linutronix.de>,
"'Rob Herring'" <robh+dt@kernel.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-samsung-soc@vger.kernel.org>
Subject: RE: [PATCH v2 4/4] arm64: dts: tesla: add a specific compatible to MCT on FSD
Date: Sun, 6 Mar 2022 22:50:45 +0530 [thread overview]
Message-ID: <000501d8317e$8563cc20$902b6460$@samsung.com> (raw)
In-Reply-To: <20220304122424.307885-5-krzysztof.kozlowski@canonical.com>
>-----Original Message-----
>From: Krzysztof Kozlowski [mailto:krzysztof.kozlowski@canonical.com]
>Sent: Friday, March 4, 2022 5:54 PM
>To: Daniel Lezcano <daniel.lezcano@linaro.org>; Thomas Gleixner
><tglx@linutronix.de>; Rob Herring <robh+dt@kernel.org>; Krzysztof
>Kozlowski <krzysztof.kozlowski@canonical.com>; Alim Akhtar
><alim.akhtar@samsung.com>; linux-kernel@vger.kernel.org;
>devicetree@vger.kernel.org; linux-arm-kernel@lists.infradead.org; linux-
>samsung-soc@vger.kernel.org
>Subject: [PATCH v2 4/4] arm64: dts: tesla: add a specific compatible to MCT
on
>FSD
>
>One compatible is used for the Multi-Core Timer on Tesla FSD SoC, which is
>correct but not specific enough. The MCT blocks have different number of
>interrupts, so add a second specific compatible to Tesla FSD.
>
>Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
>---
Reviewed-by: Alim Akhtar <alim.akhtar@samsung.com>
> arch/arm64/boot/dts/tesla/fsd.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>diff --git a/arch/arm64/boot/dts/tesla/fsd.dtsi
>b/arch/arm64/boot/dts/tesla/fsd.dtsi
>index 9a652abcbcac..10c217a57a7d 100644
>--- a/arch/arm64/boot/dts/tesla/fsd.dtsi
>+++ b/arch/arm64/boot/dts/tesla/fsd.dtsi
>@@ -727,7 +727,7 @@ spi_2: spi@14160000 {
> };
>
> timer@10040000 {
>- compatible = "samsung,exynos4210-mct";
>+ compatible = "tesla,fsd-mct", "samsung,exynos4210-
>mct";
> reg = <0x0 0x10040000 0x0 0x800>;
> interrupts = <GIC_SPI 455 IRQ_TYPE_LEVEL_HIGH>,
> <GIC_SPI 456 IRQ_TYPE_LEVEL_HIGH>,
>--
>2.32.0
next prev parent reply other threads:[~2022-03-06 17:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 12:24 [PATCH v2 0/4] dt-bindings: timer: exynos4210-mct: describe known hardware and its interrupts Krzysztof Kozlowski
2022-03-04 12:24 ` [PATCH v2 1/4] " Krzysztof Kozlowski
2022-03-06 17:20 ` Alim Akhtar
2022-03-08 0:59 ` Rob Herring
2022-03-04 12:24 ` [PATCH v2 2/4] ARM: dts: exynos: add a specific compatible to MCT Krzysztof Kozlowski
2022-04-04 17:01 ` (subset) " Krzysztof Kozlowski
2022-03-04 12:24 ` [PATCH v2 3/4] arm64: " Krzysztof Kozlowski
2022-04-04 17:01 ` (subset) " Krzysztof Kozlowski
2022-03-04 12:24 ` [PATCH v2 4/4] arm64: dts: tesla: add a specific compatible to MCT on FSD Krzysztof Kozlowski
2022-03-06 17:20 ` Alim Akhtar [this message]
2022-04-04 17:01 ` (subset) " Krzysztof Kozlowski
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='000501d8317e$8563cc20$902b6460$@samsung.com' \
--to=alim.akhtar@samsung.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
/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).