Inside gps_controller.c
We issue the following instruction to begin searching for a satellite fix.
k_delayed_work_submit(&gps_work.work,K_SECONDS(CONFIG_GPS_CONTROL_FIX_CHECK_INTERVAL));
When we have a fix we issue the following:
printk("Cancelling timer...\n");
k_delayed_work_submit(&gps_work.work,K_SECONDS(1));
After reading the brief in kernel.h as follows:
/**
* @brief Submit a delayed work item to the system workqueue.
*
* This routine schedules work item @a work to be processed by the system
* workqueue after a delay of @a delay milliseconds. The routine initiates
* an asynchronous countdown for the work item and then returns to the caller.
* Only when the countdown completes is the work item actually submitted to
* the workqueue and becomes pending.
*
* Submitting a previously submitted delayed work item that is still
* counting down cancels the existing submission and restarts the countdown
* using the new delay. If the work item is currently pending on the
* workqueue's queue because the countdown has completed it is too late to
* resubmit the item, and resubmission fails without impacting the work item.
* If the work item has already been processed, or is currently being processed,
* its work is considered complete and the work item can be resubmitted.
*
* @warning
* Work items submitted to the system workqueue should avoid using handlers
* that block or yield since this may prevent the system workqueue from
* processing other work items in a timely manner.
*
* @note Can be called by ISRs.
*
* @param work Address of delayed work item.
* @param delay Delay before submitting the work item (in milliseconds).
*
* @retval 0 Work item countdown started.
* @retval -EINVAL Work item is being processed or has completed its work.
* @retval -EADDRINUSE Work item is pending on a different workqueue.
* @req K-DWORK-001
*/
It seems to indicate that in order to cancel the existing queue item, all we need to do is issue the same instruction again with a very short timer.
Please let me know if we are doing the correct thing or are we causing a memory leak.
Our board needs a hard reset after about 12 hours.
