On Fri, 15 Aug 2025 at 10:01, Corvin Köhne <corvin.koe...@gmail.com> wrote: > > From: YannickV <y.vos...@beckhoff.com> > > The a9 global timer and arm mp timer rely on the PERIPHCLK > as their clock source. The period of PERIPHCLK (denoted as N) > must be a multiple of the core CLK period, with N being equal > to or greater than two. However, the current implementation > does not take the PERIPHCLK period into account, leading to > unexpected behavior in systems where the application assumes > PERIPHCLK is clocked differently. > > The property periphclk-period represents the period N, the CLK > is devided by to get the peripheral clock PERIPHCLK. We can now > configure clock properties for the a9 global timer and arm mp > timer. That ensures timers can behave according to the > applications needs. > > The PERIPHCLK period can also be set via the command line, for > example for the a9 global timer: > -global driver=arm.cortex-a9-global-timer, > property=periphclk-period,value=2
Why is the property for the main clock frequency a value in Hz but the PERIPHCLK takes a period ? thanks -- PMM
