Interrupt energy intensive

RE: Interrupt energy intensive

boris bergman1 — Thu, 29 Aug 2024 11:35:07 GMT

Thanks, this works and uses exactly the same current as GPIO_INT_LEVEL_ACTIVE.

&gpio0 {
    sense-edge-mask = <0xFFFFFFFF>; //<0x400>;
};

Only, if I use 0x400 it consumes more. (pin 11)

RE: Interrupt energy intensive

Vidar Berg — Thu, 29 Aug 2024 08:22:41 GMT

I now understand the problem. I had only tested the GPIO_INT_LEVEL_ACTIVE with button presses and didn't realize that it would keep firing interrupts as long as the input signal is active. The solution is to revert back to using the GPIO_INT_EDGE_TO_ACTIVE flag and set the 'sense-edge-mask' property in your gpio node in the devicetree to enable the sense mechanism to be used for edge detection.

RE: Interrupt energy intensive

boris bergman1 — Wed, 28 Aug 2024 08:12:21 GMT

[quote userid="4240" url="~/f/nordic-q-a/114234/interrupt-energy-intensive/500128"]Sorry, but I'm not sure what you mean by this.[/quote]

I mean my trigger signal is HIGH(1) until my function (_data_handler) reads the register of my peripheral, then it turns LOW(0).

An GPIO_INT_EDGE_TO_ACTIVE trigger will only trigger once, when the signal goes from LOW to HIGH. a level trigger will trigger indefinite as long as this signal is HIGH.

That's the reason I turn of the trigger in my ISR (see my previous code snippet).

RE: Interrupt energy intensive

Vidar Berg — Wed, 28 Aug 2024 08:06:04 GMT

PORT events are used when you use the *_LEVEL_* flags with the gpio_pin_interrupt_configure_dt() function, and IN events are used when you use the *_EDGE_* flags. I don't know what your input signal looks like, but are you not having this problem when using GPIO_INT_EDGE_TO_ACTIVE?

[quote userid="120039" url="~/f/nordic-q-a/114234/interrupt-energy-intensive/500121"]I meant I configured my peripheral to signal 1 until _data_handler is executed.[/quote]

Sorry, but I'm not sure what you mean by this.

RE: Interrupt energy intensive

boris bergman1 — Wed, 28 Aug 2024 07:46:35 GMT

[quote userid="4240" url="~/f/nordic-q-a/114234/interrupt-energy-intensive/500103"]'m also not sure I understand which hardware changes you're referring to.[/quote]

I meant I configured my peripheral to signal 1 until _data_handler is executed.

[quote userid="4240" url="~/f/nordic-q-a/114234/interrupt-energy-intensive/500103"]Could you please post a snippet of your current code?[/quote]

static void lsm6dsl_data_handler(struct k_work *work);
K_WORK_DELAYABLE_DEFINE(_proces, _data_handler);

void _isr(const struct device *dev, struct gpio_callback *cb, uint32_t pins) {  
  gpio_pin_interrupt_configure_dt(&signal, GPIO_INT_DISABLE);
  LOG_INF("isr given");

  k_work_schedule(&_proces, K_NO_WAIT); 
}

void attachinterrupt(void) {

	__ASSERT(device_is_ready(signal.port), "custom device not ready");
	if(gpio_pin_configure_dt(&signal, GPIO_INPUT)) {
    LOG_ERR("error configure signalgpio");
  }

	if(gpio_pin_interrupt_configure_dt(&signal, GPIO_INT_LEVEL_HIGH)) {  //GPIO_INT_EDGE_TO_ACTIVE
    LOG_ERR("error configure interrupt signalgpio");
  };
	gpio_init_callback(&_interrupt, _isr, BIT(signal.pin));
	if(gpio_add_callback(signal.port, &_interrupt)) {
    LOG_ERR("callback for interrupt not set");
 };
}

[quote userid="4240" url="~/f/nordic-q-a/114234/interrupt-energy-intensive/500103"]Any GPIO input enabled with sense can trigger the PORT event.[/quote]

I don't really get how this translates to the events in Zephyr.

RE: Interrupt energy intensive

Vidar Berg — Wed, 28 Aug 2024 05:46:24 GMT

Are you saying that you need to clear the PORT event within your interrupt handler to prevent the interrupt from firing repeatedly? I'm also not sure I understand which hardware changes you're referring to. Could you please post a snippet of your current code?

[quote user="boris bergman1"]What triggers also belong to GPIOTE PORT event[/quote]

Any GPIO input enabled with sense can trigger the PORT event.

RE: Interrupt energy intensive

boris bergman1 — Tue, 27 Aug 2024 13:00:29 GMT

Thanks, but that'll only work when I configure my hardware to have a latched interrupt. This will cause an infinite loop, which I don't know how to resolve. I can immidiately disable the interrupt from the ISR routine. This won't ensure tough things are not executed twice. What triggers also belong to GPIOTE PORT event?

It does save ~12uA, thanks!

RE: Interrupt energy intensive

Vidar Berg — Tue, 27 Aug 2024 07:45:54 GMT

You may also consider enabling level triggering instead of edge triggering by replacing the GPIO_INT_EDGE_TO_ACTIVE flag with GPIO_INT_LEVEL_ACTIVE. Edge triggering uses GPIOTE IN instead of GPIOTE PORT events, which increases the idle current to ~17 uA. PORT events are suitable for detecting lower frequency inputs.

RE: Interrupt energy intensive

boris bergman1 — Mon, 26 Aug 2024 20:50:57 GMT

Thank you that was the issue.

RE: Interrupt energy intensive

hmolesworth — Mon, 26 Aug 2024 17:46:54 GMT

How much time does the pin spend high? I only ask as the pull-down is about 13k0 and 3.3V @ 13k = 250uA