Skip to content

[Tracking] modules depending on 64-bit xtimer implementation #13667

@jue89

Description

@jue89

Description

The new ztimer offers the pseudo-module ztimer_xtimer_compat that replaces all xtimer related API by ztimer functions. Since ztimer doesn't offer 64-bit timers, no replacement functions can be found for the xtimer_*64() functions.

In most cases, those 64-bit timers are used for long-running timers. However, the high precision is not required.

This issue tracks modules that require the 64-bit xtimer functions and are not compatible with ztimer_xtimer_compat. The highlighted modules are using the 64-bit implementation just for long-running timers (as far as I understand the code on the first glimpse ...).

sys
drivers
  • drivers/ata8520e: wait for uint8 (256) seconds with us resolution -> 32 bit is enough (one function rewrite) drivers/ata8520e: migrate to ztimer #17105
  • drivers/ltc4150: has a 64Bit timestamp callback MODULE_ZTIMER_NOW64 but would consider redefining the API to 32Bit
  • drivers/pir: timestamp to calculate the occupation between readout i think this can live with 32 Bit (time between readout < the 2^32 usec) or MODULE_ZTIMER_NOW64
  • drivers/rn2xx3: wait for uint8 (256) seconds with us resolution -> 32 bit is enough (one function rewrite) drivers/rn2xx3: migrate to ztimer #17112
  • drivers/xbee: wait 1 second with us precision -> 32 bit is enough (one function rewrite) drivers/xbee: migrate to ztimer_msec #17114
pkg

Metadata

Metadata

Labels

Area: timersArea: timer subsystemsType: enhancementThe issue suggests enhanceable parts / The PR enhances parts of the codebase / documentationType: trackingThe issue tracks and organizes the sub-tasks of a larger effort

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions