From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-media@vger.kernel.org, tomi.valkeinen@ideasonboard.com,
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 13:17:54 +0000 [thread overview]
Message-ID: <ZumBghexAr_n5_hs@kekkonen.localdomain> (raw)
In-Reply-To: <20240917130047.GC17350@pendragon.ideasonboard.com>
Hi Laurent,
On Tue, Sep 17, 2024 at 04:00:47PM +0300, 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 ?
That's indeed the current implementation.
--
Regards,
Sakari Ailus
next prev parent reply other threads:[~2024-09-17 20:24 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 [this message]
2024-09-17 14:16 ` Tomi Valkeinen
2024-09-17 14:57 ` Laurent Pinchart
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=ZumBghexAr_n5_hs@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=alain.volmat@foss.st.com \
--cc=benjamin.mugnier@foss.st.com \
--cc=hverkuil@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 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.