When you said you plugged in a sensor to i2c-1, I assumed you meant one of your image sensors, not just a random sensor of some form.
If you're not seeing any addresses on i2c-4 or 6 ever, I'd check your control of regulators and reset GPIOs.
Do note that you can not have both sensors claiming "<&gpio 5 1>", and that that will be GPIO5 on the 40pin header, not the GPIO on the camera connectors. All the image sensor overlays in our kernel tree use cam1_reg and cam0_reg as regulators which do control the relevant GPIO on the CAM/DISP connector.
Having to modprobe i2c-regmap implies that your module Kconfig entry is missing a "select REGMAP_I2C". Actually there is no module i2c-regmap, only regmap-i2c. Typo or genuine error?
Your ST forum post contradicts this one, as there you have "[ 5.581963] vd56g3 10-0010: Successfully probe vd66gy sensor".
Pi5 REQUIRES configuration via Media Controller. There is no simple option for just using /dev/video0 to configure everything. As per your media-ctl output, you have no link enabled from csi2 pad 4 to rp1-cfe-csi2_ch0 pad 0, and the formats for the links are not configured.
Even on Pi0-4, you've included "brcm,media-controller;" in your overlay, so you've enabled Media Controller there too (see viewtopic.php?t=322076).
Pi5 also supports either directly writing the bitstream as received (hence all the "Packed" Bayer formats as formats 15-26), or unpacking to the highest bits of 16bpp (hence formats 27 to 30). It does not support unpacking to the bottom bits of a 16 bit word as the Pi0-4 Unicam block did, which would have included BA10.
All sensor controls need to be set through the relevant /dev/v4l-subdevN node for the sensor.
Libcamera on Pi5 uses the CFE to preprocess the images and produce stats. It does not write the raw data directly out to SDRAM through /dev/video0.
If you're not seeing any addresses on i2c-4 or 6 ever, I'd check your control of regulators and reset GPIOs.
Do note that you can not have both sensors claiming "<&gpio 5 1>", and that that will be GPIO5 on the 40pin header, not the GPIO on the camera connectors. All the image sensor overlays in our kernel tree use cam1_reg and cam0_reg as regulators which do control the relevant GPIO on the CAM/DISP connector.
Having to modprobe i2c-regmap implies that your module Kconfig entry is missing a "select REGMAP_I2C". Actually there is no module i2c-regmap, only regmap-i2c. Typo or genuine error?
Your ST forum post contradicts this one, as there you have "[ 5.581963] vd56g3 10-0010: Successfully probe vd66gy sensor".
Pi5 REQUIRES configuration via Media Controller. There is no simple option for just using /dev/video0 to configure everything. As per your media-ctl output, you have no link enabled from csi2 pad 4 to rp1-cfe-csi2_ch0 pad 0, and the formats for the links are not configured.
Even on Pi0-4, you've included "brcm,media-controller;" in your overlay, so you've enabled Media Controller there too (see viewtopic.php?t=322076).
Pi5 also supports either directly writing the bitstream as received (hence all the "Packed" Bayer formats as formats 15-26), or unpacking to the highest bits of 16bpp (hence formats 27 to 30). It does not support unpacking to the bottom bits of a 16 bit word as the Pi0-4 Unicam block did, which would have included BA10.
All sensor controls need to be set through the relevant /dev/v4l-subdevN node for the sensor.
Libcamera on Pi5 uses the CFE to preprocess the images and produce stats. It does not write the raw data directly out to SDRAM through /dev/video0.
Statistics: Posted by 6by9 — Tue Dec 17, 2024 6:01 pm