<?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 Re: What does a blocking peripheral driver actually block? in Kinetis Software Development Kit</title>
    <link>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/What-does-a-blocking-peripheral-driver-actually-block/m-p/505423#M4991</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, Althaf,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As far as I know, most peripheral drivers of MQX do not use blocking mechanism, in other words, the read()/write() function return immediately without blocking. If the peripheral drivers use blocking mechanism, it only blocks the corresponding MQX task that calls it.&lt;/P&gt;&lt;P&gt;Hope it can help you.&lt;/P&gt;&lt;P&gt;BR&lt;/P&gt;&lt;P&gt;Xiangjun Rong&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 16 Feb 2016 07:25:01 GMT</pubDate>
    <dc:creator>xiangjun_rong</dc:creator>
    <dc:date>2016-02-16T07:25:01Z</dc:date>
    <item>
      <title>What does a blocking peripheral driver actually block?</title>
      <link>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/What-does-a-blocking-peripheral-driver-actually-block/m-p/505422#M4990</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm trying to optimize the timing in my application that uses the K64F12, KDS3.0, KSDK1.3, and MQX.&amp;nbsp; I wonder if any one know if a blocking peripheral driver only blocks the corresponding MQX task that calls it, or does it completely block MQX from continuing on with other tasks?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 12 Feb 2016 21:49:58 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/What-does-a-blocking-peripheral-driver-actually-block/m-p/505422#M4990</guid>
      <dc:creator>althafismail</dc:creator>
      <dc:date>2016-02-12T21:49:58Z</dc:date>
    </item>
    <item>
      <title>Re: What does a blocking peripheral driver actually block?</title>
      <link>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/What-does-a-blocking-peripheral-driver-actually-block/m-p/505423#M4991</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, Althaf,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As far as I know, most peripheral drivers of MQX do not use blocking mechanism, in other words, the read()/write() function return immediately without blocking. If the peripheral drivers use blocking mechanism, it only blocks the corresponding MQX task that calls it.&lt;/P&gt;&lt;P&gt;Hope it can help you.&lt;/P&gt;&lt;P&gt;BR&lt;/P&gt;&lt;P&gt;Xiangjun Rong&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Feb 2016 07:25:01 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/What-does-a-blocking-peripheral-driver-actually-block/m-p/505423#M4991</guid>
      <dc:creator>xiangjun_rong</dc:creator>
      <dc:date>2016-02-16T07:25:01Z</dc:date>
    </item>
  </channel>
</rss>

