<?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>The INT pin is pulled down, but sometimes it takes 1 second to interrupt</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/128809/the-int-pin-is-pulled-down-but-sometimes-it-takes-1-second-to-interrupt</link><description>Hi: 
 I use ncs 3.3.0 and nrf54lm20dk. 
 USB mode running phenomenon: Mouse stuttering. 
 But use ncs 3.1.0 mouse is very smooth. 
 Since the ncs3.1.0 version does not support nrf54lm20 BLE, I switched to ncs3.3.0.</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 27 Jul 2026 11:58:34 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/128809/the-int-pin-is-pulled-down-but-sometimes-it-takes-1-second-to-interrupt" /><item><title>RE: The INT pin is pulled down, but sometimes it takes 1 second to interrupt</title><link>https://devzone.nordicsemi.com/thread/569506?ContentTypeID=1</link><pubDate>Mon, 27 Jul 2026 11:58:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5c3a3ff1-e1e5-46ce-a93d-99c30b807f99</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;&lt;span&gt;When defining a &amp;quot;direct&amp;quot; ISR (Ref.&amp;nbsp;&lt;a href="https://nrfconnectdocs.nordicsemi.com/ncs/latest/zephyr/kernel/services/interrupts.html#defining-a-direct-isr"&gt;https://nrfconnectdocs.nordicsemi.com/ncs/latest/zephyr/kernel/services/interrupts.html#defining-a-direct-isr&lt;/a&gt;), &lt;/span&gt;it is important to return &amp;quot;1&amp;quot; from the ISR if you want the scheduler to run on return, which is required in your code if you want the PMW3360_EVENT_DATA_READY event to be processed immediately after the interrupt. Please try this and check if it fixes the pin interrupt detection&amp;nbsp;delay you are&amp;nbsp;observing.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Vidar&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>