<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://test-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>GPIOs vs Interrupts</title><link>https://test-devzone.nordicsemi.com/f/nordic-q-a/88480/gpios-vs-interrupts</link><description>Hello, 
 I&amp;#39;m familiar with the GPIO and GPIOTE peripherals, 
 The GPIOTE has 8 channels, so it can use 8 GPIO pins to fire interrupts. 
 Some questions: 
 - Can the 8 Channels fire completely independent interrupt handlers? 
 - Can any GPIO enabled pin</description><dc:language>en-US</dc:language><generator>Telligent Community 13 Non-Production</generator><lastBuildDate>Mon, 23 May 2022 12:43:33 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://test-devzone.nordicsemi.com/f/nordic-q-a/88480/gpios-vs-interrupts" /><item><title>RE: GPIOs vs Interrupts</title><link>https://test-devzone.nordicsemi.com/thread/370308?ContentTypeID=1</link><pubDate>Mon, 23 May 2022 12:43:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4f610c80-8d0b-4efc-ba20-55a9e0f82b88</guid><dc:creator>user2111</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;&lt;a href="https://infocenter.nordicsemi.com/topic/ps_nrf52840/gpiote.html#register.INTENSET"&gt;https://infocenter.nordicsemi.com/topic/ps_nrf52840/gpiote.html#register.INTENSET&lt;/a&gt;&amp;nbsp;&lt;br /&gt;There is only one interrupt handler triggered yes, but the source may be 9 different events (EVENTS_IN[0..7] and EVENTS_PORT). So in the interrupt handler you need to check which event triggered, and clear the corresponding event. Any GPIO can be used for events.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>