What happened?
In linux-rk35xx-vendor.config, CONFIG_NVMEM_ROCKCHIP_OTP should be set to y. Since rkcif depends on OTP, if OTP is set to 'm', it will load very late, which will also cause rkcif to load very late. This will result in rkisp timing out while waiting for rkcif and giving up waiting for the subdev of rkcif.
This caused the RK ISP to be unable to obtain sensor data, resulting in the ISP being unusable on the RK3588 platform. It needs to be fixed.
How to reproduce?
It can be reproduced by simply plugging in any camera.
Branch
main (main development branch)
On which host OS are you running the build script and observing this problem?
Ubuntu 24.04 Noble
Are you building on Windows WSL2?
Relevant log URL
No response
Code of Conduct
What happened?
In linux-rk35xx-vendor.config, CONFIG_NVMEM_ROCKCHIP_OTP should be set to y. Since rkcif depends on OTP, if OTP is set to 'm', it will load very late, which will also cause rkcif to load very late. This will result in rkisp timing out while waiting for rkcif and giving up waiting for the subdev of rkcif.
This caused the RK ISP to be unable to obtain sensor data, resulting in the ISP being unusable on the RK3588 platform. It needs to be fixed.
How to reproduce?
It can be reproduced by simply plugging in any camera.
Branch
main (main development branch)
On which host OS are you running the build script and observing this problem?
Ubuntu 24.04 Noble
Are you building on Windows WSL2?
Relevant log URL
No response
Code of Conduct