<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>High power consumption with interrupt enabled</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/115577/high-power-consumption-with-interrupt-enabled</link><description>I would like to wake my app from sleep (k_msleep) on a GPIO interrupt. I&amp;#39;m finding that enabling the interrupt draws an additional 6uA however (8uA vs 2uA without it) - am I missing something, or is this normal? This is on an nRF52-DK dev board, using</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 16 Oct 2024 18:38:12 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/115577/high-power-consumption-with-interrupt-enabled" /><item><title>RE: High power consumption with interrupt enabled</title><link>https://devzone.nordicsemi.com/thread/506579?ContentTypeID=1</link><pubDate>Wed, 16 Oct 2024 18:38:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:923aac41-298c-4db4-8594-f0b20bb70f7a</guid><dc:creator>Dane du Plooy</dc:creator><description>&lt;p&gt;Thanks &lt;a href="https://devzone.nordicsemi.com/members/nordicator_5f00_prim3"&gt;nordicator_prim3&lt;/a&gt;&amp;nbsp;! That worked. I also found an alternative solution (not &amp;quot;better&amp;quot;, but FYI); use&amp;nbsp;GPIO_INT_LEVEL_ACTIVE and just disable the interrupt again immediately in the interrupt routine (otherwise it keeps firing).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: High power consumption with interrupt enabled</title><link>https://devzone.nordicsemi.com/thread/506574?ContentTypeID=1</link><pubDate>Wed, 16 Oct 2024 17:38:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cdef1db4-b0d0-40bd-b7d6-2e484df27fc8</guid><dc:creator>nordicator_prim3</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I saw saw current in that ballpark recently. If you&amp;#39;re using GPIOTE, then the current consumption can be higher than you would think. If the interrupt pin you need isn&amp;#39;t high frequency (sounds like it isn&amp;#39;t) then you can use the &amp;quot;sense-edge-mask&amp;quot; dts property on your GPIO node to tell it which pins on that port to not use gpiote on.&lt;/p&gt;
&lt;p&gt;I found that originally at &lt;a href="https://github.com/zephyrproject-rtos/zephyr/issues/28499"&gt;this github issue&lt;/a&gt; which was made before that dts property was added. Later in that thread, they point to where the fix was implemented &lt;a href="https://github.com/zephyrproject-rtos/zephyr/blob/cbd93a819854c3c8c7410ac2ab99fd42108b2630/dts/bindings/gpio/nordic%2Cnrf-gpio.yaml#L20-L25"&gt;here&lt;/a&gt;.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>