From: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
To: Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil@xs4all.nl>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Umang Jain <umang.jain@ideasonboard.com>
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Subject: [PATCH 0/4] media: subdev: Improve stream enable/disable machinery
Date: Thu, 04 Apr 2024 13:49:59 +0300 [thread overview]
Message-ID: <20240404-enable-streams-impro-v1-0-1017a35bbe07@ideasonboard.com> (raw)
This series works on the .s_stream, .enable_streams, .disable_streams
related code:
"media: subdev: Add checks for subdev features" adds check to verify
that the subdevs implement the proper mix of the above ops.
"media: subdev: Fix use of sd->enabled_streams in call_s_stream()" fixes
somewhat questionable use of sd->enabled_streams in call_s_stream().
"media: subdev: Improve v4l2_subdev_enable/disable_streams_fallback"
drops the restriction of supporting only a single source pads, and
prepares the way for the following patch.
"media: subdev: Support enable/disable_streams for non-streams subdevs"
makes it possible for non-streams subdevs to use .enable_streams and
.disable_streams, deprecating the earlier patch "[PATCH] media:
v4l2-subdev: Support enable/disable_streams for single-pad subdevs".
I have tested this on RPi5 with multiple streams, but I still need to
figure out ways to test the other scenarios.
Tomi
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
---
Tomi Valkeinen (4):
media: subdev: Add checks for subdev features
media: subdev: Fix use of sd->enabled_streams in call_s_stream()
media: subdev: Improve v4l2_subdev_enable/disable_streams_fallback
media: subdev: Support enable/disable_streams for non-streams subdevs
drivers/media/v4l2-core/v4l2-subdev.c | 189 +++++++++++++++++++++++-----------
include/media/v4l2-subdev.h | 11 +-
2 files changed, 133 insertions(+), 67 deletions(-)
---
base-commit: b82779648dfd3814df4e381f086326ec70fd791f
change-id: 20240404-enable-streams-impro-db8bcd898471
Best regards,
--
Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
next reply other threads:[~2024-04-04 10:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 10:49 Tomi Valkeinen [this message]
2024-04-04 10:50 ` [PATCH 1/4] media: subdev: Add checks for subdev features Tomi Valkeinen
2024-04-04 11:09 ` Sakari Ailus
2024-04-04 11:30 ` Tomi Valkeinen
2024-04-04 10:50 ` [PATCH 2/4] media: subdev: Fix use of sd->enabled_streams in call_s_stream() Tomi Valkeinen
2024-04-04 13:00 ` Laurent Pinchart
2024-04-04 13:06 ` Tomi Valkeinen
2024-04-04 10:50 ` [PATCH 3/4] media: subdev: Improve v4l2_subdev_enable/disable_streams_fallback Tomi Valkeinen
2024-04-04 12:18 ` Sakari Ailus
2024-04-04 12:38 ` Tomi Valkeinen
2024-04-04 13:06 ` Laurent Pinchart
2024-04-04 13:47 ` Tomi Valkeinen
2024-04-04 14:25 ` Laurent Pinchart
2024-04-05 9:12 ` Tomi Valkeinen
2024-04-04 10:50 ` [PATCH 4/4] media: subdev: Support enable/disable_streams for non-streams subdevs Tomi Valkeinen
2024-04-04 13:08 ` 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=20240404-enable-streams-impro-v1-0-1017a35bbe07@ideasonboard.com \
--to=tomi.valkeinen@ideasonboard.com \
--cc=hverkuil@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=umang.jain@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
all inboxes | Powered by JetHome®