<?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 imx6ul hrtimer problem in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/imx6ul-hrtimer-problem/m-p/1193709#M165983</link>
    <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I'm using&amp;nbsp;&lt;SPAN&gt;imx6ulevk&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;YOCTO sumo linux kernel L4.14.98-2.3.1.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;I'm testing the minimum timing of hrtimer in imx6ul. My testing is just enable the hrtimer for a period (e.g 5 ms) and each period we toggle the gpio result.&lt;/P&gt;&lt;P&gt;I found that the minimum timer is only 96 micro seconds even though I set the timing to 50 micro second. It's quite slow.&lt;/P&gt;&lt;P&gt;In my application, I want at least 10 micro seconds timer.&lt;/P&gt;&lt;P&gt;Anyone have the idea?&lt;/P&gt;</description>
    <pubDate>Fri, 04 Dec 2020 05:42:51 GMT</pubDate>
    <dc:creator>wayneshih</dc:creator>
    <dc:date>2020-12-04T05:42:51Z</dc:date>
    <item>
      <title>imx6ul hrtimer problem</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/imx6ul-hrtimer-problem/m-p/1193709#M165983</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I'm using&amp;nbsp;&lt;SPAN&gt;imx6ulevk&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;YOCTO sumo linux kernel L4.14.98-2.3.1.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;I'm testing the minimum timing of hrtimer in imx6ul. My testing is just enable the hrtimer for a period (e.g 5 ms) and each period we toggle the gpio result.&lt;/P&gt;&lt;P&gt;I found that the minimum timer is only 96 micro seconds even though I set the timing to 50 micro second. It's quite slow.&lt;/P&gt;&lt;P&gt;In my application, I want at least 10 micro seconds timer.&lt;/P&gt;&lt;P&gt;Anyone have the idea?&lt;/P&gt;</description>
      <pubDate>Fri, 04 Dec 2020 05:42:51 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/imx6ul-hrtimer-problem/m-p/1193709#M165983</guid>
      <dc:creator>wayneshih</dc:creator>
      <dc:date>2020-12-04T05:42:51Z</dc:date>
    </item>
    <item>
      <title>Re: imx6ul hrtimer problem</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/imx6ul-hrtimer-problem/m-p/1193744#M165985</link>
      <description>&lt;P&gt;Hi wayneshih&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;reason for that may be large software overheads as linux is running many tasks&lt;/P&gt;
&lt;P&gt;concurrently. One can try to achieve better resolution with M4 SDK (look at gpt_timer.c, epit.c)&lt;/P&gt;
&lt;H5 class="design-res-title"&gt;&lt;A id="designResources_title6" href="https://www.nxp.com/webapp/Download?colCode=SDK2.2_iMX6UL_WIN&amp;amp;appType=license" data-dtmaction="Software &amp;amp; Tools tab: Developer Resources - Download Link click" data-dtmsubaction="SDK2.2_iMX6UL_WIN" target="_blank"&gt;SDK2.2_iMX6UL_WIN&lt;/A&gt;&lt;/H5&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best regards&lt;BR /&gt;igor&lt;/P&gt;</description>
      <pubDate>Fri, 04 Dec 2020 06:53:27 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/imx6ul-hrtimer-problem/m-p/1193744#M165985</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2020-12-04T06:53:27Z</dc:date>
    </item>
  </channel>
</rss>

