<?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:  I.mx28 9 bit data UART linux drivers in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/I-mx28-9-bit-data-UART-linux-drivers/m-p/563685#M87133</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Desmond,&lt;/P&gt;&lt;P&gt;i think your thoughts should be okay. I think the tricky part is to detect the parity errors with termios. Maybe the flag PARMRK should do the trick.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 04 Aug 2016 16:40:36 GMT</pubDate>
    <dc:creator>lategoodbye</dc:creator>
    <dc:date>2016-08-04T16:40:36Z</dc:date>
    <item>
      <title>I.mx28 9 bit data UART linux drivers</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/I-mx28-9-bit-data-UART-linux-drivers/m-p/563681#M87129</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, &lt;/P&gt;&lt;P&gt;Has anyone implemented a 9 bit data UART driver under linux for the I.mx28. I have been reviewing the "MCIMX28RM" document and as far as I see it's not possible to read the 9bit from the UART register since the hardware just tells you the status of the parity bit.&lt;/P&gt;&lt;P&gt;Does anyone have any idea how I could do this. I need to know what the 9bit is since I am trying to interface the I.mx28 with a UART that uses 9bit data for UART&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Aug 2016 20:53:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/I-mx28-9-bit-data-UART-linux-drivers/m-p/563681#M87129</guid>
      <dc:creator>desmondcorreia</dc:creator>
      <dc:date>2016-08-02T20:53:14Z</dc:date>
    </item>
    <item>
      <title>Re:  I.mx28 9 bit data UART linux drivers</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/I-mx28-9-bit-data-UART-linux-drivers/m-p/563682#M87130</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Desmond&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;you are right i.MX28 uart hardware does not support 9 data bits.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;P&gt;igor&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 03 Aug 2016 06:34:20 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/I-mx28-9-bit-data-UART-linux-drivers/m-p/563682#M87130</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2016-08-03T06:34:20Z</dc:date>
    </item>
    <item>
      <title>Re:  I.mx28 9 bit data UART linux drivers</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/I-mx28-9-bit-data-UART-linux-drivers/m-p/563683#M87131</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Desmond,&lt;/P&gt;&lt;P&gt;in case you don't need 9 bit + parity it's possible to emulate bit 9 with parity (like here: &lt;A href="https://viereck.ch/linux-mark-space-parity/" title="https://viereck.ch/linux-mark-space-parity/"&gt;https://viereck.ch/linux-mark-space-parity/&lt;/A&gt; ).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Based on this similiar patch: &lt;A href="https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=bb70002cb7430252c6c8e3b19ad66957f253e667" title="https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=bb70002cb7430252c6c8e3b19ad66957f253e667"&gt;https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=bb70002cb7430252c6c8e3b19ad66957f253e667&lt;/A&gt; &lt;/P&gt;&lt;P&gt;i attached one for mxs-auart from Mainline Linux 4.5. I only compile tested this patch.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 03 Aug 2016 20:42:55 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/I-mx28-9-bit-data-UART-linux-drivers/m-p/563683#M87131</guid>
      <dc:creator>lategoodbye</dc:creator>
      <dc:date>2016-08-03T20:42:55Z</dc:date>
    </item>
    <item>
      <title>Re:  I.mx28 9 bit data UART linux drivers</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/I-mx28-9-bit-data-UART-linux-drivers/m-p/563684#M87132</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Stefan,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for response. I don't want to write 9bit data I need to read it. I came up with a scenario to derive the 9th bit. See below and give me your thoughts.&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Imx28 is setup to use even parity checking&lt;/LI&gt;&lt;LI&gt;We calculate the parity error on 8 bits using even parity checking and always using the 9th bit as 0&lt;/LI&gt;&lt;LI&gt;We take our parity error flag XOR with imx28 parity error flag&lt;/LI&gt;&lt;LI&gt;The result is the 9th bit&lt;/LI&gt;&lt;/OL&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 03 Aug 2016 21:00:45 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/I-mx28-9-bit-data-UART-linux-drivers/m-p/563684#M87132</guid>
      <dc:creator>desmondcorreia</dc:creator>
      <dc:date>2016-08-03T21:00:45Z</dc:date>
    </item>
    <item>
      <title>Re:  I.mx28 9 bit data UART linux drivers</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/I-mx28-9-bit-data-UART-linux-drivers/m-p/563685#M87133</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Desmond,&lt;/P&gt;&lt;P&gt;i think your thoughts should be okay. I think the tricky part is to detect the parity errors with termios. Maybe the flag PARMRK should do the trick.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Aug 2016 16:40:36 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/I-mx28-9-bit-data-UART-linux-drivers/m-p/563685#M87133</guid>
      <dc:creator>lategoodbye</dc:creator>
      <dc:date>2016-08-04T16:40:36Z</dc:date>
    </item>
  </channel>
</rss>

