https://devzone.nordicsemi.com/f/nordic-q-a/64644/increased-power-consumption-when-using-gpiote-on-nrf52840We see an increased power consumption at around 26uA when enabling GPIOTE IN events in our application with a NRF52840_xxAA_REV1 chip. We use nRF5_SDK_15.2.0_9412b96 and the following code: // reg is NRF_P1, pin is 13 reg-&gt;PIN_CNF[pin] &amp;= ~(GPIO_PIN_CNF_DIR_Msken-USTelligent Community 13Mon, 10 Aug 2020 12:22:24 GMThttps://devzone.nordicsemi.com/thread/263819?ContentTypeID=1Mon, 10 Aug 2020 12:22:24 GMT137ad170-7792-4731-bb38-c0d22fbe4515:482293a9-f111-4d89-902d-c3c5c8b238abVidar Berg<p>Hello,</p> <p>Yes, this is an expected power increase. For low power operation, you may consider using GPIOTE PORT events instead.</p> <p><strong>Here is typ. sleep current with IN vs PORT events from the PS (<a href="https://infocenter.nordicsemi.com/topic/ps_nrf52840/_tmp/graviton/autodita/CURRENT/parameters.i_sleep.html">link</a>): </strong></p> <table border="1" cellpadding="4" cellspacing="0" frame="border" rules="all" summary=""> <tbody> <tr> <td style="vertical-align:top;" colspan="1" headers="d4783e47" rowspan="1">I_{ON_RAMON_GPIOTE}</td> <td style="vertical-align:top;" colspan="1" headers="d4783e50" rowspan="1"> <p>System ON, full 256 kB RAM retention, wake on GPIOTE input (event mode)</p> </td> <td style="vertical-align:top;" colspan="1" headers="d4783e53" rowspan="1"></td> <td style="vertical-align:top;" colspan="1" headers="d4783e56" rowspan="1"></td> <td style="vertical-align:top;" colspan="1" headers="d4783e59" rowspan="1"></td> <td style="vertical-align:top;" colspan="1" headers="d4783e63" rowspan="1"><span> </span></td> <td style="vertical-align:top;" colspan="1" headers="d4783e66" rowspan="1"><span>17.37</span></td> <td style="vertical-align:top;" colspan="1" headers="d4783e69" rowspan="1"><span> </span></td> <td style="vertical-align:top;" colspan="1" headers="d4783e72" rowspan="1">µA</td> <td style="vertical-align:top;" colspan="1" headers="d4783e75" rowspan="1"></td> </tr> <tr> <td style="vertical-align:top;" colspan="1" headers="d4783e47" rowspan="1">I_{ON_RAMON_GPIOTEPORT}</td> <td style="vertical-align:top;" colspan="1" headers="d4783e50" rowspan="1"> <p>System ON, full 256 kB RAM retention, wake on GPIOTE PORT event</p> </td> <td style="vertical-align:top;" colspan="1" headers="d4783e53" rowspan="1"></td> <td style="vertical-align:top;" colspan="1" headers="d4783e56" rowspan="1"></td> <td style="vertical-align:top;" colspan="1" headers="d4783e59" rowspan="1"></td> <td style="vertical-align:top;" colspan="1" headers="d4783e63" rowspan="1"><span> </span></td> <td style="vertical-align:top;" colspan="1" headers="d4783e66" rowspan="1"><span>2.36</span></td> <td style="vertical-align:top;" colspan="1" headers="d4783e69" rowspan="1"><span> </span></td> <td style="vertical-align:top;" colspan="1" headers="d4783e72" rowspan="1">µA</td> <td style="vertical-align:top;" colspan="1" headers="d4783e75" rowspan="1"></td> </tr> </tbody> </table> <p></p> <p><strong>And an explanation of the difference between PORT and IN events from the GPIOTE driver documentation:</strong></p> <ul> <li><a href="https://infocenter.nordicsemi.com/topic/sdk_nrf5_v17.0.0/hardware_driver_gpiote.html#gpiote_in">Using a dedicated IN_EVENT: When using a dedicated IN_EVENT, one pin is assigned to an event. Only a limited number of pins can be sensed this way because there is a limited number of TASK/EVENT channels. When an IN_EVENT is enabled, it requests the high frequency clock. Therefore, this method is not suitable for scenarios where the system sleeps for a long period of time, expecting to be waken up by a pin level change. This method supports detection of toggling, low-to-high, and high-to-low transition.</a></li> <li><a href="https://infocenter.nordicsemi.com/topic/sdk_nrf5_v17.0.0/hardware_driver_gpiote.html#gpiote_in">Using a PORT event: A PORT event is a single event that is triggered whenever the value of any of the input pins that have sensing enabled changes. Pins can be configured to sense low-to-high or high-to-low transition. Toggle sensing is emulated in the driver by changing the sense configuration whenever a PORT event for a given pin is detected. Using a PORT event requires only a low frequency clock. Therefore, this method is suitable for scenarios where the application expects to be inactive for a long period of time, waiting for a pin level change. The event can be shared by multiple pins; therefore it should be used for sensing slowly changing signals only.</a></li> </ul> <p></p><div style="clear:both;"></div>