Xavier industrial gpio device or resource busy

Autonomous Machines Jetson & Embedded Systems Jetson AGX Xavier
1

Our customized carrier board use 4 x gpio, two of which are occupied,but I did not use these GPIOs for other functions.

image
image1230×170 27 KB

Calculate the GPIO number from the Pinmux table
GPIO4- 290; GPIO5 -503;GPIO20 -291;GPIO21-288
gpiochip2: GPIOs 240-247, parent: platform/max77620-gpio, max77620-gpio, can sleep:
gpio-246 ( |gpio_default ) out hi
gpio-247 ( |gpio_default ) out hi

gpiochip1: GPIOs 248-287, parent: platform/c2f0000.gpio, tegra-gpio-aon:
gpio-248 (CAN1_DOUT )
gpio-249 (CAN1_DIN )
gpio-250 (CAN0_DOUT )
gpio-251 (CAN0_DIN )
gpio-252 ( )
gpio-253 ( |usb-p9-0-5v0 ) out lo
gpio-254 ( |fairchild,vbus5v ) out lo
gpio-255 ( )
gpio-256 (GPIO8 |vdd-1v8-sd ) out hi
gpio-257 (GPIO9 |enable_gpio_patch ) out hi
gpio-258 ( |vdd-hdmi-p2-5v0 ) out hi
gpio-259 ( )
gpio-260 ( )
gpio-261 ( )
gpio-262 ( )
gpio-263 ( )
gpio-264 ( )
gpio-265 ( )
gpio-266 ( )
gpio-267 ( )
gpio-268 ( )
gpio-269 ( )
gpio-270 ( )
gpio-271 (I2C2_CLK )
gpio-272 (I2C2_DAT )
gpio-273 ( )
gpio-274 ( )
gpio-275 ( )
gpio-276 ( )
gpio-277 ( )
gpio-284 ( |power-key ) in hi
gpiochip0: GPIOs 288-511, parent: platform/2200000.gpio, tegra-gpio:
gpio-288 ( )
gpio-289 ( |vdd-12v-pcie ) out hi
gpio-290 ( )
gpio-291 ( |vdd-hdmi-p1-5v0 ) out lo
gpio-292 ( )
gpio-293 ( )
gpio-294 ( )
gpio-295 ( )
gpio-296 ( )
gpio-297 ( )
gpio-298 ( )
gpio-299 ( )
gpio-300 ( )
gpio-301 ( )
gpio-302 ( )
gpio-303 ( )
gpio-304 ( )
gpio-305 ( )
gpio-306 ( )
gpio-307 ( )
gpio-308 ( )
gpio-309 ( )
gpio-310 ( )
gpio-311 ( )
gpio-312 ( )
gpio-313 ( )
gpio-314 ( )
gpio-315 ( )
gpio-316 ( )
gpio-317 ( )
gpio-318 ( )
gpio-319 ( )
gpio-320 ( )
gpio-321 ( )
gpio-322 ( )
gpio-323 ( )
gpio-324 ( )
gpio-325 ( )
gpio-326 ( )
gpio-327 ( )
gpio-328 ( )
gpio-329 ( )
gpio-330 ( )
gpio-331 ( )
gpio-332 ( )
gpio-333 ( )
gpio-334 ( )
gpio-335 ( )
gpio-336 ( |force-recovery ) in hi
gpio-337 ( )
gpio-338 ( |DP0-HPD-CTL ) out lo
gpio-339 ( |wifi-enable ) out hi
gpio-340 ( )
gpio-341 ( |eqos_phy_reset ) out hi
gpio-342 ( )
gpio-343 ( |cd ) in lo
gpio-344 (GPIO35 )
gpio-345 ( )
gpio-346 ( |temp-alert ) in hi
gpio-347 ( )
gpio-348 ( )
gpio-349 ( )
gpio-350 ( )
gpio-351 (I2S2_CLK )
gpio-352 (I2S2_DOUT )
gpio-353 (I2S2_DIN )
gpio-354 (I2S2_FS )
gpio-355 ( )
gpio-356 ( )
gpio-357 ( )
gpio-358 ( )
gpio-359 ( )
gpio-360 ( )
gpio-361 ( )
gpio-362 ( )
gpio-363 ( )
gpio-364 ( )
gpio-365 ( )
gpio-366 ( )
gpio-367 ( )
gpio-368 ( )
gpio-369 ( )
gpio-370 ( )
gpio-371 ( )
gpio-372 ( )
gpio-373 ( )
gpio-374 ( )
gpio-375 ( )
gpio-376 ( )
gpio-377 ( )
gpio-378 ( |pcie_wake ) in hi
gpio-379 ( )
gpio-380 ( )
gpio-381 ( )
gpio-382 ( )
gpio-383 ( )
gpio-384 ( )
gpio-385 ( |hdmi2.0_hpd ) in hi
gpio-386 ( |hdmi2.0_hpd ) in lo
gpio-387 ( )
gpio-388 ( )
gpio-389 ( |vdd_sys_en ) out lo
gpio-390 ( |reset_gpio ) out lo
gpio-391 ( |bt_ext_wake ) out hi
gpio-392 ( |avdd-cam-2v8 ) out lo
gpio-393 ( )
gpio-394 ( )
gpio-395 ( )
gpio-396 ( )
gpio-397 ( )
gpio-398 ( )
gpio-399 ( )
gpio-400 ( )
gpio-401 ( )
gpio-402 ( )
gpio-403 ( )
gpio-404 ( )
gpio-405 ( )
gpio-406 ( )
gpio-407 ( )
gpio-408 ( )
gpio-409 ( )
gpio-410 ( )
gpio-411 ( )
gpio-412 (GPIO32 )
gpio-413 ( )
gpio-414 ( )
gpio-415 ( )
gpio-416 ( )
gpio-417 (GPIO17 |fairchild,int_n ) in hi
gpio-418 ( )
gpio-419 ( )
gpio-420 ( |cc-switch-gpio ) out hi
gpio-421 ( )
gpio-422 (MCLK05 )
gpio-423 ( |fairchild,vbus5v ) out hi
gpio-424 ( )
gpio-425 ( )
gpio-426 (UART1_TX )
gpio-427 (UART1_RX )
gpio-428 (UART1_RTS )
gpio-429 (UART1_CTS )
gpio-430 ( )
gpio-431 ( )
gpio-432 ( )
gpio-433 ( )
gpio-434 ( )
gpio-435 ( )
gpio-436 ( )
gpio-437 ( )
gpio-438 ( )
gpio-439 ( )
gpio-440 ( )
gpio-441 ( )
gpio-442 ( )
gpio-443 ( )
gpio-444 ( )
gpio-445 ( )
gpio-446 ( )
gpio-447 ( )
gpio-448 ( )
gpio-449 ( )
gpio-450 ( )
gpio-451 ( )
gpio-452 ( )
gpio-453 ( )
gpio-454 ( )
gpio-455 ( )
gpio-456 ( )
gpio-457 ( )
gpio-458 ( )
gpio-459 ( )
gpio-460 ( )
gpio-461 ( )
gpio-462 ( )
gpio-463 ( )
gpio-464 ( )
gpio-465 ( )
gpio-466 ( )
gpio-467 ( )
gpio-468 ( )
gpio-469 ( )
gpio-470 ( )
gpio-471 ( )
gpio-472 ( )
gpio-473 ( )
gpio-474 ( )
gpio-475 ( )
gpio-476 ( )
gpio-477 ( )
gpio-478 ( )
gpio-479 ( )
gpio-480 ( |bt_host_wake ) in hi
gpio-481 ( )
gpio-482 ( )
gpio-483 (SPI3_CS0_N )
gpio-484 ( )
gpio-485 ( )
gpio-486 ( )
gpio-487 ( )
gpio-488 ( )
gpio-489 ( |fairchild,int_n ) in hi
gpio-490 ( )
gpio-491 (SPI1_CLK )
gpio-492 (SPI1_MISO )
gpio-493 (SPI1_MOSI )
gpio-494 (SPI1_CS0_N )
gpio-495 (SPI1_CS1_N )
gpio-496 ( )
gpio-497 ( )
//p2822_vdd_hdmi_5v0: regulator@112 {
rtso1001_vdd_hdmi_p1_5v0: regulator@112 {
compatible = “regulator-fixed”;
reg = <112>;
//regulator-name = “vdd-hdmi-5v0”;
regulator-name = “vdd-hdmi-p1-5v0”;
regulator-min-microvolt = <5000000>;
regulator-max-microvolt = <5000000>;
//gpio = <&tegra_main_gpio TEGRA194_MAIN_GPIO(A, 3) 0>;
//enable-active-high;
};

