Re: [PATCH 1/1] v4l: subdev: Serialise open and release internal ops

2015-07-28 Thread Hans Verkuil
On 07/22/2015 06:14 PM, Sakari Ailus wrote: > By default, serialise open and release internal ops using a mutex. > > The underlying problem is that a large proportion of the drivers do use Well, the only one I found that does this is the flash-led-class :-) But you are correct in your reply to m

Re: [PATCH 1/1] v4l: subdev: Serialise open and release internal ops

2015-07-25 Thread Sakari Ailus
Hi Hans, On Fri, Jul 24, 2015 at 11:08:06AM +0200, Hans Verkuil wrote: > Hi Sakari, > > On 07/22/2015 06:14 PM, Sakari Ailus wrote: > > By default, serialise open and release internal ops using a mutex. > > > > The underlying problem is that a large proportion of the drivers do use > > v4l2_fh_i

Re: [PATCH 1/1] v4l: subdev: Serialise open and release internal ops

2015-07-24 Thread Hans Verkuil
Hi Sakari, On 07/22/2015 06:14 PM, Sakari Ailus wrote: > By default, serialise open and release internal ops using a mutex. > > The underlying problem is that a large proportion of the drivers do use > v4l2_fh_is_singular() in their open() handlers (struct > v4l2_subdev_internal_ops). v4l2_subdev

[PATCH 1/1] v4l: subdev: Serialise open and release internal ops

2015-07-22 Thread Sakari Ailus
By default, serialise open and release internal ops using a mutex. The underlying problem is that a large proportion of the drivers do use v4l2_fh_is_singular() in their open() handlers (struct v4l2_subdev_internal_ops). v4l2_subdev_open(), .open file operation handler of the V4L2 sub-device frame