From: Vincent Whitchurch <vincent.whitchurch@axis.com>
To: <krzysztof.kozlowski@canonical.com>, <tglx@linutronix.de>,
<daniel.lezcano@linaro.org>
Cc: <kernel@axis.com>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-samsung-soc@vger.kernel.org>, <devicetree@vger.kernel.org>,
<alim.akhtar@samsung.com>, <robh+dt@kernel.org>,
Vincent Whitchurch <vincent.whitchurch@axis.com>
Subject: [PATCH v2 2/4] dt-bindings: timer: exynos4210-mct: Support using only local timer
Date: Tue, 8 Mar 2022 15:24:08 +0100 [thread overview]
Message-ID: <20220308142410.3193729-3-vincent.whitchurch@axis.com> (raw)
In-Reply-To: <20220308142410.3193729-1-vincent.whitchurch@axis.com>
The ARTPEC-8 SoC has a quad-core Cortex-A53 and a single-core Cortex-A5
which share one MCT with one global and eight local timers. The
Cortex-A53 and Cortex-A5 do not have cache-coherency between them, and
therefore run two separate kernels.
The Cortex-A53 boots first and starts the global FRC and also registers
a clock events device using the global timer. (This global timer clock
events is usually replaced by arch timer clock events for each of the
cores.)
When the A5 boots, we should not use the global timer interrupts or
write to the global timer registers. This is because even if there are
four global comparators, the control bits for all four are in the same
registers, and we would need to synchronize between the cpus. Instead,
the global timer FRC (already started by the A53) should be used as the
clock source, and one of the local timers which are not used by the A53
can be used for clock events on the A5.
To support this usecase, add a property to the binding to specify the
first local timer index to be used. If this parameter is non-zero, the
global timer interrupts will also not be used.
Signed-off-by: Vincent Whitchurch <vincent.whitchurch@axis.com>
---
Notes:
v2: New.
.../bindings/timer/samsung,exynos4210-mct.yaml | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/Documentation/devicetree/bindings/timer/samsung,exynos4210-mct.yaml b/Documentation/devicetree/bindings/timer/samsung,exynos4210-mct.yaml
index dce42f1f7574..46f466081836 100644
--- a/Documentation/devicetree/bindings/timer/samsung,exynos4210-mct.yaml
+++ b/Documentation/devicetree/bindings/timer/samsung,exynos4210-mct.yaml
@@ -47,6 +47,15 @@ properties:
reg:
maxItems: 1
+ local-timer-index:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ default: 0
+ maximum: 15 # Last local timer index
+ description: |
+ If present, sets the first local timer index to use. If this value is
+ set to a non-default value, the global timer will not be used for
+ interrupts.
+
interrupts:
description: |
Interrupts should be put in specific order. This is, the local timer
--
2.34.1
next prev parent reply other threads:[~2022-03-08 14:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 14:24 [PATCH v2 0/4] clocksource: Add MCT support for ARTPEC-8 Vincent Whitchurch
2022-03-08 14:24 ` [PATCH v2 1/4] dt-bindings: timer: exynos4210-mct: Add ARTPEC-8 MCT Vincent Whitchurch
2022-03-08 14:37 ` Krzysztof Kozlowski
2022-03-08 14:24 ` Vincent Whitchurch [this message]
2022-03-08 14:44 ` [PATCH v2 2/4] dt-bindings: timer: exynos4210-mct: Support using only local timer Krzysztof Kozlowski
2022-03-08 14:24 ` [PATCH v2 3/4] clocksource/drivers/exynos_mct: Support local-timer-index property Vincent Whitchurch
2022-03-08 14:57 ` Krzysztof Kozlowski
2022-03-11 11:35 ` Vincent Whitchurch
2022-03-11 12:51 ` Krzysztof Kozlowski
2022-03-21 8:00 ` Marek Szyprowski
2022-03-30 8:21 ` Vincent Whitchurch
2022-04-07 7:48 ` Vincent Whitchurch
2022-03-08 14:24 ` [PATCH v2 4/4] clocksource/drivers/exynos_mct: Enable building on ARTPEC Vincent Whitchurch
2022-03-08 14:58 ` 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=20220308142410.3193729-3-vincent.whitchurch@axis.com \
--to=vincent.whitchurch@axis.com \
--cc=alim.akhtar@samsung.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@axis.com \
--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
all inboxes | Powered by JetHome®