From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>,
linux-media@vger.kernel.org,
Alain Volmat <alain.volmat@foss.st.com>,
Benjamin Mugnier <benjamin.mugnier@foss.st.com>,
hverkuil@xs4all.nl
Subject: Re: [PATCH 2/2] media: Documentation: Update {enable,disable}_streams documentation
Date: Tue, 17 Sep 2024 17:57:35 +0300 [thread overview]
Message-ID: <20240917145735.GE17350@pendragon.ideasonboard.com> (raw)
In-Reply-To: <61a0d763-2a6f-48f7-9439-3cc8102cb803@ideasonboard.com>
On Tue, Sep 17, 2024 at 05:16:25PM +0300, Tomi Valkeinen wrote:
> On 17/09/2024 16:00, Laurent Pinchart wrote:
> > On Tue, Sep 17, 2024 at 03:43:45PM +0300, Sakari Ailus wrote:
> >> Document the expected {enable,disable}_streams callback behaviour for
> >> drivers that are stream-unaware i.e. don't specify the
> >> V4L2_SUBDEV_CAP_STREAMS sub-device capability flat. In this specific case,
> >> the mask argument can be ignored.
> >
> > Wouldn't it be better to use BIT(0) in that case to simplifiy
> > interoperability with stream-aware devices ?
>
> The caller has to set BIT(0), but I think here the documentation is
> about the callee.
>
> If the driver is not stream aware and implements the callbacks, it will
> get BIT(0) as the mask parameter (do we enforce this?), but as there's
> nothing it can do with the parameter it "does not need to be concerned
> with the mask argument".
Right. I had misunderstood the patch.
> >> Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
> >> ---
> >> include/media/v4l2-subdev.h | 8 ++++++++
> >> 1 file changed, 8 insertions(+)
> >>
> >> diff --git a/include/media/v4l2-subdev.h b/include/media/v4l2-subdev.h
> >> index 3cc6b4a5935f..67a6e6ec58b8 100644
> >> --- a/include/media/v4l2-subdev.h
> >> +++ b/include/media/v4l2-subdev.h
> >> @@ -834,11 +834,19 @@ struct v4l2_subdev_state {
> >> * v4l2_subdev_init_finalize() at initialization time). Do not call
> >> * directly, use v4l2_subdev_enable_streams() instead.
> >> *
> >> + * Drivers that support only a single stream without setting the
> >> + * V4L2_SUBDEV_CAP_STREAMS sub-device capatility flag do not need to
s/capatility/capability/
Same below.
> >> + * be concerned with the mask argument.
How about "can ignore the mask argument" instead ? I interpreted as "not
need to be concerned with" from the point of view of the caller.
> >> + *
> >> * @disable_streams: Disable the streams defined in streams_mask on the given
> >> * source pad. Subdevs that implement this operation must use the active
> >> * state management provided by the subdev core (enabled through a call to
> >> * v4l2_subdev_init_finalize() at initialization time). Do not call
> >> * directly, use v4l2_subdev_disable_streams() instead.
> >> + *
> >> + * Drivers that support only a single stream without setting the
> >> + * V4L2_SUBDEV_CAP_STREAMS sub-device capatility flag do not need to
> >> + * be concerned with the mask argument.
> >> */
> >> struct v4l2_subdev_pad_ops {
> >> int (*enum_mbus_code)(struct v4l2_subdev *sd,
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2024-09-17 14:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-17 12:43 [PATCH 1/2] media: Documentation: Deprecate s_stream video op, update docs Sakari Ailus
2024-09-17 12:43 ` [PATCH 2/2] media: Documentation: Update {enable,disable}_streams documentation Sakari Ailus
2024-09-17 13:00 ` Laurent Pinchart
2024-09-17 13:17 ` Sakari Ailus
2024-09-17 14:16 ` Tomi Valkeinen
2024-09-17 14:57 ` Laurent Pinchart [this message]
2024-09-17 15:00 ` Tomi Valkeinen
2024-09-17 15:05 ` Sakari Ailus
2024-09-17 14:22 ` [PATCH 1/2] media: Documentation: Deprecate s_stream video op, update docs Tomi Valkeinen
2024-09-17 14:53 ` Sakari Ailus
2024-09-17 14:54 ` 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=20240917145735.GE17350@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=alain.volmat@foss.st.com \
--cc=benjamin.mugnier@foss.st.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@linux.intel.com \
--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 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.