IMX219 get_mbus_config fail

[smzahraee]

When connecting the IMX219 camera, I encounter the following error:

imx219 2-0010 get_mbus_config fail, pls check it.

This issue occurs with kernel 6.1, but it works correctly with kernel 5.10.160. As a result, I'm unable to capture video from /dev/video0.

Any guidance or suggestions for resolving this would be greatly appreciated.

[    6.509422] rockchip-iodomain fdc20000.syscon:io-domains: pmuio2(3300000 uV) supplied by vcc_3v3
[    6.509543] rockchip-iodomain fdc20000.syscon:io-domains: vccio1(3300000 uV) supplied by vccio_acodec
[    6.509634] rockchip-iodomain fdc20000.syscon:io-domains: vccio2(1800000 uV) supplied by vcc_1v8
[    6.509734] rockchip-iodomain fdc20000.syscon:io-domains: vccio3(3300000 uV) supplied by vccio_sd
[    6.509783] rockchip-iodomain fdc20000.syscon:io-domains: vccio4(1800000 uV) supplied by vcc_1v8
[    6.509830] rockchip-iodomain fdc20000.syscon:io-domains: vccio5(3300000 uV) supplied by vcc_3v3
[    6.509879] rockchip-iodomain fdc20000.syscon:io-domains: vccio6(3300000 uV) supplied by vcc_3v3
[    6.509925] rockchip-iodomain fdc20000.syscon:io-domains: vccio7(3300000 uV) supplied by vcc_3v3
[    6.510331] imx219 2-0010: Consider updating driver imx219 to match on endpoints
[    6.510381] rockchip-csi2-dphy csi2-dphy1: dphy1 matches imx219 2-0010:bus type 5
[    6.510401] rockchip-csi2-dphy csi2-dphy1: imx219 2-0010 get_mbus_config fail, pls check it
[    6.511024] rockchip-csi2-dphy csi2-dphy1: imx219 2-0010 get_mbus_config fail, pls check it
[    6.511057] rockchip-csi2-dphy csi2-dphy1: imx219 2-0010 get_mbus_config fail, pls check it
[    6.511084] rkisp-vir0: Async subdev notifier completed
[    6.511098] rockchip-csi2-dphy csi2-dphy1: csi2 dphy1 probe successfully!
[    6.511480] mpp_rkvenc fdf40000.rkvenc: Adding to iommu group 4

[bmx666]

I found a patch for imx219 and ov5647 in another fork

Joshua-Riek@1b4e0ed

[igorpecovnik]

I found a patch for imx219 and ov5647 in another fork

Grab it and provide a PR.

[bmx666]

I got confirmation from customer on custom board based on rk3568, patched ov5647 can be captured and streaming.

Before patch for OV5647

root@smarc:~# dmesg | grep -i -e ov5647 -e csi -e mipi -e dphy
[ 8.226269] platform csi2-dphy1: Fixed dependency cycle(s) with /rkisp-vir0/port/endpoint@0
[ 8.805189] SCSI subsystem initialized
[ 9.666901] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 241)
[ 9.670025] rockchip-csi2-dphy-hw fe870000.csi2-dphy-hw: csi2 dphy hw probe successfully!
[ 10.197453] i2c 4-0036: Fixed dependency cycle(s) with /csi2-dphy1/ports/port@0/endpoint@1
[ 10.236802] rockchip-mipi-csi2-hw fdfb0000.mipi-csi2-hw: enter mipi csi2 hw probe!
[ 10.237172] rockchip-mipi-csi2-hw fdfb0000.mipi-csi2-hw: probe success, v4l2_dev:mipi-csi2-hw!
[ 10.242327] rkisp rkisp-vir0: Entity type for entity rkisp-csi-subdev was not initialized!
[ 10.337266] ov5647 4-0036: Consider updating driver ov5647 to match on endpoints
[ 10.337298] rockchip-csi2-dphy csi2-dphy1: dphy1 matches ov5647 4-0036:bus type 5
[ 10.337313] rockchip-csi2-dphy csi2-dphy1: ov5647 4-0036 get_mbus_config fail, pls check it
[ 10.337775] rockchip-csi2-dphy csi2-dphy1: ov5647 4-0036 get_mbus_config fail, pls check it
[ 10.337794] rockchip-csi2-dphy csi2-dphy1: ov5647 4-0036 get_mbus_config fail, pls check it
[ 10.337822] rockchip-csi2-dphy csi2-dphy1: csi2 dphy1 probe successfully!
[ 14.642550] rockchip-csi2-dphy csi2-dphy1: ov5647 4-0036 get_mbus_config fail, pls check it
[ 14.655974] rockchip-csi2-dphy csi2-dphy1: ov5647 4-0036 get_mbus_config fail, pls check it
[ 14.658456] rockchip-csi2-dphy csi2-dphy1: ov5647 4-0036 get_mbus_config fail, pls check it
[ 14.667623] rockchip-csi2-dphy csi2-dphy1: ov5647 4-0036 get_mbus_config fail, pls check it
[ 14.673766] rockchip-csi2-dphy csi2-dphy1: ov5647 4-0036 get_mbus_config fail, pls check it
[ 14.675991] rockchip-csi2-dphy csi2-dphy1: ov5647 4-0036 get_mbus_config fail, pls check it
[ 14.693690] rockchip-csi2-dphy csi2-dphy1: ov5647 4-0036 get_mbus_config fail, pls check it
[ 14.700768] rockchip-csi2-dphy csi2-dphy1: ov5647 4-0036 get_mbus_config fail, pls check it

