Being able to control a couple of features of the AGC algo is one thing. Opening up full control of the ISP (eg lens shading etc) would require IP release discussions with Broadcom senior management. Seeing as they are continuing to use the IP in other chips, I doubt they'll be too keen. The support effort required for the "my settings don't work" complaints would be unsustainable too.jdb wrote:This times ten million. For a given telescope aperture, field of view and object the gains can be easily adjusted to a) not saturate the sensor and b) provide the best SNR - if not through calculation then via successive approximation.
We totally need an ASSUMING DIRECT CONTROL mode for the camera interface. Broadcom may have wizards working in the lens shading and tuning department, but I highly doubt that they ever considered the sensor<->device pairing would be used naked and attached without lens to a prime focus mount of your average garden-variety 10 inch reflector
For the request to disable the hardware denoise I am looking at a solution that would enable arbitrary disabling of any of the ISP blocks that are configured. Doing that on some blocks would be meaningless (no demosaic?!), but it may provide a way to bypass lens shading as well.
That's all ARM side, so fails my features list criteria of needing to be a firmware thing to be done in this particular time window.steve_gulick wrote:need a way to bypass (or a pass-thru) of the closed ISP. This would allow the use of sensors other than the OV5647 by I2C programming directly of the sensor's registers (like it is done in most of the other sensors that there are V4L2 drivers available.
This is really needed in the Compute Module if it is going to be sold to do serious industrial machine vision. One camera sensor can't meet all needs - that's why there are so many. The OV5647 has poor low light performance. Some users might need an HDR sensor or one with a global shutter. The closed nature of the ISP has been a real limitation. If, for what ever reason, it has to remain closed, we can do without it - just give us a way around it.
As above, releasing access to the ISP hardware isn't going to happen without lots of negotiation and a probably unmanageable support burden. gsh is on the case for getting the Unicam (receiver peripheral) docs released, but that is his negotiation with Broadcom lawyers.
I will make some "totally unrelated" comments:
- the same Unicam interface has been used on phones featuring VC4 hardware blocks but driven from the ARM.
- Kernel drivers would be open source with manufacturers obliged to release them.
- HTC are naughty by not releasing the kernel source for the Desire 601 Dual Sim - might be worth someone chasing them. (I haven't checked the Samsung Galaxy Y and Wave Y, but they are a bit older, more limited in camera functionality, and Samsung are pretty good on releasing the kernels).