<?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のトピックiMX28 Linux Device Tree - Configure Pin for External Interrupt</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/iMX28-Linux-Device-Tree-Configure-Pin-for-External-Interrupt/m-p/267995#M28289</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Can anyone help me define a device tree node that configures a GPIO pin to generate an interrupt?&amp;nbsp; I have a device that asserts an IRQ and would like to handle it in the kernel.&amp;nbsp; I'm attempting to use MX28_PAD_GPMI_D04__GPIO_0_4 for the IRQ pin.&amp;nbsp; I'm also using a mainline 3.8.3 kernel.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Ryan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 15 Apr 2013 20:43:30 GMT</pubDate>
    <dc:creator>rabryn</dc:creator>
    <dc:date>2013-04-15T20:43:30Z</dc:date>
    <item>
      <title>iMX28 Linux Device Tree - Configure Pin for External Interrupt</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/iMX28-Linux-Device-Tree-Configure-Pin-for-External-Interrupt/m-p/267995#M28289</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Can anyone help me define a device tree node that configures a GPIO pin to generate an interrupt?&amp;nbsp; I have a device that asserts an IRQ and would like to handle it in the kernel.&amp;nbsp; I'm attempting to use MX28_PAD_GPMI_D04__GPIO_0_4 for the IRQ pin.&amp;nbsp; I'm also using a mainline 3.8.3 kernel.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Ryan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 15 Apr 2013 20:43:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/iMX28-Linux-Device-Tree-Configure-Pin-for-External-Interrupt/m-p/267995#M28289</guid>
      <dc:creator>rabryn</dc:creator>
      <dc:date>2013-04-15T20:43:30Z</dc:date>
    </item>
    <item>
      <title>Re: iMX28 Linux Device Tree - Configure Pin for External Interrupt</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/iMX28-Linux-Device-Tree-Configure-Pin-for-External-Interrupt/m-p/267996#M28290</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ryan,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I haven't tried it on mx28, but on mx5 we have an example for GPIO interrupt in imx51-babbage.dts:&lt;/P&gt;&lt;P&gt;&lt;A href="https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/tree/arch/arm/boot/dts/imx51-babbage.dts?id=refs/tags/v3.8.7" title="https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/tree/arch/arm/boot/dts/imx51-babbage.dts?id=refs/tags/v3.8.7"&gt;https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/tree/arch/arm/boot/dts/imx51-babbage.dts?id=refs/tags/v3.8.7&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please check the PMIC node, that has a GPIO that triggers an interrupt.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you still face issues, please post this question into the linux-arm-kernel&amp;nbsp; mailing list.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Fabio Estevam&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Apr 2013 16:03:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/iMX28-Linux-Device-Tree-Configure-Pin-for-External-Interrupt/m-p/267996#M28290</guid>
      <dc:creator>fabio_estevam</dc:creator>
      <dc:date>2013-04-16T16:03:30Z</dc:date>
    </item>
    <item>
      <title>Re: iMX28 Linux Device Tree - Configure Pin for External Interrupt</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/iMX28-Linux-Device-Tree-Configure-Pin-for-External-Interrupt/m-p/267997#M28291</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="color: #500050; font-family: arial, sans-serif; background-color: #ffffff;"&gt;Fabio,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #500050; font-family: arial, sans-serif; background-color: #ffffff;"&gt;Thanks for the response.&amp;nbsp; I've seen that in the imx51-babbage.dts file, but I'm still confused.&amp;nbsp; In the kernel source, under Documentation/devicetree/&lt;/SPAN&gt;&lt;SPAN style="color: #500050; font-family: arial, sans-serif; background-color: #ffffff;"&gt;bindings/gpio, I see the following in gpio-mxs.txt:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #500050; font-family: 'courier new', courier; background-color: #ffffff;"&gt;As the GPIO controller is embedded in the PIN controller and all the&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #500050; font-family: 'courier new', courier; background-color: #ffffff;"&gt;GPIO ports share the same IO space with PIN controller, the GPIO node&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #500050; font-family: 'courier new', courier; background-color: #ffffff;"&gt;will be represented as sub-nodes of MXS pinctrl node.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #500050; font-family: 'courier new', courier; background-color: #ffffff;"&gt;Required properties for GPIO node:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #500050; font-family: 'courier new', courier; background-color: #ffffff;"&gt;- compatible : Should be "fsl,&amp;lt;soc&amp;gt;-gpio".&amp;nbsp; The supported SoCs include&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #500050; font-family: 'courier new', courier; background-color: #ffffff;"&gt;&amp;nbsp; imx23 and imx28.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #500050; font-family: 'courier new', courier; background-color: #ffffff;"&gt;- interrupts : Should be the port interrupt shared by all 32 pins.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #500050; font-family: 'courier new', courier; background-color: #ffffff;"&gt;- gpio-controller : Marks the device node as a gpio controller.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #500050; font-family: 'courier new', courier; background-color: #ffffff;"&gt;- #gpio-cells : Should be two.&amp;nbsp; The first cell is the pin number and&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #500050; font-family: 'courier new', courier; background-color: #ffffff;"&gt;&amp;nbsp; the second cell is used to specify the gpio polarity:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #500050; font-family: 'courier new', courier; background-color: #ffffff;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0 = active high&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #500050; font-family: 'courier new', courier; background-color: #ffffff;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1 = active low&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #500050; font-family: 'courier new', courier; background-color: #ffffff;"&gt;- interrupt-controller: Marks the device node as an interrupt controller.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #500050; font-family: 'courier new', courier; background-color: #ffffff;"&gt;- #interrupt-cells : Should be 2.&amp;nbsp; The first cell is the GPIO number.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #500050; font-family: 'courier new', courier; background-color: #ffffff;"&gt;&amp;nbsp; The second cell bits[3:0] is used to specify trigger type and level flags:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #500050; font-family: 'courier new', courier; background-color: #ffffff;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1 = low-to-high edge triggered.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #500050; font-family: 'courier new', courier; background-color: #ffffff;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 2 = high-to-low edge triggered.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #500050; font-family: 'courier new', courier; background-color: #ffffff;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 4 = active high level-sensitive.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #500050; font-family: 'courier new', courier; background-color: #ffffff;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 8 = active low level-sensitive.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #500050; font-family: 'courier new', courier; background-color: #ffffff;"&gt;Note: Each GPIO port should have an alias correctly numbered in "aliases"&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #500050; font-family: 'courier new', courier; background-color: #ffffff;"&gt;node.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #500050; font-family: arial, sans-serif; background-color: #ffffff;"&gt;Then in the imx28.dtsi I see the definitions of the aliases and GPIO ports, for example...&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #500050; font-family: 'courier new', courier; background-color: #ffffff;"&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;&amp;nbsp;&amp;nbsp;&amp;nbsp; gpio0: gpio@0 {&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #500050; font-family: 'courier new', courier; background-color: #ffffff;"&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;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; compatible = "fsl,imx28-gpio", "fsl,mxs-gpio";&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #500050; font-family: 'courier new', courier; background-color: #ffffff;"&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;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; interrupts = &amp;lt;127&amp;gt;;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #500050; font-family: 'courier new', courier; background-color: #ffffff;"&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;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; gpio-controller;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #500050; font-family: 'courier new', courier; background-color: #ffffff;"&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;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; #gpio-cells = &amp;lt;2&amp;gt;;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #500050; font-family: 'courier new', courier; background-color: #ffffff;"&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;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; interrupt-controller;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #500050; font-family: 'courier new', courier; background-color: #ffffff;"&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;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; #interrupt-cells = &amp;lt;2&amp;gt;;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #500050; font-family: 'courier new', courier; background-color: #ffffff;"&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;&amp;nbsp;&amp;nbsp;&amp;nbsp; };&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #500050; font-family: arial, sans-serif; background-color: #ffffff;"&gt;I don't see how I should define a node in the imx28-evk.dts that defines a GPIO that is an IRQ.&amp;nbsp; The "interrupts" in the dtsi file, 127 in the example above, refer to the IRQ source in the ICOLL.&amp;nbsp; Where are the definitions of the interrupt-cells and gpio-cells at that are described in the gpio-mxs.txt documentation?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #500050; font-family: arial, sans-serif; background-color: #ffffff;"&gt;Thanks,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #500050; font-family: arial, sans-serif; background-color: #ffffff;"&gt;Ryan&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="mce_paste_marker"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Apr 2013 16:21:12 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/iMX28-Linux-Device-Tree-Configure-Pin-for-External-Interrupt/m-p/267997#M28291</guid>
      <dc:creator>rabryn</dc:creator>
      <dc:date>2013-04-16T16:21:12Z</dc:date>
    </item>
    <item>
      <title>Re: iMX28 Linux Device Tree - Configure Pin for External Interrupt</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/iMX28-Linux-Device-Tree-Configure-Pin-for-External-Interrupt/m-p/267998#M28292</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am not sure. Please start a thread in linux-arm-kernel mailing list.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Fabio Estevam&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Apr 2013 16:23:25 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/iMX28-Linux-Device-Tree-Configure-Pin-for-External-Interrupt/m-p/267998#M28292</guid>
      <dc:creator>fabio_estevam</dc:creator>
      <dc:date>2013-04-16T16:23:25Z</dc:date>
    </item>
  </channel>
</rss>

