[Bug]: In linux-rk35xx-vendor.config, CONFIG_NVMEM_ROCKCHIP_OTP should be set to y.

[ackPeng]

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?

• Yes, my Ubuntu/Debian/OtherOS is running on WSL2

Relevant log URL

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[github-actions]

Hey @ackPeng! 👋

Thanks for opening your first issue with the Armbian project — we’re glad to have you here! 🧡
Your input doesn’t just help us improve the project — it benefits everyone who uses Armbian.

If you'd like to stay informed about project updates or collaborate more closely with the team,
you can optionally share some personal contact preferences at armbian.com/update-data.
This helps us keep in touch without relying solely on GitHub notifications.

Also, don’t forget to ⭐ star the repo to support the work — and welcome aboard! 🚀

[github-actions]

Jira ticket: AR-2834

[EvilOlaf]

feel free to send a pr adjusting this