From: Tomasz Figa <tfiga@chromium.org>
To: Alexandre Courbot <acourbot@chromium.org>
Cc: Paul Kocialkowski <paul.kocialkowski@bootlin.com>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Maxime Jourdan <mjourdan@baylibre.com>
Subject: Re: [PATCHv2 02/12] videodev2.h: add V4L2_FMT_FLAG_DYN_RESOLUTION
Date: Thu, 15 Aug 2019 19:09:53 +0900 [thread overview]
Message-ID: <CAAFQd5BqjrNDtkjZar6i8gCrxXvSgndOL7-0ERes4-WOSTqg5Q@mail.gmail.com> (raw)
In-Reply-To: <CAPBb6MWj_03kz1pVr5ap7iwr0Li0RVuTH9rKqqh5JqX5R+83-w@mail.gmail.com>
On Thu, Aug 15, 2019 at 5:12 PM Alexandre Courbot <acourbot@chromium.org> wrote:
>
> On Wed, Aug 14, 2019 at 9:53 PM Paul Kocialkowski
> <paul.kocialkowski@bootlin.com> wrote:
> >
> > Hi,
> >
> > On Mon 12 Aug 19, 13:05, Hans Verkuil wrote:
> > > From: Maxime Jourdan <mjourdan@baylibre.com>
> > >
> > > Add an enum_fmt format flag to specifically tag coded formats where
> > > dynamic resolution switching is supported by the device.
> > >
> > > This is useful for some codec drivers that can support dynamic
> > > resolution switching for one or more of their listed coded formats. It
> > > allows userspace to know whether it should extract the video parameters
> > > itself, or if it can rely on the device to send V4L2_EVENT_SOURCE_CHANGE
> > > when such changes are detected.
> >
> > Makes sense and looks good to me:
> > Reviewed-by: Paul Kocialkowski <paul.kocialkowski@bootlin.com>
> >
> > The docs aren't saying that this only applies to stateful decoders, but I think
> > it is quite clear that this can't apply to stateless decoders.
>
> Even though this can be inferred from reading the specs, I think it
> would be reasonable to explicitly mention it though.
>
> I also wonder, since this flag does not make sense for encoders, maybe
> we can use more precise vocabulary in the patch description and doc?
> I.e. s/codec/decoder.
>
> With that,
> Reviewed-by: Alexandre Courbot <acourbot@chromium.org>
There is no reason why it couldn't apply to an encoder. I think the
idea is to actually have the encoder advertise the same flag once we
figure out how to implement encoding with resolution changes.
Best regards,
Tomasz
next prev parent reply other threads:[~2019-08-15 10:10 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 11:05 [PATCHv2 00/12] Stateful/stateless codec core support Hans Verkuil
2019-08-12 11:05 ` [PATCHv2 01/12] videodev2.h: add V4L2_FMT_FLAG_CONTINUOUS_BYTESTREAM Hans Verkuil
2019-08-14 12:52 ` Paul Kocialkowski
2019-08-15 8:11 ` Alexandre Courbot
2019-08-15 8:13 ` Alexandre Courbot
2019-08-12 11:05 ` [PATCHv2 02/12] videodev2.h: add V4L2_FMT_FLAG_DYN_RESOLUTION Hans Verkuil
2019-08-14 12:53 ` Paul Kocialkowski
2019-08-15 8:11 ` Alexandre Courbot
2019-08-15 10:09 ` Tomasz Figa [this message]
2019-08-15 14:22 ` Hans Verkuil
2019-08-12 11:05 ` [PATCHv2 03/12] media: venus: vdec: flag OUTPUT formats with V4L2_FMT_FLAG_DYN_RESOLUTION Hans Verkuil
2019-08-12 13:49 ` Stanimir Varbanov
2019-08-14 12:54 ` Paul Kocialkowski
2019-08-12 11:05 ` [PATCHv2 04/12] media: s5p_mfc_dec: set flags for OUTPUT coded formats Hans Verkuil
2019-08-14 12:55 ` Paul Kocialkowski
2019-08-15 10:14 ` Tomasz Figa
2019-08-16 11:37 ` Marek Szyprowski
2019-08-16 11:47 ` Tomasz Figa
2019-08-12 11:05 ` [PATCHv2 05/12] media: mtk-vcodec: flag OUTPUT formats with V4L2_FMT_FLAG_DYN_RESOLUTION Hans Verkuil
2019-08-14 12:59 ` Paul Kocialkowski
2019-08-15 8:12 ` Alexandre Courbot
2019-08-12 11:05 ` [PATCHv2 06/12] media: vicodec: set flags for vdec/stateful OUTPUT coded formats Hans Verkuil
2019-08-14 13:04 ` Paul Kocialkowski
2019-08-12 11:05 ` [PATCHv2 07/12] media: docs-rst: Document memory-to-memory video decoder interface Hans Verkuil
2019-08-12 11:05 ` [PATCHv2 08/12] pixfmt-compressed.rst: improve H264/HEVC/MPEG1+2/VP8+9 documentation Hans Verkuil
2019-08-14 13:09 ` Paul Kocialkowski
2019-08-14 13:15 ` Hans Verkuil
2019-08-12 11:05 ` [PATCHv2 09/12] vb2: add V4L2_BUF_FLAG_M2M_HOLD_CAPTURE_BUF Hans Verkuil
2019-08-15 8:12 ` Alexandre Courbot
2019-08-15 11:53 ` Hans Verkuil
2019-08-15 12:27 ` Tomasz Figa
2019-08-15 12:31 ` Hans Verkuil
2019-08-15 14:27 ` Alexandre Courbot
2019-08-12 11:05 ` [PATCHv2 10/12] videodev2.h: add V4L2_DEC_CMD_FLUSH Hans Verkuil
2019-08-15 8:12 ` Alexandre Courbot
2019-08-15 11:53 ` Hans Verkuil
2019-08-12 11:05 ` [PATCHv2 11/12] media: docs-rst: Document m2m stateless video decoder interface Hans Verkuil
2019-08-15 9:58 ` Alexandre Courbot
2019-08-16 5:49 ` Alexandre Courbot
2019-08-16 6:59 ` Hans Verkuil
2019-08-16 7:17 ` Alexandre Courbot
2019-08-12 11:05 ` [PATCHv2 12/12] media: docs-rst: Document memory-to-memory video encoder interface Hans Verkuil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAAFQd5BqjrNDtkjZar6i8gCrxXvSgndOL7-0ERes4-WOSTqg5Q@mail.gmail.com \
--to=tfiga@chromium.org \
--cc=acourbot@chromium.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=mjourdan@baylibre.com \
--cc=paul.kocialkowski@bootlin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).