Re: [ANN] Meeting minutes of the Cambourne meeting

[Sakari Ailus <sakari.ailus@maxwell.research.nokia.com>]

nitesh moundekar wrote:
> Hi Sakari,

Hi Nitesh,

> So without touching these controls, drivers should be able to work with
> default or internal settings calculated from frame rate and resolution. And
> when application like DSLR wants more control it can access those controls.

The current interface is provided from V4L2 subdevs, so the application
using that can be expected to know something of the system already.

It may be up to drivers to decide what do they implement and what they
do not. We'll have to see how generic the new way of configuring the
sensors is; my hope is that practically all raw bayer sensors (not the
SoC ones!) could be configured this way. Lack of information from
manufacturer could limit the ability to write such drivers for sensors,
though.

With such a system, an user space algorithm library (a plugin for
libv4l) will be needed in any case to come up with a fully functional
system useful for generic applications, and it may well be that this
interface will be used from the plugins.

Alternatively the old interface could be implemented using a wrapper
library for all drivers providing the new sensor configuration
interface. There would be a list of default modes, some of which could
be more board dependent than others.

Regards,

-- 
Sakari Ailus
sakari.ailus@maxwell.research.nokia.com