Work queues

RE: Work queues

Tron — Thu, 16 Apr 2020 11:31:09 GMT

I totally redesigned the solution, and now got it to work.

The way I solved it was to start the GSensor in the regular thread, and submit a delayed work to the normal work queue in order to stop the interupt.

I thank you for your patience.

RE: Work queues

Hakon — Tue, 24 Mar 2020 15:53:03 GMT

Have you tried calling k_delayed_work_cancel() outside of the ISR? I tested this and it works, but calling it inside gave me a hardfault.

RE: Work queues

Tron — Mon, 23 Mar 2020 10:28:35 GMT

First start on GPS, I get error code -22:

]Turning gsensor ON
[3.23 11.26.58.090]Turning LNA	ON
[3.23 11.26.58.090]Turned LNA ON
[3.23 11.26.58.090]Cancel GPS work resutlt: -22
[3.23 11.26.59.098]GPS	thread_id: 0x20028ce0
[3.23 11.26.59.098]GPS	started	successfully.

Hope this helps

RE: Work queues

Hakon — Mon, 23 Mar 2020 09:12:04 GMT

Have you checked the return code for when you run k_delayed_work_cancel() in gps_control_start()?

RE: Work queues

Tron — Thu, 19 Mar 2020 19:31:57 GMT

GSensor custom defined worker thread has priority 5, I am a lazy bugger, and this was the suggested priority in the sample.

Main thread has pri 7 (according to the prj.conf) file, and system work queue has default priority(whatever that is), I havent found any files where it has been changed from the default config.

RE: Work queues

Hakon — Thu, 19 Mar 2020 16:10:34 GMT

What priorities do you have on the work queues and on main?

RE: Work queues

Tron — Wed, 18 Mar 2020 13:55:06 GMT

This is how I use the system work queue (GPS work item):

void  gps_control_stop(u32_t delay_ms) {
#if !defined(CONFIG_GPS_SIM)
    if (gps_control_is_active()) {
        setLNAState(false);
        atomic_set(&gps_is_active, 0);

        k_delayed_work_cancel(&gps_work.work);
        gps_work.type = GPS_WORK_STOP;
        k_delayed_work_submit(&gps_work.work, delay_ms);
    }
#endif
}

void gps_control_start(u32_t delay_ms) {
#if !defined(CONFIG_GPS_SIM)
    setLNAState(true);
    atomic_set(&gps_is_active, 1);
    //    setLedState(LED_RED, true);
    k_delayed_work_cancel(&gps_work.work);
    gps_work.type = GPS_WORK_START;
    k_delayed_work_init(&gps_work.work, gps_work_handler);

    k_delayed_work_submit(&gps_work.work, delay_ms);
#endif
}

The code for using the dedicated work queue is as follows:

void nRFGSensorInit(void) {
    printk("Starting GSensor init\n");
    gpio_vdd_sensor(true);
    i2c_gpio_init();

    nRFGSensorInitWorkQueue();
    printk("Gsensor work queue init complete\n");
    //set Shock	Level for the accelerometer
    adxl343_init(GSENSOR_STARTUP_SHOCKLEVEL);

    gpio_vdd_sensor(false);
    //Turn on all axes
    //setActivityXYZ(true, true, true);
    gpio_adxl343_interrupt_configure(gpio_adxl_interrupt_handler);

    k_delayed_work_init(&gsensor_work.work, gsensor_handler);

    printk("i2c	gsensor	init complete!\n");
    
    k_delayed_work_submit_to_queue(&gsensor_work_q, &gsensor_work.work,	K_SECONDS(240));
    printk("Starting gsensor process in	4 minutes\n");
}


void gpio_adxl_interrupt_handler(struct	device *port, struct gpio_callback *cb,	u32_t pins) {
    printk("Interrupt from GSensor received!\n");
    if (callback != NULL) {
	callback(NULL);
    }
    k_delayed_work_cancel(&gsensor_work.work);
    gsensor_work.type=GSENSOR_STOP;
    k_delayed_work_submit_to_queue(&gsensor_work_q, &gsensor_work.work,	K_NO_WAIT);
}

As far as I can see, there is no API call to cansel a delayed work item from a specific work queue, Therefore the k_delayed_work_cancel without the queue parameter.

Hope this helps

RE: Work queues

Hakon — Wed, 18 Mar 2020 13:41:04 GMT

Hello,

can you share the code where you use the system work queue, and also the rest of the code where you use a dedicated work queue. That way I can see if you are doing something wrong in the code.