3 ms·
good news great to hear, all in all. sensor interfaces are one of the things open source has needed the most help on. good look that Qualcomm reached out & got
by rektide 6y ago
good news great to hear, all in all. sensor interfaces are one of the things open source has needed the most help on. good look that Qualcomm reached out & got Linaro to build a (hopefully) good set of drivers.
less than stellar though: However, the image processing pipeline has been revamped, and the ISPIF no longer exists. What replaces it is an embedded CPU which is fed commands and in turn configures the data processing blocks. Adding support for this CPU is beyond the current scope of CAMSS due to the amount of work it would take to enable and the lack of documentation for the CPU command stream.
that's not the greatest to here. it'd be a good thing to be able to experiment with. but hopefully this encourages some reverse engineering of the command stream.
also with noting that google moved away from their custom Video Core & then follow up Neural Core chips on the latest Pixel 5[1]. which sounded semi-somewhat similar to this new general embedded imaging cpu. that computational photography work is probably largely mostly on the gpu now, i'd guess? probably some cpu. I doubt Google has spent a ton of time tapping the ISP but maybe. that'd be a good first thing to try to observe, to reverse, just seeing how much isp utization there is on a modern Pixel.
[1] https://9to5google.com/2020/10/01/google-pixel-5-neural-core/ https://9to5google.com/2020/10/01/google-pixel-5-neural-core...