<?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>How to use single GPIOTE interrupt handler to handle two different events?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/7529/how-to-use-single-gpiote-interrupt-handler-to-handle-two-different-events</link><description>We are using two GPIOTE inputs and there is only 1 GPIOTE interrupt handler.
One of the GPIOTE input is from a power line chip that toggles @ 50 Hz rate. This GPIOTE input is used for AC zero cross detection on every rising edge, While the other GPIOTE</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 17 Jun 2015 09:14:24 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/7529/how-to-use-single-gpiote-interrupt-handler-to-handle-two-different-events" /><item><title>RE: How to use single GPIOTE interrupt handler to handle two different events?</title><link>https://devzone.nordicsemi.com/thread/26826?ContentTypeID=1</link><pubDate>Wed, 17 Jun 2015 09:14:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:028d8e65-7686-45ae-b2ae-ff4f1ca89c7a</guid><dc:creator>JohnBrown</dc:creator><description>&lt;p&gt;I would guess that the zero crossing is the highest priority here, so why not add some code in the zero crossing servic routine(after the dimming has been taken care of) to read the on/off switch in a pedestrian polling manner? You could then handle this directly or by scheduling an event.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>