This is a cache of https://discuss.96boards.org/t/has-anyone-tested-camera-in-kernel-5-7/9866. It is a snapshot of the page at 2024-10-31T13:30:50.135+0000.
Has Anyone tested camera in kernel-5.7? - DragonBoard 820c - 96Boards Forum

Has Anyone tested camera in kernel-5.7?

Products Support DragonBoard 820c
#1

Hi,

getting errors if i enable qcom camss “CONFIG_VIDEO_QCOM_CAMSS=m” in kernel-5.7,
attached logs here, [10] platform_init()[10] target_init()[10] RPM GLink Init[10] Opening RPM - Pastebin.com

[ 21.124438] debugfs: Directory ‘a34000.camss-vdda’ with parent ‘vreg_l2a_1p25’ already present!
[ 21.132785] debugfs: Directory ‘a34000.camss-vdda’ with parent ‘vreg_l2a_1p25’ already present!
[ 21.147073] debugfs: Directory ‘a34000.camss-vdda’ with parent ‘vreg_l2a_1p25’ already present!
[ 21.280280] qcom-camss: probe of a34000.camss failed with error -17

[ 77.333044] pc : pm_runtime_drop_link+0xf4/0x2e0
[ 77.333048] lr : device_link_add+0x23c/0x5e8
[ 77.333050] sp : ffff800013683890
[ 77.333052] x29: ffff800013683890 x28: ffff0000ea8b0110
[ 77.333056] x27: 0000000000000000 x26: 0000000000020000
[ 77.333059] x25: ffff800013683c48 x24: 0000000000000001
[ 77.333062] x23: ffff0000ea8b1308 x22: ffff0000f884b010
[ 77.333066] x21: ffffffffffffffef x20: 0000000000000004
[ 77.333069] x19: ffffffffffffffef x18: 0000000000000000
[ 77.333072] x17: 0000000000000000 x16: 0000000000000000
[ 77.333075] x15: 0000000000000000 x14: 0000000000000000
[ 77.333078] x13: 0000000000000000 x12: 0000000000000000
[ 77.333081] x11: fefefefefefefeff x10: 0000ffffc3de5f39
[ 77.333084] x9 : 0000000000000000 x8 : ffff0000ead31408
[ 77.333087] x7 : 0000000000000000 x6 : 000000000000003f
[ 77.333090] x5 : ffff0000ec3bf238 x4 : 0000000000000000
[ 77.333093] x3 : ffff0000ea8b0110 x2 : 00000000000001af
[ 77.333096] x1 : 00000000000001af x0 : ffffffffffffffef
[ 77.333100] Call trace:
[ 77.333104] pm_runtime_drop_link+0xf4/0x2e0
[ 77.333106] device_link_add+0x23c/0x5e8
[ 77.333120] camss_pm_domain_on+0x38/0x60 [qcom_camss]
[ 77.333127] vfe_set_power+0x264/0x670 [qcom_camss]
[ 77.333161] pipeline_pm_power_one+0xe8/0x150 [videodev]
[ 77.333174] pipeline_pm_power.part.0+0x54/0xf0 [videodev]
[ 77.333185] v4l2_pipeline_pm_use+0x54/0x90 [videodev]
[ 77.333208] v4l2_pipeline_pm_get+0x14/0x20 [videodev]
[ 77.349820] EA = 0, S1PTW = 0
[ 77.355981] video_open+0x70/0xf0 [qcom_camss]
[ 77.355994] v4l2_open+0x7c/0x128 [videodev]
[ 77.355999] chrdev_open+0xa8/0x1c0
[ 77.356004] do_dentry_open+0x1cc/0x3e8
[ 77.356007] vfs_open+0x2c/0x38
[ 77.356012] path_openat+0xaf4/0xe38
[ 77.356015] do_filp_open+0x7c/0x100
[ 77.356018] do_sys_openat2+0x200/0x2d0
[ 77.356021] do_sys_open+0x64/0xa0
[ 77.356023] __arm64_sys_openat+0x24/0x30
[ 77.356031] el0_svc_common.constprop.2+0x68/0x170
[ 77.356034] do_el0_svc+0x24/0x90
[ 77.356039] el0_sync_handler+0xe8/0x190
[ 77.356041] el0_sync+0x158/0x180
[ 77.356048] Code: 88027c01 35ffffa2 17fff8a9 f9800051 (885f7c40)
[ 77.356053] —[ end trace 90b858eeeaea3241 ]—

Any idea?

@Loic
@todortomov
@vinaysimha

Thanks,
Arun

#2

Hi, I encountered the same problem with both kernel-5.7 ad 5.8.

I had to modify camss@a00000 node’s power-domains attribute in /arch/arm64/boot/dts/qcom/msm8996.dtsi to fix the problem:

camss: camss@a00000 {
    ....
    power-domains = <&mmcc VFE0_GDSC>,
        <&mmcc VFE1_GDSC>;
    ....
};
1 Like
#3

@robertfoss, look like we need this change.

#4

Nice catch Timothy!

I’ve added the patch to the linaro qcom integration branch which should include the patch in the next build, and submitted a patch to LKML.