From: Krzysztof Kozlowski <krzk@kernel.org>
To: Ivaylo Ivanov <ivo.ivanov.ivanov1@gmail.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Alim Akhtar <alim.akhtar@samsung.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] dt-bindings: timer: exynos4210-mct: add samsung,exynos2200-mct-peris compatible
Date: Wed, 19 Feb 2025 09:34:16 +0100 [thread overview]
Message-ID: <03ec9bef-715a-462b-b58b-03255cd80225@kernel.org> (raw)
In-Reply-To: <20250215123922.163630-1-ivo.ivanov.ivanov1@gmail.com>
On 15/02/2025 13:39, Ivaylo Ivanov wrote:
> Whilst having a new multicore timer that differs from the old designs in
> functionality and registers (marked as MCTv2 in vendor kernels),
> Exynos2200 also keeps an additional multicore timer connected over PERIS
> that reuses the same design as older exynos socs.
>
> Add a compatible for the legacy multicore timer of Exynos2200. Rather
> than differentiating it based on the block version, mark it as the
> one connected over PERIS.
>
> Signed-off-by: Ivaylo Ivanov <ivo.ivanov.ivanov1@gmail.com>
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-02-19 8:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-15 12:39 [PATCH v1] dt-bindings: timer: exynos4210-mct: add samsung,exynos2200-mct-peris compatible Ivaylo Ivanov
2025-02-19 8:34 ` Krzysztof Kozlowski [this message]
2025-02-19 11:46 ` Daniel Lezcano
2025-03-25 8:14 ` [tip: timers/clocksource] " tip-bot2 for Ivaylo Ivanov
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=03ec9bef-715a-462b-b58b-03255cd80225@kernel.org \
--to=krzk@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=conor+dt@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=ivo.ivanov.ivanov1@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=robh@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).