Hi I am trying to port camera driver and HAL on Samsung Board. My camera driver uses Samsung Camera Interface FIMC driver The fimc0,fimc1 and fimc2 are registered and Following device Nodes are created successfully /dev/video1 ,/dev/video1 and /dev/video2
My camera driver is registered as subdev for the fimc driver which registers as a video device to the v4l2 Framework When i open the camera, My camera driver probe is called but rest of the v4l2_subdev_core_ops like init is not called since fimc device is busy s3c-fimc-0 : (0) Clock sclk_fimc(0) enabled. [ 1699.717696] s3c-fimc-0 : fimc_open: fd.lcd_hres=480 fd.lcd_vres=800 [ 1699.723179] s3c-fimc-0 : s3c-fimc0 opened. [ 1699.726742] s3c-fimc-0 : fimc_querycap: called [ 1699.737662] s3c-fimc-0 : fimc_enum_input: index 0 [ 1699.741025] s3c-fimc-0 : fimc_s_input: index 0 [ 1699.751937] My camera Driver loaded. [ 1699.756052] s3c-fimc-2 : (2) Clock sclk_fimc(2) enabled. [ 1699.763375] s3c-fimc-2 : fimc_open: fd.lcd_hres=480 fd.lcd_vres=800 [ 1699.778094] s3c-fimc-2 : (2) Clock sclk_fimc(2) disabled. [ 1699.786897] s3c-fimc-2 : s3c-fimc2 opened. [ 1699.789655] s3c-fimc-2 : fimc_querycap: called [ 1699.794110] s3c-fimc-2 : fimc_enum_input: index 0 [ 1699.798763] s3c-fimc-2 : fimc_s_input: index 0 [ 1699.836793] s3c-fimc-0 : fimc_enum_input: index 0 [ 1699.857959] s3c-fimc-1 : Current context is 0 [ 1699.861596] s3c-fimc-1 : (1) Clock sclk_fimc(1) enabled. [ 1699.872835] s3c-fimc-1 : fimc_open: fd.lcd_hres=480 fd.lcd_vres=800 [ 1699.883535] s3c-fimc-1 : (1) Clock sclk_fimc(1) disabled. [ 1699.893756] s3c-fimc-1 : s3c-fimc1 opened. [ 1699.900200] s3c-fimc-1 : fimc_querycap: called [ 1699.903281] s3c-fimc-1 : fimc_g_fmt_vid_out: called [ 1700.049894] s3c-fimc-1 : fimc_open: Device busy. [ 1700.073728] s3c-fimc-1 : fimc_open: Device busy. [ 1700.099395] s3c-fimc-1 : fimc_open: Device busy. [ 1700.123148] s3c-fimc-1 : fimc_open: Device busy. After this fimc_release is called and camera closes!!! Any inputs on why fimc device is busy....Can anybody explain the flow of how the Fimc_open fimc_remove gets called Thanks Kavitha -- unsubscribe: android-kernel+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-kernel
