PCAL6408a IO Expander INT-Debounce

RE: PCAL6408a IO Expander INT-Debounce

MaLu — Tue, 08 Mar 2022 12:07:48 GMT

Hi,

Thank you very much for looking into this and for the notification!

RE: PCAL6408a IO Expander INT-Debounce

helsing — Tue, 08 Mar 2022 12:01:18 GMT

Hi Matthias,

This is addressed here: https://github.com/zephyrproject-rtos/zephyr/pull/43436

Feedback from the developer:

"Regarding the assertion in gpio_pin_interrupt_configure(), it is correct. Although the documentation does not state it in the best way, the GPIO_INT_DEBOUNCE flag, despite its name, is supposed to be used in a call to gpio_pin_configure(), not gpio_pin_interrupt_configure(). See this description."

Thanks again for reporting this :)

Best regards,

Håkon

RE: PCAL6408a IO Expander INT-Debounce

helsing — Thu, 17 Feb 2022 14:53:24 GMT

Hi Mattias,

Thank you for reporting this. I will forward this to the relevant developers and keep you updated.

Best regards,

Håkon

RE: PCAL6408a IO Expander INT-Debounce

MaLu — Thu, 17 Feb 2022 13:17:34 GMT

Update:

I realise that pin configure() might not have been the right function to look at, sorry.
In the pin Interrupt configure functions is essentially the same problem though.

The Flag gets an assert before even getting to a driver level functionat gpio_pin_interrupt_configure():

static inline int z_impl_gpio_pin_interrupt_configure(const struct device *port,
						      gpio_pin_t pin,
						      gpio_flags_t flags)
{
	const struct gpio_driver_api *api =
		(const struct gpio_driver_api *)port->api;
	const struct gpio_driver_config *const cfg =
		(const struct gpio_driver_config *)port->config;
	const struct gpio_driver_data *const data =
		(const struct gpio_driver_data *)port->data;
	enum gpio_int_trig trig;
	enum gpio_int_mode mode;

	__ASSERT_NO_MSG((flags & GPIO_INT_DEBOUNCE) == 0);
// ...
}