All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Vincent Whitchurch <vincent.whitchurch@axis.com>
Cc: krzk@kernel.org, tglx@linutronix.de, daniel.lezcano@linaro.org,
	kernel@axis.com, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org, alim.akhtar@samsung.com,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v3 1/4] dt-bindings: timer: exynos4210-mct: Add ARTPEC-8 MCT support
Date: Thu, 7 Apr 2022 10:04:09 -0500	[thread overview]
Message-ID: <Yk79acnuZE1Wj/3s@robh.at.kernel.org> (raw)
In-Reply-To: <20220407074432.424578-2-vincent.whitchurch@axis.com>

On Thu, Apr 07, 2022 at 09:44:29AM +0200, Vincent Whitchurch wrote:
> The ARTPEC-8 has an MCT with 4 global and 8 local timer interrupts.
> 
> The 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 free-running counter
> 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 (via the A53), it 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 hardware, add a compatible for the MCT as well as two
> new properties to describe the hardware-mandated sharing of the FRC and
> dedicating local timers to specific processors.
> 
> Signed-off-by: Vincent Whitchurch <vincent.whitchurch@axis.com>
> ---
> 
> Notes:
>     v3:
>     - Add all required bindings for ARTPEC-8 in one patch
>     - Rename and split local-timer-only to samsung,local-timers and
>       samsung,frc-shared
>     - Restrict above properties to the ARTPEC-8 compatible.
>     - Rewrite descriptions of properties to hopefully describe hardware.
>     
>     v2:
>     - Use devicetree property instead of module parameter.
> 
>  .../timer/samsung,exynos4210-mct.yaml         | 26 +++++++++++++++++++
>  1 file changed, 26 insertions(+)

What's this based on? Doesn't apply on v5.18-rc1.

Rob

WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Vincent Whitchurch <vincent.whitchurch@axis.com>
Cc: krzk@kernel.org, tglx@linutronix.de, daniel.lezcano@linaro.org,
	kernel@axis.com, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org, alim.akhtar@samsung.com,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v3 1/4] dt-bindings: timer: exynos4210-mct: Add ARTPEC-8 MCT support
Date: Thu, 7 Apr 2022 10:04:09 -0500	[thread overview]
Message-ID: <Yk79acnuZE1Wj/3s@robh.at.kernel.org> (raw)
In-Reply-To: <20220407074432.424578-2-vincent.whitchurch@axis.com>

On Thu, Apr 07, 2022 at 09:44:29AM +0200, Vincent Whitchurch wrote:
> The ARTPEC-8 has an MCT with 4 global and 8 local timer interrupts.
> 
> The 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 free-running counter
> 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 (via the A53), it 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 hardware, add a compatible for the MCT as well as two
> new properties to describe the hardware-mandated sharing of the FRC and
> dedicating local timers to specific processors.
> 
> Signed-off-by: Vincent Whitchurch <vincent.whitchurch@axis.com>
> ---
> 
> Notes:
>     v3:
>     - Add all required bindings for ARTPEC-8 in one patch
>     - Rename and split local-timer-only to samsung,local-timers and
>       samsung,frc-shared
>     - Restrict above properties to the ARTPEC-8 compatible.
>     - Rewrite descriptions of properties to hopefully describe hardware.
>     
>     v2:
>     - Use devicetree property instead of module parameter.
> 
>  .../timer/samsung,exynos4210-mct.yaml         | 26 +++++++++++++++++++
>  1 file changed, 26 insertions(+)

What's this based on? Doesn't apply on v5.18-rc1.

Rob

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-04-07 15:04 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-07  7:44 [PATCH v3 0/4] clocksource: Add MCT support for ARTPEC-8 Vincent Whitchurch
2022-04-07  7:44 ` Vincent Whitchurch
2022-04-07  7:44 ` [PATCH v3 1/4] dt-bindings: timer: exynos4210-mct: Add ARTPEC-8 MCT support Vincent Whitchurch
2022-04-07  7:44   ` Vincent Whitchurch
2022-04-07 15:04   ` Rob Herring [this message]
2022-04-07 15:04     ` Rob Herring
2022-04-08  6:58     ` Vincent Whitchurch
2022-04-08  6:58       ` Vincent Whitchurch
2022-04-08  7:16   ` Krzysztof Kozlowski
2022-04-08  7:16     ` Krzysztof Kozlowski
2022-04-07  7:44 ` [PATCH v3 2/4] clocksource/drivers/exynos_mct: Support frc-shared property Vincent Whitchurch
2022-04-07  7:44   ` Vincent Whitchurch
2022-04-08  7:17   ` Krzysztof Kozlowski
2022-04-08  7:17     ` Krzysztof Kozlowski
2022-04-07  7:44 ` [PATCH v3 3/4] clocksource/drivers/exynos_mct: Support local-timers property Vincent Whitchurch
2022-04-07  7:44   ` Vincent Whitchurch
2022-04-08  8:02   ` Krzysztof Kozlowski
2022-04-08  8:02     ` Krzysztof Kozlowski
2022-04-07  7:44 ` [PATCH v3 4/4] clocksource/drivers/exynos_mct: Enable building on ARTPEC Vincent Whitchurch
2022-04-07  7:44   ` Vincent Whitchurch

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=Yk79acnuZE1Wj/3s@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=alim.akhtar@samsung.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kernel@axis.com \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=vincent.whitchurch@axis.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.