MX8M GPIO: Difference between revisions

From Variscite Wiki
No edit summary
Line 28: Line 28:
  gpio-114 (                    |Up                  ) in  hi IRQ
  gpio-114 (                    |Up                  ) in  hi IRQ
</pre>
</pre>
|
| {{#ifeq: {{#var:HARDWARE_NAME}} | DART-MX8M-MINI |
<pre>
<pre>
# cat /sys/kernel/debug/gpio  
# cat /sys/kernel/debug/gpio  
Line 59: Line 59:
  gpio-156 (                    |ov5640_mipi_reset  ) out hi
  gpio-156 (                    |ov5640_mipi_reset  ) out hi
</pre>
</pre>
}}
| {{#ifeq: {{#var:HARDWARE_NAME}} | VAR-SOM-MX8M-NANO |
<pre>
gpiochip0: GPIOs 0-31, parent: platform/30200000.gpio, 30200000.gpio:
gpio-0  (                    |spi_imx            ) out hi   
gpio-9  (                    |phy-reset          ) out hi   
gpio-10  (                    |connect            ) in  hi IRQ
gpio-13  (                    |ov5640_mipi_reset  ) out hi   
gpio-14  (                    |spi_imx            ) in  lo   
 
gpiochip1: GPIOs 32-63, parent: platform/30210000.gpio, 30210000.gpio:
gpio-38  (                    |sysfs              ) out hi   
gpio-39  (                    |sysfs              ) out hi   
gpio-41  (                    |eth_phy_pwr        ) out hi   
gpio-42  (                    |sysfs              ) out hi   
gpio-43  (                    |enable              ) out hi   
gpio-44  (                    |cd                  ) in  lo IRQ
gpio-51  (                    |VSD_3V3            ) out hi   
gpio-52  (                    |sysfs              ) out hi   
 
gpiochip2: GPIOs 64-95, parent: platform/30220000.gpio, 30220000.gpio:
 
gpiochip3: GPIOs 96-127, parent: platform/30230000.gpio, 30230000.gpio:
 
gpiochip4: GPIOs 128-159, parent: platform/30240000.gpio, 30240000.gpio:
gpio-133 (                    |sysfs              ) out lo   
gpio-140 (                    |ov5640_mipi_pwdn    ) out lo   
 
gpiochip6: GPIOs 502-503, parent: spi/spi0.1, spi0.1, can sleep:
 
gpiochip5: GPIOs 504-511, parent: i2c/1-0020, pca9534, can sleep:
gpio-504 (                    |Heartbeat          ) out lo   
gpio-505 (                    |Back                ) in  hi IRQ
gpio-506 (                    |Home                ) in  hi IRQ
gpio-507 (                    |Menu                ) in  hi IRQ
gpio-508 (                    |usb3_sel            ) out hi   
gpio-509 (                    |enet_rst            ) out lo   
gpio-510 (                    |som_vsel            ) out lo   
gpio-511 (                    |enet_sel            ) out lo   
</pre>
|}} }} }}


