Back

Don't expect too much for now: both image quality and performance are not quite where we want them to be.
That, however, also means that there are a lot of low hanging fruits where help is very welcome :)
We need to create #libcamera tuning files for the individual cameras, the swISP could be improved to use the GPU for debayering, there are WIP autofocus patches that could be tried and improved - and in Snapshot we need to reduce the number of copies before frames reach the screen or encoders.

Note that with all of this in place, camera support on a lot of other devices is in close reach. For example the #OnePlus6 and #SHIFT6mq should only need kernel patches enabling the camera sensors. The softwareISP should then - at least in theory - "just work". Well, fingers crossed :)

P.S.: the one device where this already worked is the #PinePhonePro - but until recently it broke audio. That was also fixed in the process.

P.S.S.: maybe I'm a bit too optimistic regarding QC devices, see below

@pavel Which missing parts do you have in mind? And would they be on the kernel or libcamera side?

P.S.: I was under the impression that the qcom-camss should work there as well - or that it at least wouldn't be missing much.

@rmader @pavel OP6 needs the camss driver updated to support C-PHY on that platform, which currently only supports D-PHY.
Unfortunately - without the datasheets from qualcomm or some reverse engineering of the drivers in a binary implementation thats' quite difficult I think.

Once that's done - I believe we can run the IMX519 that is present on the OP6.

@libcamera @pavel Ah right. Yeah, need to talk @cas into coming over again for another session on that :) (or the shift, which IIRC uses D-PHY?)