From: Robert Foss <robert.foss@linaro.org>
To: Andrey Konovalov <andrey.konovalov@linaro.org>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media <linux-media@vger.kernel.org>,
linux-arm-msm@vger.kernel.org,
Peter Griffin <peter.griffin@linaro.org>
Subject: Re: [PATCH 0/3] media: camss: extend VIDIOC_ENUM_* ioctls support
Date: Tue, 18 Aug 2020 15:33:43 +0200 [thread overview]
Message-ID: <CAG3jFytWaWH2TUprQ1dEjKatUEfWWzeuUc18J3g8zk6bE9-cQQ@mail.gmail.com> (raw)
In-Reply-To: <20200814205403.27639-1-andrey.konovalov@linaro.org>
Hey Andrey,
I've looked through this series, and it all looks good to me.
Acked-by: Robert Foss <robert.foss@linaro.org>
On Fri, 14 Aug 2020 at 22:54, Andrey Konovalov
<andrey.konovalov@linaro.org> wrote:
>
> The first two patches add mbus_code filtering support to VIDIOC_ENUM_FMT
> implementation, and VIDIOC_ENUM_FRAMESIZES support.
>
> The minimum and the maximum frame size values are deduced from
> __video_try_fmt() code.
>
> The third patch replaces harcoded limits in __video_try_fmt() with
> the definitions introduced by the second patch.
>
> Andrey Konovalov (3):
> media: camss: Make use of V4L2_CAP_IO_MC
> media: camss: add support for vidioc_enum_framesizes ioctl
> media: camss: __video_try_fmt(): don't use hardcoded constants
>
> .../media/platform/qcom/camss/camss-video.c | 112 +++++++++++++++---
> 1 file changed, 95 insertions(+), 17 deletions(-)
>
> --
> 2.17.1
>
prev parent reply other threads:[~2020-08-18 13:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-14 20:54 [PATCH 0/3] media: camss: extend VIDIOC_ENUM_* ioctls support Andrey Konovalov
2020-08-14 20:54 ` [PATCH 1/3] media: camss: Make use of V4L2_CAP_IO_MC Andrey Konovalov
2020-08-14 20:54 ` [PATCH 2/3] media: camss: add support for vidioc_enum_framesizes ioctl Andrey Konovalov
2020-08-14 20:54 ` [PATCH 3/3] media: camss: __video_try_fmt(): don't use hardcoded constants Andrey Konovalov
2020-08-18 13:33 ` Robert Foss [this message]
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=CAG3jFytWaWH2TUprQ1dEjKatUEfWWzeuUc18J3g8zk6bE9-cQQ@mail.gmail.com \
--to=robert.foss@linaro.org \
--cc=andrey.konovalov@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=peter.griffin@linaro.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.