From: Kaaira Gupta <kgupta@es.iitr.ac.in>
To: "Helen Koike" <helen.koike@collabora.com>,
"Shuah Khan" <skhan@linuxfoundation.org>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
"Kieran Bingham" <kieran.bingham@ideasonboard.com>,
"Niklas Söderlund" <niklas.soderlund@ragnatech.se>
Cc: Kaaira Gupta <kgupta@es.iitr.ac.in>
Subject: [PATCH v2 0/3] media: vimc: Allow multiple capture devices to use the same sensor
Date: Fri, 24 Jul 2020 17:32:10 +0530 [thread overview]
Message-ID: <20200724120213.17119-1-kgupta@es.iitr.ac.in> (raw)
This is version 2 of the patch series posted by Niklas for allowing
multiple streams in VIMC.
The original series can be found here:
https://patchwork.kernel.org/cover/10948831/
This series adds support for two (or more) capture devices to be
connected to the same sensors and run simultaneously. Each capture device
can be started and stopped independent of each other.
Patch 1/3 and 2/3 deals with solving the issues that arises once two
capture devices can be part of the same pipeline. While 3/3 allows for
two capture devices to be part of the same pipeline and thus allows for
simultaneously use.
Changes since v1:
- All three patches rebased on latest media-tree.
Patch 3:
- Search for an entity with a non-NULL pipe instead of searching
for sensor. This terminates the search at output itself.
Kaaira Gupta (3):
media: vimc: Add usage count to subdevices
media: vimc: Serialize vimc_streamer_s_stream()
media: vimc: Join pipeline if one already exists
.../media/test-drivers/vimc/vimc-capture.c | 35 ++++++++++++++++++-
.../media/test-drivers/vimc/vimc-debayer.c | 8 +++++
drivers/media/test-drivers/vimc/vimc-scaler.c | 8 +++++
drivers/media/test-drivers/vimc/vimc-sensor.c | 9 ++++-
.../media/test-drivers/vimc/vimc-streamer.c | 23 +++++++-----
5 files changed, 73 insertions(+), 10 deletions(-)
--
2.17.1
next reply other threads:[~2020-07-24 12:02 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 12:02 Kaaira Gupta [this message]
2020-07-24 12:02 ` [PATCH v2 1/3] media: vimc: Add usage count to subdevices Kaaira Gupta
2020-07-24 12:02 ` [PATCH v2 2/3] media: vimc: Serialize vimc_streamer_s_stream() Kaaira Gupta
2020-07-24 12:02 ` [PATCH v2 3/3] media: vimc: Join pipeline if one already exists Kaaira Gupta
2020-07-28 12:24 ` Dafna Hirschfeld
2020-07-28 12:48 ` Kaaira Gupta
2020-07-29 10:58 ` Dafna Hirschfeld
2020-07-24 12:15 ` [PATCH v2 0/3] media: vimc: Allow multiple capture devices to use the same sensor Niklas Söderlund
2020-07-24 12:21 ` Kaaira Gupta
2020-07-27 14:31 ` Kieran Bingham
2020-07-27 17:54 ` Helen Koike
2020-07-28 11:39 ` Kaaira Gupta
2020-07-28 12:07 ` Dafna Hirschfeld
2020-07-28 14:00 ` Dafna Hirschfeld
2020-07-28 14:26 ` Kaaira Gupta
2020-07-29 13:05 ` Kieran Bingham
2020-07-29 13:16 ` Dafna Hirschfeld
2020-07-29 13:27 ` Kieran Bingham
2020-07-29 15:24 ` Dafna Hirschfeld
2020-07-31 17:22 ` Kaaira Gupta
2020-08-04 10:24 ` Kieran Bingham
2020-08-04 18:49 ` Kaaira Gupta
2020-08-04 18:52 ` Kaaira Gupta
2020-08-05 15:18 ` Helen Koike
2020-07-30 10:51 ` Laurent Pinchart
2020-07-30 18:09 ` Kaaira Gupta
2020-07-30 22:21 ` 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=20200724120213.17119-1-kgupta@es.iitr.ac.in \
--to=kgupta@es.iitr.ac.in \
--cc=helen.koike@collabora.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=niklas.soderlund@ragnatech.se \
--cc=skhan@linuxfoundation.org \
/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.