I got it Mr Nutt,
thanks for the detailed explanation!
Em ter., 16 de mar. de 2021 às 16:04, Gregory Nutt
escreveu:
> The oneshot and free-running OS timers have value even without tickless
> mode. But they are not required by the OS. I think you have a complete
> BSP without them.
>
> The si
The oneshot and free-running OS timers have value even without tickless
mode. But they are not required by the OS. I think you have a complete
BSP without them.
The single timer approach is a lot more difficult. The free-running and
oneshot timers are very easy to program. the first is jus
Hummm.. I see.
For the tickless implementation with 2 timers it's interesting to have the
_oneshot.c to help implement the System Interfaces along with the
_freerun.c.
The 2 timers approach is intended to keep one timer to track time and the
another to drive the events?
What would be the hardware
Most architectures support a timer library. The _oneshot.c file
is a wrapper around the library that creates an internal one shot
driver. That oneshot does not depend on the onshot driver and can be
used anywhere in the OS architecture-specific code where you need a
oneshot. The _lowerhalf.c
Hi all,
I've been working on the oneshot driver implementation for ESP32 and
I've noticed that other chips split the implementation into 2 files:
- _oneshot_lowerhalf.c
- _oneshot.c
The second file is not used at all besides the lowerhalf. And the
lowerhalf file seems more like a wrap
