I am concerned about is that after configuring the pinmux as GPIO, i try to read it in system ,so i exporting it under the eMMC system . but it displays Device or resource busy.
root@tegra-ubuntu:/sys/class/gpio# sudo cat /sys/kernel/debug/gpio|grep "gpio-486"
gpio-486 (PAC.00 |camera-control-outpu) out lo
root@tegra-ubuntu:/sys/class/gpio# sudo cat /sys/kernel/debug/gpio|grep "gpio-487"
gpio-487 (PAC.01 |camera-control-outpu) out lo
root@tegra-ubuntu:/sys/class/gpio#
why this two pins are still used in camera functions.and how can i find these camera-control-outpu node.i grep it in my dts source but i can not find it
i know that from other topics , we don’t have camera on our custom board and i want to know how to free it and use it as gpio. i see one is for CAM1_PWDN and the other for CAM1_RST_L , Could you give me some suggestions About it ?
[ 4.107785] gpio-394 (camera-control-output-low): hogged as output/low
[ 4.107816] gpio-397 (camera-control-output-low): hogged as output/low
[ 4.107840] gpio-487 (camera-control-output-low): hogged as output/low
[ 4.107856] gpio-486 (camera-control-output-low): hogged as output/low
may I also confirm which Jetpack release version you’re working with,
as you can see, it’s AGX Orin’s main camera device tree to include all camera module sources, and define the CAM1_PWDN pin.
for instance, $public_sources/kernel_src/hardware/nvidia/platform/t23x/concord/kernel-dts/cvb/tegra234-p3737-camera-modules.dtsi
please try remove that main camera device tree if you’re not have cameras on the customize board.
for example,
i am using jetpack6.0 (r36.3) ,this directory is not exit. my directory is Linux_for_Tegra/source/hardware/nvidia/t23x/nv-public/overlay/tegra234-p3737-camera-modules.dtsi,actually ,i have remove the gpio@220000 in the tegra234-p3737-camera-modules.dtsi file .i will try to flash again.