It is this atomisp-ov5693 for which I pasted above. So what I did for my kernel (4.18.14) was to revert the removal of atomisp (which also included an OV5693 driver). The OV5693 driver included in the camera.patch won't even compile because it includes v4l2-chip-ident.h which is an old header only present in kernel 3.x series. So with quite a bit of luck we only need to wait some time and adapt the controller driver for OV5693 to work without the atomisp subsystem. The catch is: This has apparently been removed because the atomisp subsystem was a bit of a mess and Intel didn't care enough to fix it. The atomisp is a different signal processor for some older Intel Atom platform, but we might be able to use that as a template, AFAIK this also uses some CSI-2 PCI interface.
This depends on the atomisp subsystem and won't work with anything else without modification. Then there's the OV5693 driver, or rather the one that was in staging. Maybe it's working, maybe not, haven't had the time to check that yet. In this case, there are 3 GPIO ouput lines defined in ACPI, but the driver expects an additional 4 input lines. The TPS68470 also has a driver upstream, but the same problem there. I've enabled it in the kernel options but nothing changes with respect to video devices under /dev. The CSI-2 interface has an upstream driver, but I'm not sure if that's working properly or supports everything. I'm not yet sure if we actually need that, or if we can get the images directly from the CSI-2 interface. There's a bit about all of that here (Section 3.4), but not really much to go on.Īs to drivers: There's currently some work upstream for the ISP device, it's currently in staging for 4.21. This is also a PCI device ( 8086:1919), and if I understand that correctly, independent of the CSI-2 interface. According to the kernel, those are TPS68470, which is a "Power Management IC (PMIC) with flash LED driver and ref clock generation for compact camera module", so that would fit in.Īlso there's the matter of the ISP (Image Signal Processor). Then there are the INT3472 devices, which are defined in the ACPI directly next to each camera sensor. This device is shared by all cameras (on KabyLake it can handle 4 of them parallel, on SkyLake 2 or 3, AFAIK depending on the configuration). The I2C interface is for stuff like setting the exposure etc., the actual images are provided via a MIPI CSI-2 (Camera Serial Interface) connection handled by a PCI device (with ID 8086:9d32). This is in fact the actual camera sensor, but it doesn't directly provide the images.
Here's a rough overview: OV5693 is a camera sensor with an I2C interface. I've had a look at this over the past couple days and I still don't quite understand things as good as I'd like to get started. Yeah, unfortunately it won't be that easy.
0 kommentar(er)