After patch for OV5647

root@smarc:~# dmesg | grep -i -e ov5647 -e csi -e mipi -e dphy
[ 8.216025] platform csi2-dphy1: Fixed dependency cycle(s) with /rkisp-vir0/port/endpoint@0
[ 8.795314] SCSI subsystem initialized
[ 9.655310] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 241)
[ 9.658522] rockchip-csi2-dphy-hw fe870000.csi2-dphy-hw: csi2 dphy hw probe successfully!
[ 10.184039] i2c 4-0036: Fixed dependency cycle(s) with /csi2-dphy1/ports/port@0/endpoint@1
[ 10.187504] ov5647 4-0036: driver version: 00.01.01
[ 10.187800] ov5647 4-0036: OV5647 power on
[ 10.716071] ov5647 4-0036: OV5647 power off
[ 10.718561] ov5647 4-0036: OmniVision OV5647 camera driver probed
[ 10.722982] rockchip-mipi-csi2-hw fdfb0000.mipi-csi2-hw: enter mipi csi2 hw probe!
[ 10.723355] rockchip-mipi-csi2-hw fdfb0000.mipi-csi2-hw: probe success, v4l2_dev:mipi-csi2-hw!
[ 10.728530] rkisp rkisp-vir0: Entity type for entity rkisp-csi-subdev was not initialized!
[ 10.819350] ov5647 4-0036: Consider updating driver ov5647 to match on endpoints
[ 10.819386] rockchip-csi2-dphy csi2-dphy1: dphy1 matches m00_b_ov5647 4-0036:bus type 5
[ 10.819940] rockchip-csi2-dphy csi2-dphy1: csi2 dphy1 probe successfully!

Waiting feedback for patched IMX219 driver.

P.S. But rk3588 has some issues with kernel 6.1 (ISP/CIF/MIPI-CSI)

[igorpecovnik]

But rk3588 has some issues with kernel 6.1

"Some"? :) Well, this #289 is best what is publicly available and we have negative support budget to maintain this stack.

[bmx666]

@igorpecovnik relax man, no one blamed or shamed you. I jumped into Rockchip 2 months ago, and deal with customized USB, PCIe, DisplayPort, HDMI and I2S for different codecs for the customers. Jumped into MIPI-CSI 3-4 weeks ago, and I'm trying to support customer into this area. Luck of documentation from Rockchip makes it even harder. Binding these cameras via DTS another story, 1 week of pain.

Meanwhile from the latest customer update about patched IMX219, it works on rk3568 also.
Patched imx219 can be captured and streaming.

Before patch for IMX219

