From: Sakari Ailus <sakari.ailus@iki.fi>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-media@vger.kernel.org,
Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>
Subject: Re: [PATCH] media: v4l2-subdev: Fix stream handling for crop API
Date: Tue, 2 Apr 2024 08:46:15 +0000 [thread overview]
Message-ID: <ZgvF1wi2UpkUTC9-@valkosipuli.retiisi.eu> (raw)
In-Reply-To: <20240402084407.GC10288@pendragon.ideasonboard.com>
On Tue, Apr 02, 2024 at 11:44:07AM +0300, Laurent Pinchart wrote:
> On Tue, Apr 02, 2024 at 08:20:22AM +0000, Sakari Ailus wrote:
> > Moi,
> >
> > On Tue, Apr 02, 2024 at 02:37:25AM +0300, Laurent Pinchart wrote:
> > > When support for streams was added to the V4L2 subdev API, the
> > > v4l2_subdev_crop structure was extended with a stream field, but the
> > > field was not handled in the core code that translates the
> > > VIDIOC_SUBDEV_[GS]_CROP ioctls to the selection API. Fix it.
> >
> > The field is indeed in the UAPI headers. But do we want to support the CROP
> > IOCTL for streams? Shouldn't the callers be using the [GS]_SELECTION
> > instead?
>
> They should, but if the field is there, we should support it :-) The
> alternative is to remove it. It will cause failures in v4l2-compliance
> that we'll need to handle though.
I'd prefer to stick to selections here, this is new functionality so
[GS]_CROP support isn't required. I don't have a strong opinion on the
matter though.
>
> > > Fixes: 2f91e10ee6fd ("media: subdev: add stream based configuration")
> > > Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > > ---
> > > drivers/media/v4l2-core/v4l2-subdev.c | 2 ++
> > > 1 file changed, 2 insertions(+)
> > >
> > > diff --git a/drivers/media/v4l2-core/v4l2-subdev.c b/drivers/media/v4l2-core/v4l2-subdev.c
> > > index 4c6198c48dd6..45836f0a2b0a 100644
> > > --- a/drivers/media/v4l2-core/v4l2-subdev.c
> > > +++ b/drivers/media/v4l2-core/v4l2-subdev.c
> > > @@ -732,6 +732,7 @@ static long subdev_do_ioctl(struct file *file, unsigned int cmd, void *arg,
> > > memset(&sel, 0, sizeof(sel));
> > > sel.which = crop->which;
> > > sel.pad = crop->pad;
> > > + sel.stream = crop->stream;
> > > sel.target = V4L2_SEL_TGT_CROP;
> > >
> > > rval = v4l2_subdev_call(
> > > @@ -756,6 +757,7 @@ static long subdev_do_ioctl(struct file *file, unsigned int cmd, void *arg,
> > > memset(&sel, 0, sizeof(sel));
> > > sel.which = crop->which;
> > > sel.pad = crop->pad;
> > > + sel.stream = crop->stream;
> > > sel.target = V4L2_SEL_TGT_CROP;
> > > sel.r = crop->rect;
> > >
> > >
> > > base-commit: 39cd87c4eb2b893354f3b850f916353f2658ae6f
>
> --
> Regards,
>
> Laurent Pinchart
--
Sakari Ailus
next prev parent reply other threads:[~2024-04-02 8:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-01 23:37 [PATCH] media: v4l2-subdev: Fix stream handling for crop API Laurent Pinchart
2024-04-02 6:04 ` Tomi Valkeinen
2024-04-02 8:20 ` Sakari Ailus
2024-04-02 8:44 ` Laurent Pinchart
2024-04-02 8:46 ` Sakari Ailus [this message]
2024-04-02 9:11 ` Tomi Valkeinen
2024-04-02 9:22 ` Laurent Pinchart
2024-04-02 15:23 ` Sakari Ailus
2024-04-02 20:11 ` Laurent Pinchart
2024-04-03 6:51 ` Tomi Valkeinen
2024-04-03 7:01 ` Laurent Pinchart
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=ZgvF1wi2UpkUTC9-@valkosipuli.retiisi.eu \
--to=sakari.ailus@iki.fi \
--cc=hverkuil-cisco@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=tomi.valkeinen@ideasonboard.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