So I’ve come to terms with that I need to make a custom driver for my MIPI CSI sensor, and I’m trying my best at following the Sensor Software Driver Programming guide.
At the very top it says There are two types of camera programming paths. You must choose one, depending on the camera and your application: Camera Core Library interface or Direct V4L2 interface.
I will only work with the raw data from the sensor, so it seems clear that I should go for the latter choice. However, it isn’t clear at all to me if that should impact my device tree modules and/or driver, and if so what parts of them? Or does this only matter at the application layer?
The first mention of anything that seems specific the Camera Core Library is Device Tree-related under Individual Imaging Device → Property Value pairs, at num_control_point . Can and/or should I omit for example everything that has to do with the control points, and if so, how do I figure out what else I can omit?
The only thing that seems to relate to the Camera Core Library driver-wise (at least for V4L version 2, which it seems I should use) is under * V4L2 Kernel Driver (Version 2.0)* → * Control Handlers* TEGRA_CAMERA_CID_VI_BYPASS_MODE. Does that mean it doesn’t matter for the driver?