Jukka Laitinen be68354b6a px4_work_queue: Start worker runner depending on whether initiated from kernel or user side ...

This uses px4_task_spawn_cmd instead of pthread, since px4_task_spawn_cmd is already
made to start worker on proper side.

TODO: check that we don't accidentally run user-side code in kernel context in work queue.
The work items should be scheduled to work queues depending on whether the actual callback
is on kerne/user side.

Signed-off-by: Jukka Laitinen <jukkax@ssrc.tii.ae>

2021-09-23 13:57:48 +03:00

..

test

WorkItem modules: Run() shouldn't be public

2020-01-22 12:03:03 -05:00

CMakeLists.txt

Remove px4_work_queue linking to px4_platform

2021-09-23 13:57:48 +03:00

ScheduledWorkItem.cpp

drivers/tone_alarm and tune_control small improvements/cleanup

2020-10-05 21:39:26 -04:00

WorkItem.cpp

px4_work_queue: reset statistics after each status print

2020-09-02 10:09:13 -04:00

WorkItemSingleShot.cpp

px4_work_queue: add WorkItemSingleShot

2020-03-17 23:31:17 -04:00

WorkQueue.cpp

Fix memory corruption when work queue is being deleted

2021-08-27 10:43:45 +02:00

WorkQueueManager.cpp

px4_work_queue: Start worker runner depending on whether initiated from kernel or user side

2021-09-23 13:57:48 +03:00