4e3b92609b
The new API cannot be used from userspace because it is not merely a wrapper around existing userspace-capable objects (threads and queues), but instead requires much more complex and lower-level access to memory that can't be touched from userspace. The vast majority of work queue users are operating from privileged mode, so there's little motivation to go through the pain and complexity of converting all functions to system calls. Copy the necessary pieces of the existing userspace work queue API out and expose them with new names and types: * k_work_handler_t becomes k_work_user_handler_t * k_work becomes k_work_user * k_work_q becomes k_work_user_q etc. Because the replacement API cannot use the same types new API names are also introduced to make it more clear that the userspace work queue API is a separate functionality. Signed-off-by: Peter Bigot <peter.bigot@nordicsemi.no> |
||
|---|---|---|
| .. | ||
| app_kernel | ||
| boot_time | ||
| cmsis_dsp | ||
| data_structure_perf | ||
| footprints | ||
| latency_measure | ||
| mbedtls | ||
| sched | ||
| sys_kernel | ||