3

hello baijianping1989,

did you follow Jetson AGX Xavier Platform Adaptation and Bring-Up to update the board configuration files accordingly?

4

Hi,
I did not find gPIO to update. These four GPIOs are only used for GPIO functions . gpio-291 and gpio-503 be occupied. but I did not use these GPIOs for other functions. in addition gpio-289 be occupied.Even if I have comment out. I can’t find gpio-503 in /sys/kernel/debug/gpio

5

hello baijianping1989,

please access Jetson AGX Xavier Series Pinmux via download center for reference,
did you mean these four pins? there’re default usage as mentioned in the last column.
for example,

Signal Name  / GPIO        / Jetson Dev kit Usage
GPIO04       / GPIO3_PA.02 / Combo UFS/SD memory card detection
GPIO05       / GPIO3_PA.07 / 12V VR Enable
GPIO20       / GPIO3_PA.03 / CVB HDMI 5V enable
GPIO21       / GPIO3_PA.00 / SD card power enable
6

Hi JerryChang,
yes,can these four pins be used for GPIO function? Because I have 4 GPIO pins on the custom carry board use these four gpio pins . Our custom carrier board can normally use these GPIO pins on xaver 32GB L4T32.5.0.

7

hello baijianping1989,

note, here’s GPIO20 and GPIO21 of Jetson Dev kit default usage in the device tree settings.

                p2822_vdd_1v8_sd: regulator@104 {
                        gpio = <&tegra_main_gpio TEGRA194_MAIN_GPIO(A, 0) 0>;

                p2822_vdd_sdmmc1_sw: regulator@106 {
                        gpio = <&tegra_main_gpio TEGRA194_MAIN_GPIO(A, 0) 0>;

                p2822_vdd_hdmi_5v0: regulator@112 {
                        gpio = <&tegra_main_gpio TEGRA194_MAIN_GPIO(A, 3) 0>;

according to pinmux, those pin has already configure as GPIO,
you should also revise the device tree settings to adapt to your platform.
thanks

8

I see. Thank you very much.