root@smarc:~# dmesg | grep -i -e imx219 -e csi -e mipi
[ 8.222906] platform csi2-dphy1: Fixed dependency cycle(s) with /rkisp-vir0/port/endpoint@0
[ 8.801019] SCSI subsystem initialized
[ 9.664466] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 241)
[ 9.667560] rockchip-csi2-dphy-hw fe870000.csi2-dphy-hw: csi2 dphy hw probe successfully!
[ 10.190952] i2c 4-0010: Fixed dependency cycle(s) with /csi2-dphy1/ports/port@0/endpoint@1
[ 10.194076] imx219 4-0010: Looking up VANA-supply from device tree
[ 10.194111] imx219 4-0010: Looking up VANA-supply property in node /i2c@fe5d0000/cam0_imx219@10 failed
[ 10.194172] imx219 4-0010: supply VANA not found, using dummy regulator
[ 10.194388] imx219 4-0010: Looking up VDIG-supply from device tree
[ 10.194414] imx219 4-0010: Looking up VDIG-supply property in node /i2c@fe5d0000/cam0_imx219@10 failed
[ 10.194462] imx219 4-0010: supply VDIG not found, using dummy regulator
[ 10.194561] imx219 4-0010: Looking up VDDL-supply from device tree
[ 10.194587] imx219 4-0010: Looking up VDDL-supply property in node /i2c@fe5d0000/cam0_imx219@10 failed
[ 10.194629] imx219 4-0010: supply VDDL not found, using dummy regulator
[ 10.208752] rockchip-mipi-csi2-hw fdfb0000.mipi-csi2-hw: enter mipi csi2 hw probe!
[ 10.209134] rockchip-mipi-csi2-hw fdfb0000.mipi-csi2-hw: probe success, v4l2_dev:mipi-csi2-hw!
[ 10.214278] rkisp rkisp-vir0: Entity type for entity rkisp-csi-subdev was not initialized!
[ 10.303838] imx219 4-0010: Consider updating driver imx219 to match on endpoints
[ 10.303877] rockchip-csi2-dphy csi2-dphy1: dphy1 matches imx219 4-0010:bus type 5
[ 10.303891] rockchip-csi2-dphy csi2-dphy1: imx219 4-0010 get_mbus_config fail, pls check it
[ 10.304357] rockchip-csi2-dphy csi2-dphy1: imx219 4-0010 get_mbus_config fail, pls check it
[ 10.304378] rockchip-csi2-dphy csi2-dphy1: imx219 4-0010 get_mbus_config fail, pls check it
[ 10.304405] rockchip-csi2-dphy csi2-dphy1: csi2 dphy1 probe successfully!
[ 14.955735] rockchip-csi2-dphy csi2-dphy1: imx219 4-0010 get_mbus_config fail, pls check it
[ 14.966300] rockchip-csi2-dphy csi2-dphy1: imx219 4-0010 get_mbus_config fail, pls check it
[ 14.972171] rockchip-csi2-dphy csi2-dphy1: imx219 4-0010 get_mbus_config fail, pls check it
[ 14.981961] rockchip-csi2-dphy csi2-dphy1: imx219 4-0010 get_mbus_config fail, pls check it
[ 14.988296] rockchip-csi2-dphy csi2-dphy1: imx219 4-0010 get_mbus_config fail, pls check it
[ 15.010605] rockchip-csi2-dphy csi2-dphy1: imx219 4-0010 get_mbus_config fail, pls check it
[ 87.604836] rockchip-csi2-dphy csi2-dphy1: imx219 4-0010 get_mbus_config fail, pls check it
[ 87.669250] rockchip-csi2-dphy csi2-dphy1: imx219 4-0010 get_mbus_config fail, pls check it
[ 87.676575] rockchip-csi2-dphy1: dphy1, data_rate_mbps 912

After patch for IMX219

root@smarc:~# dmesg | grep -i -e imx219 -e csi -e mipi -e dphy
[ 8.218330] platform csi2-dphy2: Fixed dependency cycle(s) with /rkisp-vir1/port/endpoint@0
[ 8.797975] SCSI subsystem initialized
[ 9.659508] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 241)
[ 9.662701] rockchip-csi2-dphy-hw fe870000.csi2-dphy-hw: csi2 dphy hw probe successfully!
[ 10.188661] i2c 3-0010: Fixed dependency cycle(s) with /csi2-dphy2/ports/port@0/endpoint@1
[ 10.192448] imx219 3-0010: driver version: 00.01.01
[ 10.217353] imx219 3-0010: Model ID 0x0219, Lot ID 0x818c83, Chip ID 0x00f2
[ 10.217397] ==> imx219 ken: 1104 imx219_probe
[ 10.221868] rockchip-mipi-csi2-hw fdfb0000.mipi-csi2-hw: enter mipi csi2 hw probe!
[ 10.222252] rockchip-mipi-csi2-hw fdfb0000.mipi-csi2-hw: probe success, v4l2_dev:mipi-csi2-hw!
[ 10.227458] rkisp rkisp-vir1: Entity type for entity rkisp-csi-subdev was not initialized!
[ 10.320906] imx219 3-0010: Consider updating driver imx219 to match on endpoints
[ 10.320943] rockchip-csi2-dphy csi2-dphy2: dphy2 matches m01_b_imx219 3-0010:bus type 5
[ 10.321692] rockchip-csi2-dphy csi2-dphy2: csi2 dphy2 probe successfully!

[bmx666]

P.S. the customer kernel was based on branch rk-6.1-rkr3

[igorpecovnik]

relax man, no one blamed or shamed you

Didn't take it that way, no worries. Heard that too many times.

1 week of pain

Understand. Aim of Armbian is to address and mitigate this common pain. With what we have, as much as possible, best effort.

Luck of documentation from Rockchip makes it even harder.

This is what they sell, alongside with support. In case you want to speed up and your company can cover, I can privately link you with a person that knows more and is operating in this area. Just an idea.

Patched imx219 can be captured and streaming.

Great to hear that!