kernel/drivers/clocksource/timer-vf-pit.c, branch linux-rolling-stableHosts the 0x221E linux distro kernel.https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-rolling-stable2025-09-23T10:30:05Zclocksource/drivers/vf-pit: Rename the VF PIT to NXP PIT2025-09-23T10:30:05ZDaniel Lezcanodaniel.lezcano@linaro.org2025-08-04T15:23:36Zurn:sha1:fc346a155fe910a1cf4639b00b131f9a10284bdd
The PIT acronym stands for Periodic Interrupt Timer which is found on
different NXP platforms not only on the Vybrid Family. Change the name
to be more generic for the NXP platforms in general. That will be
consistent with the NXP STM driver naming convention.
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Link: https://lore.kernel.org/r/20250804152344.1109310-19-daniel.lezcano@linaro.org
clocksource/drivers/vf-pit: Unify the function name for irq ack2025-09-23T10:30:00ZDaniel Lezcanodaniel.lezcano@linaro.org2025-08-04T15:23:35Zurn:sha1:3c34321e9b5965fdbf51fd407a35322a64c9e9c6
Most the function are under the form pit_timer_*, let's change the
interrupt acknowledgment function name to have the same format.
No functional changes intended.
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Link: https://lore.kernel.org/r/20250804152344.1109310-18-daniel.lezcano@linaro.org
clocksource/drivers/vf-pit: Consolidate calls to pit_*_disable/enable2025-09-23T10:29:55ZDaniel Lezcanodaniel.lezcano@linaro.org2025-08-04T15:23:34Zurn:sha1:5ba405c719ce68a86308dd3bd90aeea59959030d
The difference between the pit_clocksource_enable() and
pit_clocksource_disable() is only setting the TIF flag for the
clockevent. Let's group them and pass the TIF flag parameter to the
function so we save some lines of code. But as the base address is
different regarding if it is a clocksource or a clockevent, we pass
the base address in parameter instead of the struct pit_timer.
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Link: https://lore.kernel.org/r/20250804152344.1109310-17-daniel.lezcano@linaro.org
clocksource/drivers/vf-pit: Encapsulate set counter function2025-09-23T10:29:50ZDaniel Lezcanodaniel.lezcano@linaro.org2025-08-04T15:23:33Zurn:sha1:46e83e4afc05c87b5edc2b0b4765283f101af0c6
Encapsulate the writel() calls to set the counter into a
self-explainatory function.
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Link: https://lore.kernel.org/r/20250804152344.1109310-16-daniel.lezcano@linaro.org
clocksource/drivers/vf-pit: Enable and disable module on error2025-09-23T10:29:45ZDaniel Lezcanodaniel.lezcano@linaro.org2025-08-04T15:23:32Zurn:sha1:13cea8527c95e1359191347abe5d94cccc47a311
Encapsulate the calls to writel to enable and disable the PIT module
and make use of them. Add the missing module disablement in case of
error.
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Link: https://lore.kernel.org/r/20250804152344.1109310-15-daniel.lezcano@linaro.org
clocksource/drivers/vf-pit: Encapsulate clocksource enable / disable2025-09-23T10:29:39ZDaniel Lezcanodaniel.lezcano@linaro.org2025-08-04T15:23:31Zurn:sha1:fcf25b4427c7d1edb91dd02753d6153fb25da094
For the sake of lisibility, let's encapsulate the writel calls to
enable and disable the timer into a function with a self-explainatory
name.
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Link: https://lore.kernel.org/r/20250804152344.1109310-14-daniel.lezcano@linaro.org
clocksource/drivers/vf-pit: Use the node name for the interrupt and timer names2025-09-23T10:29:34ZDaniel Lezcanodaniel.lezcano@linaro.org2025-08-04T15:23:30Zurn:sha1:7201c95c258936e32c950f447c59875780046848
In order to differentiate from userspace the pit timer given the
device tree, let's use the node name for the interrupt and the timer
names.
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Link: https://lore.kernel.org/r/20250804152344.1109310-13-daniel.lezcano@linaro.org
clocksource/drivers/vf-pit: Encapsulate the PTLCVAL macro2025-09-23T10:29:29ZDaniel Lezcanodaniel.lezcano@linaro.org2025-08-04T15:23:29Zurn:sha1:d8629b9b2c17a458ca504b10b604b8cfe95df3ab
Pass the channel and the base address to the PITLCVAL macro so it is
possible to use multiple instances of the timer with the macro.
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Link: https://lore.kernel.org/r/20250804152344.1109310-12-daniel.lezcano@linaro.org
clocksource/drivers/vf-pit: Encapsulate the macros2025-09-23T10:29:22ZDaniel Lezcanodaniel.lezcano@linaro.org2025-08-04T15:23:28Zurn:sha1:1ba63930e72356315e1a664952f52ee340edbbd3
Pass the base address to the macro, so we can use the macro with
multiple instances of the timer because we deal with different base
address. At the same time, change writes to the register to the
existing corresponding functions.
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Link: https://lore.kernel.org/r/20250804152344.1109310-11-daniel.lezcano@linaro.org
clocksource/drivers/vf-pit: Register the clocksource from the driver2025-09-23T10:29:15ZDaniel Lezcanodaniel.lezcano@linaro.org2025-08-04T15:23:27Zurn:sha1:c106b698ab8d1899d62de880d73dd99edb319849
The function clocksource_mmio_init() uses its own global static
clocksource variable making no possible to have several instances of a
clocksource using this function. In order to support that, let's add
the clocksource structure to the pit structure and use the
clocksource_register_hz() function instead.
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Link: https://lore.kernel.org/r/20250804152344.1109310-10-daniel.lezcano@linaro.org