<?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のトピックRe: GPIO Wake up</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/GPIO-Wake-up/m-p/1831393#M221483</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/224286"&gt;@cduarte0306&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Could you please try to add tou your dts:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;interrupt-parent = &amp;lt;&amp;amp;gpio1&amp;gt;; 
interrupts = &amp;lt;6 IRQ_TYPE_EDGE_RISING&amp;gt;;&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;And let me know if that works.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best regards.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Salas.&lt;/P&gt;</description>
    <pubDate>Tue, 19 Mar 2024 19:24:28 GMT</pubDate>
    <dc:creator>Manuel_Salas</dc:creator>
    <dc:date>2024-03-19T19:24:28Z</dc:date>
    <item>
      <title>GPIO Wake up</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/GPIO-Wake-up/m-p/1829693#M221367</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;I am working on a device based on an IMX8MP which uses a Trigger pin as a wake up pin when the unit is asleep, and a regular pin from user space when awake.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The pin is bound by the following functions&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;int ret = 0;
    ret = system("echo gpio-keys &amp;gt; /sys/bus/platform/drivers/gpio-keys/unbind");
    if (ret != 0) {
        std::cerr &amp;lt;&amp;lt; "Failed to set direction for GPIO pin 6." &amp;lt;&amp;lt; std::endl;
        return 0;
    }

    ret = system("echo 6 &amp;gt; /sys/class/gpio/export");
    if (ret != 0) {
        std::cerr &amp;lt;&amp;lt; "Failed to set direction for GPIO pin 6." &amp;lt;&amp;lt; std::endl;
        return 0;
    }

    ret = system("echo out &amp;gt; /sys/class/gpio/gpio6/direction");
    if (ret != 0) {
        std::cerr &amp;lt;&amp;lt; "Failed to set direction for GPIO pin 6." &amp;lt;&amp;lt; std::endl;
        return 0;
    }

    ret = system("echo 1 &amp;gt; /sys/class/gpio/gpio6/value");
    if (ret != 0) {
        std::cerr &amp;lt;&amp;lt; "Failed to set direction for GPIO pin 6." &amp;lt;&amp;lt; std::endl;
        return 0;
    }

    return 1;&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My problem is, despite my DTS settings, the pin is still waking up from both edges (falling and rising), when it should only wake up from a rising edge.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Would anyone happen to know why?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;gpio-keys {
		compatible = "gpio-keys";
		pinctrl-0 = &amp;lt;&amp;amp;pinctrl_gpio_keys&amp;gt;;
		pinctrl-names = "default";

		trigger_in {
			label = "TRIGGER IN_PIN";
			gpios = &amp;lt;&amp;amp;gpio1 6 GPIO_ACTIVE_LOW&amp;gt;;
			linux,code = &amp;lt;KEY_WAKEUP&amp;gt;;
			debounce-interval = &amp;lt;10&amp;gt;;
			wakeup-source;
		};
	};


pinctrl_gpio_keys: gpiokeysgrp {
		fsl,pins = &amp;lt;
			MX8MP_IOMUXC_GPIO1_IO06__GPIO1_IO06	0x19
		&amp;gt;;
	};&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am using kernel version 6.1&lt;/P&gt;</description>
      <pubDate>Sat, 16 Mar 2024 05:05:42 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/GPIO-Wake-up/m-p/1829693#M221367</guid>
      <dc:creator>cduarte0306</dc:creator>
      <dc:date>2024-03-16T05:05:42Z</dc:date>
    </item>
    <item>
      <title>Re: GPIO Wake up</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/GPIO-Wake-up/m-p/1831393#M221483</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/224286"&gt;@cduarte0306&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Could you please try to add tou your dts:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;interrupt-parent = &amp;lt;&amp;amp;gpio1&amp;gt;; 
