[QUERY] : pinmux-pins GPIO interrupt pin

["Lad, Prabhakar" <prabhakar.csengg@xxxxxxxxx>]

Hi All,

When using GPIO pins as interrupts with the `gpios` DT property, it
follows the `gpio_request()`/`gpio_free()` path, and in this case, the
`pinmux-pins` sysfs file indicates that the pin is claimed by the
pinctrl/GPIO driver.

However, when the same GPIO pin is used as an interrupt with the
`interrupts` property, it doesn't follow the
`gpio_request()`/`gpio_free()` path, and the `pinmux-pins` sysfs file
shows it as `UNCLAIMED`.

What would be the correct approach when using GPIO pins as interrupts
with the `interrupts` property?

One possible solution could be to hog the GPIO pin as an input when
using it as an interrupt with the `interrupts` property, ensuring it
is claimed by the pinctrl/GPIO driver.

Any pointers on how we can fix this so that the `pinmux-pins` sysfs
file reports it as claimed?

Cheers,
Prabhakar