Each GPIO is defined as in or out and the state is shown as lo or hi.<br>
Each GPIO is defined as in or out and the state is shown as lo or hi.<br>
Line 209: Line 248:
#define MX8MQ_IOMUXC_SAI1_RXD0_SIM_M_HADDR17                                0x164 0x3CC 0x000 0x7 0x0
#define MX8MQ_IOMUXC_SAI1_RXD0_SIM_M_HADDR17                                0x164 0x3CC 0x000 0x7 0x0
</pre>
</pre>
|
|{{#ifeq: {{#var:HARDWARE_NAME}} | DART-MX8MM |
In the directory {{#ifeq: {{#var:ANDROID_NAME}} | Pie |{{#var:BUILD_FOLDER}}/{{#var:BUILD_FOLDER_ANDROID}}/variscite/kernel_imx/}}include/dt-bindings/pinctrl/ of the Linux kernel source you will find the pin functions definition files.<br>
In the directory {{#ifeq: {{#var:ANDROID_NAME}} | Pie |{{#var:BUILD_FOLDER}}/{{#var:BUILD_FOLDER_ANDROID}}/variscite/kernel_imx/}}include/dt-bindings/pinctrl/ of the Linux kernel source you will find the pin functions definition files.<br>
The relevant file is pins-imx8mm.h.<br>
The relevant file is pins-imx8mm.h.<br>
Line 222: Line 261:
#define MX8MM_IOMUXC_SAI1_RXD0_SIM_M_HADDR17                                0x164 0x3CC 0x000 0x7 0x0
#define MX8MM_IOMUXC_SAI1_RXD0_SIM_M_HADDR17                                0x164 0x3CC 0x000 0x7 0x0
</pre>
</pre>
}}
|{{#ifeq: {{#var:HARDWARE_NAME}} | VAR-SOM-MX8M-NANO |
Adding only the one with the GPIO4_IO2 suffix (function) to your dts file will let you use the pin as GPIO.
In the directory {{#ifeq: {{#var:ANDROID_NAME}} | Pie |{{#var:BUILD_FOLDER}}/{{#var:BUILD_FOLDER_ANDROID}}/variscite/kernel_imx/}}include/dt-bindings/pinctrl/ of the Linux kernel source you will find the pin functions definition files.<br>
The relevant file is pins-imx8mn.h.<br>
If you search it for GPIO4_IO22, for example, you will see a group of definitions with same prefix (pad name), "MX8MN_IOMUXC_SAI2_RXC".
<pre>
#define MX8MN_IOMUXC_SAI2_RXC_SAI2_RX_BCLK                                  0x01B4 0x041C 0x0000 0x0 0x0
#define MX8MN_IOMUXC_SAI2_RXC_SAI5_TX_BCLK                                  0x01B4 0x041C 0x04E8 0x1 0x2
#define MX8MN_IOMUXC_SAI2_RXC_UART1_DCE_RX                                  0x01B4 0x041C 0x04F4 0x4 0x3
#define MX8MN_IOMUXC_SAI2_RXC_UART1_DTE_TX                                  0x01B4 0x041C 0x0000 0x4 0x0
#define MX8MN_IOMUXC_SAI2_RXC_GPIO4_IO22                                    0x01B4 0x041C 0x0000 0x5 0x0
#define MX8MN_IOMUXC_SAI2_RXC_PDM_BIT_STREAM1                              0x01B4 0x041C 0x0538 0x6 0x8
</pre>
|}} }} }}
Adding only the one with the {{#ifeq: {{#var:HARDWARE_NAME}}|VAR-SOM-MX8MN|GPIO4_IO22|GPIO4_IO2}} suffix (function) to your dts file will let you use the pin as GPIO.


== Define a pin as GPIO in the kernel Device Tree ==
== Define a pin as GPIO in the kernel Device Tree ==
Line 244: Line 295:
};
};
</pre>
</pre>
|
|{{#ifeq: {{#var:HARDWARE_NAME}} | DART-MX8MM |
Edit {{#ifeq: {{#var:ANDROID_NAME}} | Pie |{{#var:BUILD_FOLDER}}/{{#var:BUILD_FOLDER_ANDROID}}/variscite/kernel_imx/}}arch/arm64/boot/dts/freescale/fsl-imx8mm-var-dart.dts and add the definition for the GPIO you need in the iomuxc node.<br>
Edit {{#ifeq: {{#var:ANDROID_NAME}} | Pie |{{#var:BUILD_FOLDER}}/{{#var:BUILD_FOLDER_ANDROID}}/variscite/kernel_imx/}}arch/arm64/boot/dts/freescale/fsl-imx8mm-var-dart.dts and add the definition for the GPIO you need in the iomuxc node.<br>
<pre>
<pre>
Line 261: Line 312:
};
};
</pre>
</pre>
}}
| {{#ifeq: {{#var:HARDWARE_NAME}} | VAR-SOM-MX8M-NANO |
Edit {{#ifeq: {{#var:ANDROID_NAME}} | Pie |{{#var:BUILD_FOLDER}}/{{#var:BUILD_FOLDER_ANDROID}}/variscite/kernel_imx/}}arch/arm64/boot/dts/freescale/fsl-imx8mn-var-som.dts and add the definition for the GPIO you need in the iomuxc node.<br>
<pre>
&iomuxc {
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_hog>;
 
imx8mn-var-som {
pinctrl_hog: hoggrp {
fsl,pins = <
/* Add your GPIO definitions here */
>;
};
};
...
};
</pre>
|}} }} }}


=== Device Tree GPIO attribute ===
=== Device Tree GPIO attribute ===

Revision as of 10:35, 26 January 2020


DART-MX8M GPIO

GPIO state

The current state of the system's GPIOs can be obtained in user-mode, as shown in the following example:

# cat /sys/kernel/debug/gpio
gpiochip0: GPIOs 0-31, parent: platform/30200000.gpio, 30200000.gpio:
 gpio-8   (                    |eth_phy_pwr         ) out hi    
 gpio-9   (                    |phy-reset           ) out hi    
 gpio-10  (                    |connect             ) in  hi IRQ

gpiochip1: GPIOs 32-63, parent: platform/30210000.gpio, 30210000.gpio:
 gpio-44  (                    |cd                  ) in  lo IRQ
 gpio-51  (                    |VSD_3V3             ) out hi    

gpiochip2: GPIOs 64-95, parent: platform/30220000.gpio, 30220000.gpio:

gpiochip3: GPIOs 96-127, parent: platform/30230000.gpio, 30230000.gpio:
 gpio-102 (                    |Back                ) in  hi IRQ
 gpio-109 (                    |Home                ) in  hi IRQ
 gpio-111 (                    |Down                ) in  hi IRQ
 gpio-113 (                    |?                   ) out lo    
 gpio-114 (                    |Up                  ) in  hi IRQ

Each GPIO is defined as in or out and the state is shown as lo or hi.
For example pin 44 is the SD card card-detect. When an SD card is plugged in, the state will be:

 gpio-44  (                    |cd                  ) in  lo IRQ

When the SD card is removed, the state will be:

 gpio-44  (                    |cd                  ) in  hi IRQ

Manipulating a single GPIO via /sys/class/gpio

Using a command line or a script

GPIOs in i.MX are grouped in groups of 32 pins.
For example, GPIO1_3 belong to the first group, pin 3. Its absolute number will be 3.
GPIO4_21 will be (4-1)*32+21=117.
Assuming this GPIO is defined in your device tree, the following is an example of how to use it from userspace.

To export the GPIO for userspace use:

$ echo 117 > /sys/class/gpio/export


To configure as output:

$ echo out > /sys/class/gpio/gpio117/direction

Set GPIO high:

$ echo 1 > /sys/class/gpio/gpio117/value

Set GPIO low:

$ echo 0 > /sys/class/gpio/gpio117/value


To configure as input:

$ echo in > /sys/class/gpio/gpio117/direction

Read the current value:

$ cat /sys/class/gpio/gpio117/value


To free the GPIO after you're done using it:

$ echo 117 > /sys/class/gpio/unexport

Using a C application

All of the command line operations above can be translated to C code:
Reserve (export) the GPIO:

#define IMX_GPIO_NR(port, index)    ((((port)-1)*32)+((index)&31))

int fd;
char buf[MAX_BUF]; 
int gpio = IMX_GPIO_NR(4, 21); /* Just an example */

fd = open("/sys/class/gpio/export", O_WRONLY);

sprintf(buf, "%d", gpio); 

write(fd, buf, strlen(buf));

close(fd);

Set the GPIO direction:

sprintf(buf, "/sys/class/gpio/gpio%d/direction", gpio);

fd = open(buf, O_WRONLY);

/* Set out direction */
write(fd, "out", 3); 
/* Set in direction */
write(fd, "in", 2); 

close(fd);

In case of out direction set the GPIO value:

sprintf(buf, "/sys/class/gpio/gpio%d/value", gpio);

fd = open(buf, O_WRONLY);

/* Set GPIO high status */
write(fd, "1", 1); 
/* Set GPIO low status */
write(fd, "0", 1); 

close(fd);

In case of in direction get the current GPIO value:

char value;

sprintf(buf, "/sys/class/gpio/gpio%d/value", gpio);

fd = open(buf, O_RDONLY);

read(fd, &value, 1);

if (value == '0') { 
     /* Current GPIO status low */
} else {
     /* Current GPIO status high */
}

close(fd);

Once finished, free (unexport) the GPIO:

fd = open("/sys/class/gpio/unexport", O_WRONLY);

sprintf(buf, "%d", gpio);

write(fd, buf, strlen(buf));

close(fd);

Important notes:

  • Remember that after the first read operation the file pointer will move to the next position in the file, so to get a correct value for each read operation you simply have to set the file pointer at the beginning of the file before read by using the following command:
lseek(fd, 0, SEEK_SET);
  • This is only a short example. If you want to use it in your code remember add error handling to it.

Kernel Device Tree GPIO configuration

Device Tree GPIO files

Pin Func files

In the directory include/dt-bindings/pinctrl/ of the Linux kernel source you will find the pin functions definition files.
The relevant file is pins-imx8mq.h.
If you search it for GPIO4_IO2, for example, you will see a group of definitions with same prefix (pad name), "MX8MQ_IOMUXC_SAI1_RXD0".

#define MX8MQ_IOMUXC_SAI1_RXD0_SAI1_RX_DATA0                                0x164 0x3CC 0x000 0x0 0x0
#define MX8MQ_IOMUXC_SAI1_RXD0_SAI5_RX_DATA0                                0x164 0x3CC 0x4D4 0x1 0x1
#define MX8MQ_IOMUXC_SAI1_RXD0_CORESIGHT_TRACE0                             0x164 0x3CC 0x000 0x4 0x0
#define MX8MQ_IOMUXC_SAI1_RXD0_GPIO4_IO2                                    0x164 0x3CC 0x000 0x5 0x0
#define MX8MQ_IOMUXC_SAI1_RXD0_CCMSRCGPCMIX_BOOT_CFG0                       0x164 0x3CC 0x000 0x6 0x0
#define MX8MQ_IOMUXC_SAI1_RXD0_SIM_M_HADDR17                                0x164 0x3CC 0x000 0x7 0x0

Adding only the one with the GPIO4_IO2 suffix (function) to your dts file will let you use the pin as GPIO.

Define a pin as GPIO in the kernel Device Tree

You need to add the relevant definitions to your device tree, as explained in the Pin Func files section above.
Edit arch/arm64/boot/dts/freescale/fsl-imx8mq-var-dart-common.dtsi and add the definition for the GPIO you need in the iomuxc node.

&iomuxc {
	pinctrl-names = "default";
	pinctrl-0 = <&pinctrl_hog>;

	imx8m-var-dart {
		pinctrl_hog: hoggrp {
			fsl,pins = <
				/* Add your GPIO definitions here */ 
			>;
		};
	};
 ...
};

Device Tree GPIO attribute

If you look at the pin control definitions in arch/arm64/boot/dts/freescale/fsl-imx8mq-var-dart-common.dtsi in the Linux kernel source tree, the number to the right of the pin mux macro can be used for additional attributes like pull-up, slew rate, open drain, drive strength, etc.
This value is written to the IOMUXC_SW_PAD_CTRL_ register of the relevant pin.
Please consult the SOC reference manual for details about the relevant register.