Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

This application note shows how to control the i.MX RT1170 GPIOs from the user level using the standard Linux GPIOLIB interface.

Changes to the Kernel Configuration

The generic GPIO interface is controlled by the CONFIG_GPIOLIB kernel option enabled by default in the rootfs project. Most of the i.MX RT1170 GPIO pins can be used in different multiplexed I/O roles (for instance, some GPIO pins can be also configured as an SPI interface, etc). Depending on the requirements of your application, you need to configure the pins that you want to use as GPIO for the GPIO role and other pins for an alternative I/O function.

The device driver for i.MX family GPIO controller is enabled in the kernel config. The gpio-leds and gpio-keys drivers will be enabled and configured in the DTS file, in order to support the USER_LED and USER_BUTTON of the IMXRT1170 EVK board.

  1. Verify that the USER LED and USER BUTTON interfaces are functional via the standard gpio-leds and gpio-keys interfaces:

    1. Use the following command to turn on the USER LED1:

      # echo 1 > /sys/class/leds/user-led1/brightness

    2. Use the following command to turn off the USER LED1:

      # echo 0 > /sys/class/leds/user-led1/brightness

    3. Use the following command to turn on the USER LED2:

      # echo 1 > /sys/class/leds/user-led2/brightness

    4. Use the following command to turn off the USER LED2:

      # echo 0 > /sys/class/leds/user-led2/brightness

  2. From the Linux shell, start the evtest utility. Then press the USER BUTTON and make sure the evtest has reported the events correctly:

    / # evtest /dev/input/event0
Event: time 927.000134, type EV_KEY, code KEY_A, value 1
Event: time 927.000134, type EV_SYN, code SYN_REPORT, value 0
Event: time 927.240114, type EV_KEY, code KEY_A, value 0
Event: time 927.240114, type EV_SYN, code SYN_REPORT, value 0
0

  3. In order to test raw GPIO functions, disable definition of the USER BUTTON in the kernel DTS file, then rebuild and reinstall the project:

    diff --git a/rootfs/rootfs.dts.IMXRT102X_NXPEVK b/rootfs/rootfs.dts.
IMXRT102X_NXPEVK
index ab152d38..6fee00b8 100644
--- a/rootfs/rootfs.dts.IMXRT102X_NXPEVK
+++ b/rootfs/rootfs.dts.IMXRT102X_NXPEVK
@@ -235,11 +235,13 @@
                compatible = "gpio-keys";
                pinctrl-names = "default";
                pinctrl-0 = <&pinctrl_keys>;
+#if 0
                user-button {
                        label = "user-button";
                        gpios = <&gpio13 0 GPIO_ACTIVE_LOW>;
                        linux,code = <KEY_A>;
                };
+#endif                                                                                                                                                                                                                                                                           
                                                                                                                                                                                                                                                            
 };

  4. Each GPIO is assigned a unique integer GPIO number within the GPIO chip range of 0 to 416 by Linux. The i.MX RT1170 supports 13 GPIO blocks of 32 pieces. To calculate that number for a specific GPIO, use the following formula
    gpio_idX(GPIOX_IOY) = (X - 1) * 32 + Y
    where an X value is a GPIO number and Y is a GPIO pin number.
    For example: gpio number for GPIO13.0 will be (13 -- 1) * 32 + 0 = 384.

  5. Export GPIO5_00 and configure it as an input:

    / # echo 384 > /sys/class/gpio/export
/ # echo in > /sys/class/gpio/gpio384/direction

  6. Make sure the value of GPIO13_00 is 1 when the USER BUTTON is untouched (due to the internal PULL-UP being enabled):

    / # cat /sys/class/gpio/gpio384/value
1
/ #

  7. Press and hold the USER BUTTON and make sure the GPIO13_00 value has changed to 0:

    / # cat /sys/class/gpio/gpio384/value
0

Alternative Ways to Access GPIO

In Linux, you may access GPIOs using different approaches, not only the ones described in this application note above. Here are some external links that might be useful if you decide to try an alternative approach.

The following article describes accessing GPIOs from the kernel context:
https://lwn.net/Articles/532714/

To work with GPIOs from the user space, there are the following possibilities:

  1. Using the GPIOLIB interface (described in this application note):
    https://www.kernel.org/doc/Documentation/gpio/sysfs.txt

  2. Using the drivers of the Linux LED/Input subsystems:
    https://www.kernel.org/doc/Documentation/leds/leds-class.txt
    https://www.kernel.org/doc/Documentation/input/input.txt
    These drivers allow to use different GPIO-related mechanisms already implemented in Linux. For example, you may simply force a LED connected to GPIO output to blink with the specified frequency, or simply force input subsystem to generate a some-button-pressed event on changing GPIO input.

  • No labels