<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Map Navigation Handwrite long delayed in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Map-Navigation-Handwrite-long-delayed/m-p/667933#M102757</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi community:&lt;/P&gt;&lt;P&gt;Map Navigation handwrite long delayed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. custorm board: iMX6 DualLite; BSP-3.10.53 , wayland, Qt5.2.1 , Cypress CY8CTMA touchscreen.&lt;/P&gt;&lt;P&gt;2. Only the touchscreen are connect to i2c-3. I have measured the interrupt of the touchscreen and sclk/data of the i2c-3 with oscilloscope,&amp;nbsp; Roughly 85 interrupts Per second, it seems normally with the oscilloscope or from the touchscreen dirver log or evtest.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Maybe the performance of Qt or something else?&amp;nbsp; This puzzled me for several weeks. Attached with a short video of long delayed handwriting.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any advice would be greatly appreciated&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 31 May 2017 02:48:57 GMT</pubDate>
    <dc:creator>yunyangsihai</dc:creator>
    <dc:date>2017-05-31T02:48:57Z</dc:date>
    <item>
      <title>Map Navigation Handwrite long delayed</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Map-Navigation-Handwrite-long-delayed/m-p/667933#M102757</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi community:&lt;/P&gt;&lt;P&gt;Map Navigation handwrite long delayed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. custorm board: iMX6 DualLite; BSP-3.10.53 , wayland, Qt5.2.1 , Cypress CY8CTMA touchscreen.&lt;/P&gt;&lt;P&gt;2. Only the touchscreen are connect to i2c-3. I have measured the interrupt of the touchscreen and sclk/data of the i2c-3 with oscilloscope,&amp;nbsp; Roughly 85 interrupts Per second, it seems normally with the oscilloscope or from the touchscreen dirver log or evtest.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Maybe the performance of Qt or something else?&amp;nbsp; This puzzled me for several weeks. Attached with a short video of long delayed handwriting.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any advice would be greatly appreciated&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 31 May 2017 02:48:57 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Map-Navigation-Handwrite-long-delayed/m-p/667933#M102757</guid>
      <dc:creator>yunyangsihai</dc:creator>
      <dc:date>2017-05-31T02:48:57Z</dc:date>
    </item>
    <item>
      <title>Re: Map Navigation Handwrite long delayed</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Map-Navigation-Handwrite-long-delayed/m-p/667934#M102758</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi yang,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Official NXP i.MX6 BSP&amp;nbsp;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;Cypress CY8CTMA touchscreen is not currently supported, so I guess the reason fo your delay could be due to the drivers itself, as suggestion check the interrupts times for touch kernel events. calls.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;Hope it helps&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 06 Jun 2017 16:12:32 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Map-Navigation-Handwrite-long-delayed/m-p/667934#M102758</guid>
      <dc:creator>Bio_TICFSL</dc:creator>
      <dc:date>2017-06-06T16:12:32Z</dc:date>
    </item>
  </channel>
</rss>

