@veye_xumm Sorry. Driver works. Testing and reading should be by v4l2.

@veye_xumm Thanks for the quick reply! Looks like I'm missing something. Can you help me with it?
I followed the documentation raspberrypi_v4l2. Unsuccessfully.
Env:

• Raspberry Pi 5

• OS: Linux raspberrypi 6.6.51+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.51-1+rpt3 (2024-10-08) aarch64 GNU/Linux

• I compiled cssc132.ko and cssc132.dtbo (from rpi-6.6.y dirs).

• then raspberrypi_v4l2/release/driver_bin/6.6.51+rpt-rpi-2712 was created

• after that I executed raspberrypi_v4l2/release/install_driver_rpi5.sh

• reboot

• then I tested /boot/firmware/config.txt:
  [all]
  dtparam=i2c_vc=on
  dtoverlay=cssc132
  dtoverlay=cssc132,cam0

After that video0 and video1 appeared.

Then I configured driver by executing following scripts:
./find_entity.sh
Found cssc132 @ i2c-4 entity on /dev/media1
Plese get frame from /dev/video0 and use /dev/v4l-subdev2 for camera setting.
./media_setting_rpi5.sh cssc132 -fmt UYVY -w 1280 -h 1080
This is a Raspberry Pi 5.
camera is YUV type
camera name cssc132; width 1280; height 1080; media_fmt UYVY8_1X16; pixel_fmt UYVY
CAM1 probed: media device is /dev/media1
set CAM1 finish, plese get frame from /dev/video0 and use /dev/v4l-subdev2 for camera setting
cssc132 6 NOT FOUND

After all I tried to test cam by ffprobe /dev/video0 or /dev/video1. But I see the following errors:
libswresample 4. 7.100 / 4. 7.100
libpostproc 56. 6.100 / 56. 6.100
[video4linux2,v4l2 @ 0x5555c17f7b00] ioctl(VIDIOC_G_FMT): Invalid argument
/dev/video1: Invalid argument

Hi
Is there a cssc132 driver update coming for raspberry pi 5?