Hi Sylwester, On Tuesday 29 November 2011 17:40:10 Sylwester Nawrocki wrote: > On 11/29/2011 12:08 PM, Hans Verkuil wrote: > > On Monday 28 November 2011 14:02:49 Sylwester Nawrocki wrote: > >> On 11/28/2011 01:39 PM, Hans Verkuil wrote: > >>> On Monday 28 November 2011 13:13:32 Sylwester Nawrocki wrote: > >>>> On 11/28/2011 12:38 PM, Hans Verkuil wrote: > >>>>> On Friday 25 November 2011 16:39:31 Sylwester Nawrocki wrote: > > Here is a patch that updates the range. It also sends a control event > > telling any listener that the range has changed. Tested with vivi and a > > modified v4l2-ctl. > > > > The only thing missing is a DocBook entry for that new event flag and > > perhaps some more documentation in places. > > > > Let me know how this works for you, and if it is really needed, then I > > can add it to the control framework. > > Thanks for your work, it's very appreciated. > > I've tested the patch with s5p-fimc and it works well. I just didn't check > the event part yet. > > I spoke to Kamil as in the past he considered the control range updating > at the codec driver. But since separate controls are used for different > encoding standards, this is not needed it any more. > > Nevertheless I have at least two use cases, for the alpha control and > for the image sensor driver. In case of the camera sensor, different device > revisions may have different step and maximum value for some controls, > depending on firmware. > By using v4l2_ctrl_range_update() I don't need to invoke lengthy sensor > start-up procedure just to find out properties of some controls. Wouldn't it be confusing for applications to start with a range and have it updated at runtime ? > It would be nice to have this enhancement in mainline. -- Regards, Laurent Pinchart -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
