Hi all, The TI dmtimer has been using a custom API to expose some hardware timer features for PWM and remoteproc so far with struct omap_dm_timer_ops. It seems that for most part we can nowadays replace most of the custom API with chained interrupts and clock provider features. There are lots of the dmtimer instances on TI SoCs, some have tens of them. Some timers have an IO pad available, which means the timers could be used as clock output for an external device with a 50% duty cycle. The timers also have input capture capability, but that is not currently supported. There have been some patches posted earlier for the PWM capture support though. These patches are against v6.1-rc2, and need also the following pending patch: [PATCH] clocksource/drivers/timer-ti-dm: Clear settings on probe and free For am6, these patches depend on the pending dts changes posted earlier: [PATCH v3 0/2] Configure dmtimers for am65 [PATCH 1/2] arm64: dts: ti: k3-am62: Add general purpose timers for am62 I have only lightly tested this so far to make sure I get clock output on k3-am625-sk on TIMER_IO2 at user expansion connector pin 10. I have not worried at all so far about disabling the legacy API if used with interrupts and clock framework. Regards, Tony Tony Lindgren (3): clocksource/drivers/timer-ti-dm: Add lock for register access clocksource/drivers/timer-ti-dm: Implement chained irq clocksource/drivers/timer-ti-dm: Add clock provider support drivers/clocksource/timer-ti-dm.c | 591 +++++++++++++++++++++++++++++- drivers/pwm/pwm-omap-dmtimer.c | 1 + include/clocksource/timer-ti-dm.h | 2 + 3 files changed, 578 insertions(+), 16 deletions(-) -- 2.37.3
