From: Helen Koike <helen.koike@collabora.com>
To: Boris Brezillon <boris.brezillon@collabora.com>, Brian.Starkey@arm.com
Cc: mchehab@kernel.org, hans.verkuil@cisco.com,
laurent.pinchart@ideasonboard.com, sakari.ailus@iki.fi,
linux-media@vger.kernel.org, tfiga@chromium.org,
hiroh@chromium.org, nicolas@ndufresne.ca, kernel@collabora.com,
narmstrong@baylibre.com, linux-kernel@vger.kernel.org,
frkoenig@chromium.org, mjourdan@baylibre.com,
stanimir.varbanov@linaro.org
Subject: Re: [PATCH v4 0/6] media: v4l2: Add extended fmt and buffer ioctls
Date: Tue, 21 Jul 2020 10:56:25 -0300 [thread overview]
Message-ID: <6bbcc4e3-aaaa-624e-94bf-a950dd77421b@collabora.com> (raw)
In-Reply-To: <20200721131537.6ff83c71@collabora.com>
Hi Boris,
On 7/21/20 8:15 AM, Boris Brezillon wrote:
> Hello Helen,
>
> Just a few drive-by comments.
>
> On Fri, 17 Jul 2020 08:54:29 -0300
> Helen Koike <helen.koike@collabora.com> wrote:
>
>> Hi,
>>
>> I'm sorry for taking too long to submit v4.
>>
>> It is not perfect, not all v4l2-compliance tests passes, but I'd like a review,
>> specially on the API and potential problems, so I can focus on improving implementation
>> and maybe drop the RFC tag for next version.
>>
>> Follow below what changed in v4 and some items I'd like to discuss:
>>
>>
>> * Ioctl to replace v4l2_pix_format
>> ---------------------------------------------------------------------------------
>> During last media summit, we agreed to create ioctls that replace the v4l2_pix_format
>> struct and leave the other structs in the v4l2_format union alone.
>> Thus I refactored the code to receive struct v4l2_ext_pix_format, and I renamed the
>> ioctls, so now we have:
>>
>> int ioctl(int fd, VIDIOC_G_EXT_FMT, struct v4l2_ext_pix_format *argp);
>
> Maybe use the EXT_PIX_FMT suffix here since the struct is really only
> about pixel formats.
Sorry, this is a copy&paste error, I'm already using this suffix in the code, except for the ioctls
that handle buffers (since they get v4l2_ext_buffer struct).
Regards,
Helen
>
>> int ioctl(int fd, VIDIOC_S_EXT_FMT, struct v4l2_ext_pix_format *argp);
>> int ioctl(int fd, VIDIOC_TRY_EXT_FMT, struct v4l2_ext_pix_format *argp);
>>
>> The only valid types are V4L2_BUF_TYPE_VIDEO_CAPTURE and V4L2_BUF_TYPE_VIDEO_OUTPUT,
>> all the other types are invalid with this API.
>>
>
> [...]
>
>>
>>
>> Boris Brezillon (5):
>> media: v4l2: Extend pixel formats to unify single/multi-planar
>> handling (and more)
>> media: videobuf2: Expose helpers to implement the _ext_fmt and
>> _ext_buf hooks
>> media: mediabus: Add helpers to convert a ext_pix format to/from a
>> mbus_fmt
>> media: vivid: Convert the capture and output drivers to
>> EXT_FMT/EXT_BUF
>> media: vimc: Implement the ext_fmt and ext_buf hooks
>
> I think you should take ownership of these patches. The end result is
> likely to be completely different from what I initially posted, and
> you're the one doing the hard work here.
>
>>
>> Hans Verkuil (1):
>> media: v4l2: Add extended buffer operations
>>
>> .../media/common/videobuf2/videobuf2-core.c | 2 +
>> .../media/common/videobuf2/videobuf2-v4l2.c | 549 +++++-----
>> .../media/test-drivers/vimc/vimc-capture.c | 61 +-
>> drivers/media/test-drivers/vimc/vimc-common.c | 6 +-
>> drivers/media/test-drivers/vimc/vimc-common.h | 2 +-
>> drivers/media/test-drivers/vivid/vivid-core.c | 70 +-
>> .../test-drivers/vivid/vivid-touch-cap.c | 26 +-
>> .../test-drivers/vivid/vivid-touch-cap.h | 3 +-
>> .../media/test-drivers/vivid/vivid-vid-cap.c | 169 +---
>> .../media/test-drivers/vivid/vivid-vid-cap.h | 15 +-
>> .../media/test-drivers/vivid/vivid-vid-out.c | 193 ++--
>> .../media/test-drivers/vivid/vivid-vid-out.h | 15 +-
>> drivers/media/v4l2-core/v4l2-dev.c | 50 +-
>> drivers/media/v4l2-core/v4l2-ioctl.c | 934 ++++++++++++++++--
>> include/media/v4l2-ioctl.h | 60 ++
>> include/media/v4l2-mediabus.h | 42 +
>> include/media/videobuf2-core.h | 6 +-
>> include/media/videobuf2-v4l2.h | 21 +-
>> include/uapi/linux/videodev2.h | 144 +++
>> 19 files changed, 1650 insertions(+), 718 deletions(-)
>>
>
prev parent reply other threads:[~2020-07-21 13:56 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 11:54 [PATCH v4 0/6] media: v4l2: Add extended fmt and buffer ioctls Helen Koike
2020-07-17 11:54 ` [PATCH v4 1/6] media: v4l2: Extend pixel formats to unify single/multi-planar handling (and more) Helen Koike
2020-07-21 10:37 ` Hans Verkuil
2020-07-28 15:18 ` Helen Koike
2020-07-28 15:30 ` Hans Verkuil
2020-07-17 11:54 ` [PATCH v4 2/6] media: v4l2: Add extended buffer operations Helen Koike
2020-07-21 10:48 ` Hans Verkuil
2020-07-21 14:36 ` Helen Koike
2020-07-21 11:26 ` Stanimir Varbanov
2020-07-21 13:54 ` Helen Koike
2020-07-21 14:30 ` Stanimir Varbanov
2020-07-21 14:40 ` Helen Koike
2020-07-24 13:16 ` Stanimir Varbanov
2020-07-27 12:01 ` Helen Koike
2020-07-28 18:02 ` Stanimir Varbanov
2020-07-27 12:35 ` Tomasz Figa
2020-07-28 18:08 ` Stanimir Varbanov
2020-08-05 14:05 ` Tomasz Figa
2020-07-17 11:54 ` [PATCH v4 3/6] media: videobuf2: Expose helpers to implement the _ext_fmt and _ext_buf hooks Helen Koike
2020-07-17 11:54 ` [PATCH v4 4/6] media: mediabus: Add helpers to convert a ext_pix format to/from a mbus_fmt Helen Koike
2020-07-17 11:54 ` [PATCH v4 5/6] media: vivid: Convert the capture and output drivers to EXT_FMT/EXT_BUF Helen Koike
2020-07-17 11:54 ` [PATCH v4 6/6] media: vimc: Implement the ext_fmt and ext_buf hooks Helen Koike
2020-07-20 11:57 ` [PATCH v4 0/6] media: v4l2: Add extended fmt and buffer ioctls Tomasz Figa
2020-07-20 19:47 ` Helen Koike
2020-07-21 10:24 ` Hans Verkuil
2020-07-21 14:23 ` Helen Koike
2020-07-21 14:34 ` Hans Verkuil
2020-07-21 11:15 ` Boris Brezillon
2020-07-21 13:56 ` Helen Koike [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=6bbcc4e3-aaaa-624e-94bf-a950dd77421b@collabora.com \
--to=helen.koike@collabora.com \
--cc=Brian.Starkey@arm.com \
--cc=boris.brezillon@collabora.com \
--cc=frkoenig@chromium.org \
--cc=hans.verkuil@cisco.com \
--cc=hiroh@chromium.org \
--cc=kernel@collabora.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mjourdan@baylibre.com \
--cc=narmstrong@baylibre.com \
--cc=nicolas@ndufresne.ca \
--cc=sakari.ailus@iki.fi \
--cc=stanimir.varbanov@linaro.org \
--cc=tfiga@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox