<?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>i.MX ProcessorsのトピックI2C2 doesn't work</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/I2C2-doesn-t-work/m-p/765780#M118960</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I have trouble to enable I2C2 to work on the iMX6 Sabre EVB under Linux and communicate with touch controller. I can’t see any SDA/SCL signals activity from iMX6 on oscilloscope. Communication is doing by i2c_transfer() function.&lt;/P&gt;&lt;P&gt;Already tried change status from “disabled”&amp;nbsp; for i2c2 node into device tree &amp;nbsp;(with no effect).&lt;/P&gt;&lt;P&gt;Is I2C number 2 is turned on by defaults?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;HW: MCIMX6QP-SDB + MIPI DSI panel&lt;/P&gt;&lt;P&gt;SW: Yocto and Linux kernel v4.9&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;UPDATE:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Also found some unknown definitions in device tree for I2C2 pinmux.&lt;/P&gt;&lt;P&gt;It’s only I2C2 specific. I2C1 and I2C3 haven’t this group. I can’t explain what It does mean.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;pinctrl-1 = &amp;lt;&amp;amp;pinctrl_i2c2_gpio&amp;gt;;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;pinctrl_i2c2_gpio: i2c2_gpio_grp {&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;fsl,pins = &amp;lt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;MX6QDL_PAD_KEY_COL3__GPIO4_IO12&amp;gt;&amp;lt;------&amp;gt;0x1b0b0&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;MX6QDL_PAD_KEY_ROW3__GPIO4_IO13&amp;gt;&amp;lt;------&amp;gt;0x1b0b0&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&amp;gt;;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;};&lt;/P&gt;&lt;P&gt;How to explain?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 09 Jun 2018 19:19:15 GMT</pubDate>
    <dc:creator>alexeykuzmin</dc:creator>
    <dc:date>2018-06-09T19:19:15Z</dc:date>
    <item>
      <title>I2C2 doesn't work</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/I2C2-doesn-t-work/m-p/765780#M118960</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I have trouble to enable I2C2 to work on the iMX6 Sabre EVB under Linux and communicate with touch controller. I can’t see any SDA/SCL signals activity from iMX6 on oscilloscope. Communication is doing by i2c_transfer() function.&lt;/P&gt;&lt;P&gt;Already tried change status from “disabled”&amp;nbsp; for i2c2 node into device tree &amp;nbsp;(with no effect).&lt;/P&gt;&lt;P&gt;Is I2C number 2 is turned on by defaults?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;HW: MCIMX6QP-SDB + MIPI DSI panel&lt;/P&gt;&lt;P&gt;SW: Yocto and Linux kernel v4.9&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;UPDATE:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Also found some unknown definitions in device tree for I2C2 pinmux.&lt;/P&gt;&lt;P&gt;It’s only I2C2 specific. I2C1 and I2C3 haven’t this group. I can’t explain what It does mean.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;pinctrl-1 = &amp;lt;&amp;amp;pinctrl_i2c2_gpio&amp;gt;;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;pinctrl_i2c2_gpio: i2c2_gpio_grp {&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;fsl,pins = &amp;lt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;MX6QDL_PAD_KEY_COL3__GPIO4_IO12&amp;gt;&amp;lt;------&amp;gt;0x1b0b0&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;MX6QDL_PAD_KEY_ROW3__GPIO4_IO13&amp;gt;&amp;lt;------&amp;gt;0x1b0b0&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&amp;gt;;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;};&lt;/P&gt;&lt;P&gt;How to explain?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 09 Jun 2018 19:19:15 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/I2C2-doesn-t-work/m-p/765780#M118960</guid>
      <dc:creator>alexeykuzmin</dc:creator>
      <dc:date>2018-06-09T19:19:15Z</dc:date>
    </item>
    <item>
      <title>Re: I2C2 doesn't work</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/I2C2-doesn-t-work/m-p/765781#M118961</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Alexey&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;seems "pinctrl_i2c2_gpio: i2c2_gpio_grp " are used for emulation,&lt;/P&gt;&lt;P&gt;really they are configured as gpios. For comparison true i2c settings&lt;/P&gt;&lt;P&gt;have sion pad bit30 set&lt;/P&gt;&lt;P&gt;pinctrl_i2c3: i2c3grp {&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;fsl,pins = &amp;lt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;MX6QDL_PAD_GPIO_3__I2C3_SCL&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;0x4001b8b1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;may be useful to check linux/Documentation/devicetree/bindings/pinctrl/fsl,imx-pinctrl.txt&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;BR /&gt;igor&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 12 Jun 2018 00:43:23 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/I2C2-doesn-t-work/m-p/765781#M118961</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2018-06-12T00:43:23Z</dc:date>
    </item>
  </channel>
</rss>

