linux-kernel - Re: [PATCH v5 0/2] Add the System Timer Module for the NXP S32 architecture

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1a05e237-4ee1-4e36-a6e8-9efb5d9739fd@linaro.org>
Date: Thu, 24 Apr 2025 15:33:01 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Daniel Lezcano <daniel.lezcano@...aro.org>, tglx@...utronix.de
Cc: linux-kernel@...r.kernel.org, thomas.fossati@...aro.org,
 Larisa.Grigore@....com, ghennadi.procopciuc@....com, S32@....com
Subject: Re: [PATCH v5 0/2] Add the System Timer Module for the NXP S32
 architecture

On 17/04/2025 17:16, Daniel Lezcano wrote:
> These couple of changes bring the System Timer Module - STM which is
> part of the NXP S32 architecture.
> 
> The timer module has one counter and four comparators, an interrupt
> line when one of the comparator matches the counter. That means the
> interrupt is shared across the comparator.
> 
> The number of STM is equal to the number of core available on the
> system. For the s32g2 variant, there are three Cortex-M3 and four
> Cortex-A53, consequently there are seven STM modules dedicated to
> those.
> 
> In addition, there is a STM variant which is read-only, so the counter
> can not be set because it is tied to another STM module dedicated to
> timestamp. These special STM modules are apart and will be handled
> differently as they can not be used as a clockevent. They are not part
> of these changes.
> 
> The choice is to have one STM instance, aka one STM description in the
> device tree, which initialize a clocksource and a clockevent per
> CPU. The latter is assigned to a CPU given the order of their
> description. First is CPU0, second is CPU1, etc ...
> 
> Changelog:
> 
>  - v5
>    - Fixed typos in the comments (Ghennadi Procopciuc)
>    - Added clocks bindings for the module and the register (Ghennadi Procopciuc)
>    - Fixed help in the Kconfig option (Ghennadi Procopciuc)
>    - Changed max_ticks to ULONG_MAX when registering the clockevent
>    - Removed Reviewed-by tag from Krzysztof Kozlowski as the binding changed
Unimportant changes do not justify dropping people's review.

Best regards,
Krzysztof