[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAAFQd5Cn9GzXEj+tBtJsL8GXouJEyj+HSUng5StqNsCxKZK9yw@mail.gmail.com>
Date: Tue, 9 Jul 2019 15:15:05 +0900
From: Tomasz Figa <tfiga@...omium.org>
To: Alexandre Courbot <acourbot@...omium.org>
Cc: Paul Kocialkowski <paul.kocialkowski@...tlin.com>,
Maxime Ripard <maxime.ripard@...tlin.com>,
Nicolas Dufresne <nicolas@...fresne.ca>,
Hans Verkuil <hverkuil@...all.nl>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Linux Media Mailing List <linux-media@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v5] media: docs-rst: Document m2m stateless video decoder interface
On Thu, Jun 20, 2019 at 4:35 PM Alexandre Courbot <acourbot@...omium.org> wrote:
[snip]
> +Initialization
> +==============
> +
[snip]
> +5. *[optional]* Choose a different ``CAPTURE`` format than suggested via
> + :c:func:`VIDIOC_S_FMT` on ``CAPTURE`` queue. It is possible for the client to
> + choose a different format than selected/suggested by the driver in
> + :c:func:`VIDIOC_G_FMT`.
> +
> + * **Required fields:**
> +
> + ``type``
> + a ``V4L2_BUF_TYPE_*`` enum appropriate for ``CAPTURE``.
> +
> + ``pixelformat``
> + a raw pixel format.
We should be able to set different width and height as well, to allow
strided and padded frame buffers. Otherwise we wouldn't be able to
import DMA-bufs allocated from some other sources.
(FYI, I've posted a similar comment to the stateful interface too.)
Best regards,
Tomasz
Powered by blists - more mailing lists