From: jacopo mondi <jacopo@jmondi.org>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: linux-media@vger.kernel.org,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Jacopo Mondi <jacopo+renesas@jmondi.org>,
Hans Verkuil <hans.verkuil@cisco.com>
Subject: Re: [PATCH 2/9] media: convert g/s_parm to g/s_frame_interval in subdevs
Date: Mon, 22 Jan 2018 15:45:42 +0100 [thread overview]
Message-ID: <20180122144542.GB13087@w540> (raw)
In-Reply-To: <20180122101857.51401-3-hverkuil@xs4all.nl>
Hi Hans,
On Mon, Jan 22, 2018 at 11:18:50AM +0100, Hans Verkuil wrote:
> From: Hans Verkuil <hans.verkuil@cisco.com>
>
>
[snip]
> diff --git a/drivers/media/platform/atmel/atmel-isc.c b/drivers/media/platform/atmel/atmel-isc.c
> index 34676409ca08..92d695b29fa9 100644
> --- a/drivers/media/platform/atmel/atmel-isc.c
> +++ b/drivers/media/platform/atmel/atmel-isc.c
> @@ -1417,20 +1417,14 @@ static int isc_g_parm(struct file *file, void *fh, struct v4l2_streamparm *a)
> {
> struct isc_device *isc = video_drvdata(file);
>
> - if (a->type != V4L2_BUF_TYPE_VIDEO_CAPTURE)
> - return -EINVAL;
> -
> - return v4l2_subdev_call(isc->current_subdev->sd, video, g_parm, a);
> + return v4l2_g_parm_cap(video_devdata(file), isc->current_subdev->sd, a);
> }
As I've reported in a comment to the CEU patch series, after having
re-based my in-review driver on this series, I noticed I need to set
a->parm.capture.readbuffers to 0, as my driver does not support
CAP_READWRITE, and v4l2-compliance checks for (readbuffers == 0) if
that's the case.
As atmel-isc (and I suspect other drivers modified by this patch) does
not support CAP_READWRITE, don't you need to set capturebuffers to 0
as well in order not to v4l2-compliance unhappy?
(I would have tested myself, but I don't have any of these platforms)
Thanks
j
next prev parent reply other threads:[~2018-01-22 14:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 10:18 [PATCH 0/9] media: replace g/s_parm by g/s_frame_interval Hans Verkuil
2018-01-22 10:18 ` [PATCH 1/9] v4l2-common: create v4l2_g/s_parm_cap helpers Hans Verkuil
2018-01-22 10:28 ` Sakari Ailus
2018-01-22 10:34 ` Hans Verkuil
2018-01-22 10:18 ` [PATCH 2/9] media: convert g/s_parm to g/s_frame_interval in subdevs Hans Verkuil
2018-01-22 10:26 ` Sakari Ailus
2018-01-22 10:33 ` Hans Verkuil
2018-01-22 10:59 ` Sakari Ailus
2018-01-22 12:19 ` Hans Verkuil
2018-01-22 14:45 ` jacopo mondi [this message]
2018-01-22 14:48 ` Hans Verkuil
2018-01-22 14:53 ` jacopo mondi
2018-01-22 10:18 ` [PATCH 3/9] staging: atomisp: Kill subdev s_parm abuse Hans Verkuil
2018-01-22 10:18 ` [PATCH 4/9] staging: atomisp: i2c: Disable non-preview configurations Hans Verkuil
2018-01-22 10:18 ` [PATCH 5/9] staging: atomisp: i2c: Drop g_parm support in sensor drivers Hans Verkuil
2018-01-22 10:18 ` [PATCH 6/9] staging: atomisp: mt9m114: Drop empty s_parm callback Hans Verkuil
2018-01-22 10:18 ` [PATCH 7/9] staging: atomisp: Drop g_parm and s_parm subdev ops use Hans Verkuil
2018-01-22 10:18 ` [PATCH 8/9] v4l2-subdev.h: remove obsolete g/s_parm Hans Verkuil
2018-01-22 10:18 ` [PATCH 9/9] vidioc-g-parm.rst: also allow _MPLANE buffer types Hans Verkuil
2018-01-22 10:26 ` Sakari Ailus
2018-01-22 10:37 ` 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=20180122144542.GB13087@w540 \
--to=jacopo@jmondi.org \
--cc=hans.verkuil@cisco.com \
--cc=hverkuil@xs4all.nl \
--cc=jacopo+renesas@jmondi.org \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@linux.intel.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 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.