Hi Hans,
On Mon, Jan 22, 2018 at 10:19:13AM +0100, Hans Verkuil wrote:
> On 21/01/18 23:48, Sakari Ailus wrote:
> > Hi Hans,
> >
> > On Sun, Jan 21, 2018 at 11:46:46AM +0100, Hans Verkuil wrote:
> >> Hi Sakari,
> >>
> >> I looked a bit closer at how atomisp uses g/s_parm. They abuse the
> >> cap
On 21/01/18 23:48, Sakari Ailus wrote:
> Hi Hans,
>
> On Sun, Jan 21, 2018 at 11:46:46AM +0100, Hans Verkuil wrote:
>> Hi Sakari,
>>
>> I looked a bit closer at how atomisp uses g/s_parm. They abuse the
>> capturemode field
>> to select video/preview/still modes on the sensor, which actually chan
Hi Hans,
On Sun, Jan 21, 2018 at 11:46:46AM +0100, Hans Verkuil wrote:
> Hi Sakari,
>
> I looked a bit closer at how atomisp uses g/s_parm. They abuse the
> capturemode field
> to select video/preview/still modes on the sensor, which actually changes the
> list
> of supported resolutions.
>
>
Hi Sakari,
I looked a bit closer at how atomisp uses g/s_parm. They abuse the capturemode
field
to select video/preview/still modes on the sensor, which actually changes the
list
of supported resolutions.
The following files use this:
i2c/atomisp-gc0310.c
i2c/atomisp-gc2235.c
i2c/atomisp-ov268
