hello BSP_User,
>>Q1
note, I’ve point-out t23x/p3768/ since you’re developing based-on Orin NX.
due to different camera connector, there’s no IMX185 device tree for Orin NX/Nano series.
so… please refer to IMX185 reference driver with Jetson AGX Orin series. (i.e. t23x/concord/)
for instance,
you may check below two device tree for reference.
(1) it’s device tree with IMX185 sensor specific settings.
$public_sources/kernel_src/hardware/nvidia/platform/t23x/common/kernel-dts/t234-common-modules/tegra234-camera-imx185-a00.dtsi
(2) here’s camera control specific settings.
$public_sources/kernel_src/hardware/nvidia/platform/t23x/concord/kernel-dts/cvb/tegra234-p3737-0000-camera-imx185-a00.dtsi
>>Q2, Q3
yes, that’s just an unique string. usually, we used CSI-port and I2C slave address to specify a camera node.
in this example, imx185_a@1a,
it means it’s IMX185 for using CSI port-A, which is under I2C at 0x1a.
>>Q4
yes, it’s just a variable,
you may use CONFIG_I2C_IOEXPANDER_SER_MAX9295=m to build as a module. (*.ko)
or, CONFIG_I2C_IOEXPANDER_SER_MAX9295=y to always build-in the driver with the kernel image.