You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for submitting an SDK feature request. Please provide as much information you can.
Describe the feature
Many RTOS drivers contain peripheral access calls with an optional tick timeout. Right now most of these calls have an unsigned as the type for the timeout variable. This should be updated to the rtos_osal_tick_t type instead.
Will this change any current APIs? How?
Many function APIs will have a type change. It should not impact current usage though, as FreeRTOS is the only supported RTOS.
Who will benefit with this feature?
Anyone who tries to port a different RTOS, and wants to use the osal compliant drivers.
The text was updated successfully, but these errors were encountered:
Thank you for submitting an SDK feature request. Please provide as much information you can.
Describe the feature
Many RTOS drivers contain peripheral access calls with an optional tick timeout. Right now most of these calls have an
unsigned
as the type for the timeout variable. This should be updated to thertos_osal_tick_t
type instead.Will this change any current APIs? How?
Many function APIs will have a type change. It should not impact current usage though, as FreeRTOS is the only supported RTOS.
Who will benefit with this feature?
Anyone who tries to port a different RTOS, and wants to use the osal compliant drivers.
The text was updated successfully, but these errors were encountered: