Hi Hans,
On Thu, Mar 29, 2018 at 11:16:45AM +0200, Hans Verkuil wrote:
> On 29/03/18 11:01, Sakari Ailus wrote:
> > On Thu, Mar 29, 2018 at 10:57:44AM +0200, Hans Verkuil wrote:
> >> On 29/03/18 10:45, Sakari Ailus wrote:
> >>> Hi Hans,
> >>>
> >>> On Wed, Mar 28, 2018 at 03:50:04PM +0200, Hans Verkuil wrote:
> >>> ...
> >>>> @@ -88,6 +96,8 @@ struct media_device_ops {
> >>>> * @disable_source: Disable Source Handler function pointer
> >>>> *
> >>>> * @ops: Operation handler callbacks
> >>>> + * @req_lock: Serialise access to requests
> >>>> + * @req_queue_mutex: Serialise validating and queueing requests
> >>>
> >>> s/validating and//
> >>>
> >>> As there's no more a separate validation step. Then,
> >>
> >> Well, you validate before queuing. It's not a separate step, but
> >> part of the queue operation. See patch 23 where this is implemented
> >> in the vb2_request_helper function.
> >
> > Works for me. I think we'll need the validate op sooner or later anyway.
> >
>
>
> There is one. Request objects have prepare, unprepare and queue ops.
>
> The request req_queue op will prepare all objects, and only queue if the
> prepare (aka validate) step succeeds for all objects. If not, then the
You can't validate the objects in a request separately from other objects
in it, the validation needs to happen at the request level. There are two
reasons for this:
- The objects in a request must be compatible with all other objects in the
request and
- The request must contain the required objects in order to be valid ---
e.g. for a device producing multiple capture buffers from one output
buffer, the output buffer is mandatory whereas one or more of the capture
buffers are not.
The latter could presumably be implemented separately for each object but
then the driver needs to go fishing for the related objects which may not
be very efficient.
What I'm proposing is to put this at the level of a request, at least for
now.
--
Sakari Ailus
sakari.ailus@xxxxxxxxxxxxxxx