interrupts = &amp;lt;6 IRQ_TYPE_EDGE_RISING&amp;gt;;&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;And let me know if that works.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best regards.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Salas.&lt;/P&gt;</description>
      <pubDate>Tue, 19 Mar 2024 19:24:28 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/GPIO-Wake-up/m-p/1831393#M221483</guid>
      <dc:creator>Manuel_Salas</dc:creator>
      <dc:date>2024-03-19T19:24:28Z</dc:date>
    </item>
    <item>
      <title>Re: GPIO Wake up</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/GPIO-Wake-up/m-p/1831404#M221485</link>
      <description>&lt;P&gt;Would this be under the gpio-keys node?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Carlos&lt;/P&gt;</description>
      <pubDate>Tue, 19 Mar 2024 19:43:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/GPIO-Wake-up/m-p/1831404#M221485</guid>
      <dc:creator>cduarte0306</dc:creator>
      <dc:date>2024-03-19T19:43:30Z</dc:date>
    </item>
    <item>
      <title>Re: GPIO Wake up</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/GPIO-Wake-up/m-p/1831411#M221487</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;gpio-keys {
		compatible = "gpio-keys";
		pinctrl-0 = &amp;lt;&amp;amp;pinctrl_gpio_keys&amp;gt;;
		pinctrl-names = "default";

		trigger_in {
			label = "TRIGGER IN_PIN";
			gpios = &amp;lt;&amp;amp;gpio1 6 GPIO_ACTIVE_LOW&amp;gt;;
			linux,code = &amp;lt;KEY_WAKEUP&amp;gt;;
			debounce-interval = &amp;lt;10&amp;gt;;
                    interrupt-parent = &amp;lt;&amp;amp;gpio1&amp;gt;; 
                    interrupts = &amp;lt;6 IRQ_TYPE_EDGE_RISING&amp;gt;;
			wakeup-source;
		};
	};&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please try and let me know.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best regards.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Salas.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 19 Mar 2024 19:51:03 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/GPIO-Wake-up/m-p/1831411#M221487</guid>
      <dc:creator>Manuel_Salas</dc:creator>
      <dc:date>2024-03-19T19:51:03Z</dc:date>
    </item>
    <item>
      <title>Re: GPIO Wake up</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/GPIO-Wake-up/m-p/1832148#M221532</link>
      <description>&lt;P&gt;I tried this and it works when I click the button. I should've mentioned that the pin's end of the connection is inverted form the button click by an optocoupler, meaning that the unit should wake up when the button is released ( a rising edge at the optocoupler, a falling edge at the SoM's Pin)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I tried changing it to&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;gpio-keys {
		compatible = "gpio-keys";
		pinctrl-0 = &amp;lt;&amp;amp;pinctrl_gpio_keys&amp;gt;;
		pinctrl-names = "default";

		trigger_in {
			label = "TRIGGER IN_PIN";
			gpios = &amp;lt;&amp;amp;gpio1 6 GPIO_ACTIVE_LOW&amp;gt;;
			linux,code = &amp;lt;KEY_WAKEUP&amp;gt;;
			debounce-interval = &amp;lt;10&amp;gt;;
                    interrupt-parent = &amp;lt;&amp;amp;gpio1&amp;gt;; 
                    interrupts = &amp;lt;6 IRQ_TYPE_EDGE_FALLING&amp;gt;;
			wakeup-source;
		};
	};&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;And it was waking on both edges once more&lt;/P&gt;</description>
      <pubDate>Wed, 20 Mar 2024 15:26:29 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/GPIO-Wake-up/m-p/1832148#M221532</guid>
      <dc:creator>cduarte0306</dc:creator>
      <dc:date>2024-03-20T15:26:29Z</dc:date>
    </item>
    <item>
      <title>Re: GPIO Wake up</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/GPIO-Wake-up/m-p/1841549#M222184</link>
      <description>&lt;P&gt;I should let you know this solution is not working for some reason.&lt;/P&gt;</description>
      <pubDate>Sat, 06 Apr 2024 02:30:02 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/GPIO-Wake-up/m-p/1841549#M222184</guid>
      <dc:creator>cduarte0306</dc:creator>
      <dc:date>2024-04-06T02:30:02Z</dc:date>
    </item>
  </channel>
</rss>

