<?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 Accessing GPIO in imx6 in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Accessing-GPIO-in-imx6/m-p/676649#M104365</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I want to change value of &lt;STRONG&gt;GPIO1_25&amp;nbsp; (phy_reset)&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;but following error comes&lt;/P&gt;&lt;BLOCKQUOTE class="jive_macro_quote jive-quote jive_text_macro"&gt;&lt;P&gt;&lt;STRONG&gt;root@var-som-mx6:~# echo 25 &amp;gt; /sys/class/gpio/export&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;-sh: echo: write error: Device or resource busy&lt;/STRONG&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;What should i do to change the value of phy reset pin&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Following is current status&lt;/P&gt;&lt;BLOCKQUOTE class="jive_macro_quote jive-quote jive_text_macro"&gt;&lt;P&gt;root@var-som-mx6:~# &lt;STRONG&gt;cat /sys/kernel/debug/gpio&lt;/STRONG&gt;&lt;BR /&gt;GPIOs 0-31, platform/209c000.gpio, 209c000.gpio:&lt;BR /&gt; gpio-6 (cd ) in lo &lt;BR /&gt; &lt;EM&gt;&lt;STRONG&gt;gpio-25 (phy-reset ) out lo&lt;/STRONG&gt; &lt;/EM&gt;&lt;BR /&gt; gpio-28 (usb_h1_vbus ) out lo&lt;/P&gt;&lt;P&gt;GPIOs 32-63, platform/20a0000.gpio, 20a0000.gpio:&lt;/P&gt;&lt;P&gt;GPIOs 64-95, platform/20a4000.gpio, 20a4000.gpio:&lt;/P&gt;&lt;P&gt;GPIOs 96-127, platform/20a8000.gpio, 20a8000.gpio:&lt;BR /&gt; gpio-101 (tlv320aic3x reset ) out lo &lt;BR /&gt; gpio-111 (usb_otg_vbus ) out lo &lt;BR /&gt; gpio-121 (Menu ) in hi &lt;BR /&gt; gpio-122 (Back ) in hi&lt;/P&gt;&lt;P&gt;GPIOs 128-159, platform/20ac000.gpio, 20ac000.gpio:&lt;BR /&gt; gpio-139 (Home ) in hi&lt;/P&gt;&lt;P&gt;GPIOs 160-191, platform/20b0000.gpio, 20b0000.gpio:&lt;BR /&gt; gpio-178 (sysfs ) out lo&lt;/P&gt;&lt;P&gt;GPIOs 192-223, platform/20b4000.gpio, 20b4000.gpio:&lt;BR /&gt; gpio-200 (wlan-en-regulator ) out lo&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks and Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 11 May 2017 13:13:00 GMT</pubDate>
    <dc:creator>sameerarvikar</dc:creator>
    <dc:date>2017-05-11T13:13:00Z</dc:date>
    <item>
      <title>Accessing GPIO in imx6</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Accessing-GPIO-in-imx6/m-p/676649#M104365</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I want to change value of &lt;STRONG&gt;GPIO1_25&amp;nbsp; (phy_reset)&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;but following error comes&lt;/P&gt;&lt;BLOCKQUOTE class="jive_macro_quote jive-quote jive_text_macro"&gt;&lt;P&gt;&lt;STRONG&gt;root@var-som-mx6:~# echo 25 &amp;gt; /sys/class/gpio/export&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;-sh: echo: write error: Device or resource busy&lt;/STRONG&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;What should i do to change the value of phy reset pin&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Following is current status&lt;/P&gt;&lt;BLOCKQUOTE class="jive_macro_quote jive-quote jive_text_macro"&gt;&lt;P&gt;root@var-som-mx6:~# &lt;STRONG&gt;cat /sys/kernel/debug/gpio&lt;/STRONG&gt;&lt;BR /&gt;GPIOs 0-31, platform/209c000.gpio, 209c000.gpio:&lt;BR /&gt; gpio-6 (cd ) in lo &lt;BR /&gt; &lt;EM&gt;&lt;STRONG&gt;gpio-25 (phy-reset ) out lo&lt;/STRONG&gt; &lt;/EM&gt;&lt;BR /&gt; gpio-28 (usb_h1_vbus ) out lo&lt;/P&gt;&lt;P&gt;GPIOs 32-63, platform/20a0000.gpio, 20a0000.gpio:&lt;/P&gt;&lt;P&gt;GPIOs 64-95, platform/20a4000.gpio, 20a4000.gpio:&lt;/P&gt;&lt;P&gt;GPIOs 96-127, platform/20a8000.gpio, 20a8000.gpio:&lt;BR /&gt; gpio-101 (tlv320aic3x reset ) out lo &lt;BR /&gt; gpio-111 (usb_otg_vbus ) out lo &lt;BR /&gt; gpio-121 (Menu ) in hi &lt;BR /&gt; gpio-122 (Back ) in hi&lt;/P&gt;&lt;P&gt;GPIOs 128-159, platform/20ac000.gpio, 20ac000.gpio:&lt;BR /&gt; gpio-139 (Home ) in hi&lt;/P&gt;&lt;P&gt;GPIOs 160-191, platform/20b0000.gpio, 20b0000.gpio:&lt;BR /&gt; gpio-178 (sysfs ) out lo&lt;/P&gt;&lt;P&gt;GPIOs 192-223, platform/20b4000.gpio, 20b4000.gpio:&lt;BR /&gt; gpio-200 (wlan-en-regulator ) out lo&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks and Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 May 2017 13:13:00 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Accessing-GPIO-in-imx6/m-p/676649#M104365</guid>
      <dc:creator>sameerarvikar</dc:creator>
      <dc:date>2017-05-11T13:13:00Z</dc:date>
    </item>
    <item>
      <title>Re: Accessing GPIO in imx6</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Accessing-GPIO-in-imx6/m-p/676650#M104366</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi sameerarvikar,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;most likely the gpio is being used by another driver, in this case no other driver can access to the gpio. You can look into the devi tree file (.dts) and look which module is using this pin. Then you can comment or delete the line where the pin is being initialized within such module and after rebuilding the dtb file you may be able to use it as a gpio.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Best regards,&lt;BR /&gt;TIC&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&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>Mon, 15 May 2017 20:30:31 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Accessing-GPIO-in-imx6/m-p/676650#M104366</guid>
      <dc:creator>Carlos_Musich</dc:creator>
      <dc:date>2017-05-15T20:30:31Z</dc:date>
    </item>
  </channel>
</rss>

