GPIO interrupt configuration failed on nRF9160 with npm1300

RE: GPIO interrupt configuration failed on nRF9160 with npm1300

Piziwate — Mon, 28 Jul 2025 06:31:14 GMT

Thanks for the clarification — it's unfortunate that GPIO interrupts on the nPM1300 can't be used in a standard way through Zephyr's GPIO API.

It would be much cleaner and more maintainable if these GPIOs could be exposed via a proper gpio_driver_api implementation, allowing the use of standard Zephyr mechanisms like gpio_pin_configure_dt() and gpio_pin_interrupt_configure_dt().

RE: GPIO interrupt configuration failed on nRF9160 with npm1300

Piziwate — Mon, 28 Jul 2025 06:04:48 GMT

We are using the QFN version.

RE: GPIO interrupt configuration failed on nRF9160 with npm1300

Kazi Afroza Sultana — Thu, 24 Jul 2025 12:36:21 GMT

Hello,

One more thing to ask, which package of nPM1300 (QFN or CSP) you are using?

RE: GPIO interrupt configuration failed on nRF9160 with npm1300

Kazi Afroza Sultana — Thu, 24 Jul 2025 11:02:35 GMT

Hello,

The error mentions interrupt configuration which has code -88 (ENOSYS, not implemented), We suspect there is an interrupt directly on the PMIC pin, which is not supported.

To get interrupts from button presses connected to PMIC, you have to try differently

1. Define PMIC interrupt callback

static void pmic_callback(const struct device *dev, struct gpio_callback *cb, uint32_t events)
{
    if (events & BIT(NPM1300_EVENT_GPIO0_EDGE)) {
        // button connected to nPM1300 GPIO0 is pressed or released
    }
    // handle other events in the same manner
}

2. Register it using npm1300 mfd API

static struct gpio_callback event_cb;

gpio_init_callback(&event_cb, pmic_callback, BIT(NPM1300_EVENT_GPIO0_EDGE) /* | more_events */);
mfd_npm1300_add_callback(pmic, &event_cb);

You can check out the one button sample source to see how we set up event handling on nPM1300 (that one uses different events, but the approach is the same)

RE: GPIO interrupt configuration failed on nRF9160 with npm1300

Piziwate — Mon, 21 Jul 2025 12:14:37 GMT

Hello,

Here is the current mapping :

button0 -> GPIO 0.0 from the nRF9160
button1 -> GPIO 0.1 from the nRF9160
button2 -> GPIO 0.2 from the nRF9160
button3 -> GPIO 0.3 from the nRF9160
button4 -> GPIO 0.4 from the nRF9160
button5 -> GPIO 0 from the nPM1300
button6 -> GPIO 1 from the nPM1300

If I look at the input_gpio_keys source file in Zephyr, the pin numbers corresponds to the button index. This has nothing to do with the GPIO pin.
In my case I only use GPIO 0 and 1 on the nPM1300 (and the GPIO4 has interrupt).

RE: GPIO interrupt configuration failed on nRF9160 with npm1300

Kazi Afroza Sultana — Mon, 21 Jul 2025 11:51:52 GMT

Hello,

I can see from the device tree overlay for button; you have defined button 5. nPM1300 only supports GPIO[0..4]; According to pin configuration ''The GPIO peripheral implements up to 5 pins, GPIO[0...4]. Each of these pins can be individually configured in the GPIOMODE[n] registers.''.

source: GPIO — General purpose input/output

The error message about "Pin 5" suggests there may be an off-by-one error or a misconfiguration in the device tree.