The usage of cam_fsync_program_abs_start_value API to control camera fsync

Autonomous Vehicles DRIVE AGX Orin DRIVE AGX Orin General
4

Dear @SivaRamaKrishnaNV

My SW is refered from nvsipl_camera application SW of nvidia. It’s not be refered nvsipl_sample.

The camera model which is show from nvsipl_camera SW are following models.

for valeo IMX728 cameras,

  • V1SIM728S1RU3120NB20_CPHY_x4
  • V1SIM728MPRU4120HD1_CPHY_x4
  • V1SIM728MPRU3030ND1_CPHY_x4

for valeo IMX623 cameras,

  • V1SIM623S5RU5195NC0_CPHY_x4

Or should I configure the dtsi file before flash to EVB?

path : /drive/drive-linux/kernel/source/hardware/nvidia/platform/t23x/automotive/kernel-dts/p3710/common/tegra234-p3710-0010.dtsi

            fsync-groups {
                    status = "disabled";
                    fsync-group@0 {
                            id = <0>;
                            status = "okay";
                            generators = <&gen0>, <&gen2>, <&gen3>;
                    };
                    fsync-group@1 {
                            id = <1>;
                            status = "okay";
                            generators = <&gen1>;
                    };
            };

The status of fsync-groups is “disabled”. Should I change this to “okay”?

How I can find the valid range of group ID in parameter?

Best Regards
Bongrae Cho