From: <quic_mmitkov@quicinc.com>
To: <linux-media@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>,
<robert.foss@linaro.org>, <akapatra@quicinc.com>,
<jzala@quicinc.com>, <todor.too@gmail.com>
Cc: <agross@kernel.org>, <konrad.dybcio@somainline.org>,
<mchehab@kernel.org>, <bryan.odonoghue@linaro.org>,
<cgera@qti.qualcomm.com>, <gchinnab@quicinc.com>,
<ayasan@qti.qualcomm.com>, <laurent.pinchart@ideasonboard.com>,
Milen Mitkov <quic_mmitkov@quicinc.com>
Subject: [PATCH v7 0/4] media: camss: sm8250: Virtual channels support for SM8250
Date: Fri, 9 Dec 2022 11:40:33 +0200 [thread overview]
Message-ID: <20221209094037.1148-1-quic_mmitkov@quicinc.com> (raw)
From: Milen Mitkov <quic_mmitkov@quicinc.com>
For v7:
- Fix an issue with output state for different versions of the IFE
hardware (for platforms different from QRB5, e.g. QRB3).
For v6:
- Fix for a potential race condition in csid
- More detailed description on how to use/test this feature in
user-space in the last patch.
For v5:
- Use entity->use_count instead of s_stream subdev call ret code to
check if another instance of the pipeline is running. Prevents an
error on 6.1 and up, when stopping one of several simultaneous
instances.
- flush buffers instead of just returning if the pipeline didn't start.
For v4:
- fixes the warning reported by the kernel test robot
- tiny code change to enable the vc functionality with the partially-applied
multistream patches on linux-next (tested on tag:next-20221010)
For v3:
- setting the sink pad format on the CSID entity will now propagate the
format to the source pads to keep the subdev in a valid internal state.
- code syntax improvements
For v2:
- code syntax improvements
- The info print for the enabled VCs was demoted to a dbg print. Can be
enabled with dynamic debug, e.g.:
echo "file drivers/media/platform/qcom/camss/* +p" > /sys/kernel/debug/dynamic_debug/control
NOTE: These changes depend on the multistream series, that as of yet
is still not merged upstream. However, part of the
multistream patches are merged in linux-next (tested on
tag:next-20221010), including the patch that introduces the
video_device_pipeline_alloc_start() functionality. This allows
applying and using this series on linux-next without applying the
complete multistream set.
The CSID hardware on SM8250 can demux the input data stream into
maximum of 4 multiple streams depending on virtual channel (vc)
or data type (dt) configuration.
Situations in which demuxing is useful:
- HDR sensors that produce a 2-frame HDR output, e.g. a light and a dark frame
(the setup we used for testing, with the imx412 sensor),
or a 3-frame HDR output - light, medium-lit, dark frame.
- sensors with additional metadata that is streamed over a different
virtual channel/datatype.
- sensors that produce frames with multiple resolutions in the same pixel
data stream
With these changes, the CSID entity has, as it did previously, a single
sink port (0), and always exposes 4 source ports (1, 2,3, 4). The
virtual channel configuration is determined by which of the source ports
are linked to an output VFE line. For example, the link below will
configure the CSID driver to enable vc 0 and vc 1:
media-ctl -l '"msm_csid0":1->"msm_vfe0_rdi0":0[1]'
media-ctl -l '"msm_csid0":2->"msm_vfe0_rdi1":0[1]'
which will be demuxed and propagated into /dev/video0
and /dev/video1 respectively. With this, the userspace can use
any normal V4L2 client app to start/stop/queue/dequeue from these
video nodes. Tested with the yavta app.
The format of each RDI channel of the used VFE(s) (msm_vfe0_rdi0,
msm_vfe0_rdi1,...) must also be configured explicitly.
Note that in order to keep a valid internal subdevice state,
setting the sink pad format of the CSID subdevice will propagate
this format to the source pads. However, since the CSID hardware
can demux the input stream into several streams each of which can
be a different format, in that case each source pad's
format must be set individually, e.g.:
media-ctl -V '"msm_csid0":1[fmt:SRGGB10/3840x2160]'
media-ctl -V '"msm_csid0":2[fmt:SRGGB10/960x540]'
Milen Mitkov (4):
media: camss: sm8250: Virtual channels for CSID
media: camss: vfe: Reserve VFE lines on stream start and link to CSID
media: camss: vfe-480: Multiple outputs support for SM8250
media: camss: sm8250: Pipeline starting and stopping for multiple
virtual channels
.../platform/qcom/camss/camss-csid-gen2.c | 54 ++++++++++------
.../media/platform/qcom/camss/camss-csid.c | 44 +++++++++----
.../media/platform/qcom/camss/camss-csid.h | 11 +++-
.../media/platform/qcom/camss/camss-vfe-170.c | 4 +-
.../media/platform/qcom/camss/camss-vfe-480.c | 61 ++++++++++++-------
.../platform/qcom/camss/camss-vfe-gen1.c | 4 +-
drivers/media/platform/qcom/camss/camss-vfe.c | 1 +
.../media/platform/qcom/camss/camss-video.c | 21 ++++++-
drivers/media/platform/qcom/camss/camss.c | 2 +-
9 files changed, 138 insertions(+), 64 deletions(-)
--
2.37.3
next reply other threads:[~2022-12-09 9:41 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 9:40 quic_mmitkov [this message]
2022-12-09 9:40 ` [PATCH v7 1/4] media: camss: sm8250: Virtual channels for CSID quic_mmitkov
2022-12-09 9:40 ` [PATCH v7 2/4] media: camss: vfe: Reserve VFE lines on stream start and link to CSID quic_mmitkov
2022-12-09 9:40 ` [PATCH v7 3/4] media: camss: vfe-480: Multiple outputs support for SM8250 quic_mmitkov
2022-12-09 9:40 ` [PATCH v7 4/4] media: camss: sm8250: Pipeline starting and stopping for multiple virtual channels quic_mmitkov
2022-12-09 16:17 ` [PATCH v7 0/4] media: camss: sm8250: Virtual channels support for SM8250 Bryan O'Donoghue
2023-01-05 8:37 ` Milen Mitkov (Consultant)
2023-01-05 18:43 ` Bryan O'Donoghue
2023-01-06 9:49 ` Milen Mitkov (Consultant)
2023-01-08 2:53 ` Laurent Pinchart
2023-01-08 2:51 ` Laurent Pinchart
2023-01-08 2:54 ` Laurent Pinchart
2023-01-10 10:25 ` Milen Mitkov (Consultant)
2023-01-31 9:00 ` Milen Mitkov (Consultant)
2023-02-20 12:18 ` Milen Mitkov (Consultant)
2023-02-20 12:26 ` Bryan O'Donoghue
2023-02-21 8:44 ` Milen Mitkov (Consultant)
2023-03-31 6:20 ` Azam Sadiq Pasha Kapatrala Syed
2023-03-31 8:07 ` Bryan O'Donoghue
[not found] ` <7b3cb8a6-8306-f001-5701-af3b482421e9@quicinc.com>
2023-04-03 9:16 ` Bryan O'Donoghue
2023-04-03 9:20 ` Milen Mitkov (Consultant)
2023-04-03 9:36 ` Bryan O'Donoghue
2023-04-03 11:01 ` Milen Mitkov (Consultant)
2023-04-03 12:10 ` Bryan O'Donoghue
2023-04-03 12:16 ` Milen Mitkov (Consultant)
2023-04-04 0:06 ` Bryan O'Donoghue
[not found] <458d2d7d-74bd-dcb0-6cb7-74fe6e527131@linaro.org>
[not found] ` <c8420c54-4f2b-c259-c5c3-29078ac0c9e6@linaro.org>
2023-04-07 15:14 ` Azam Sadiq Pasha Kapatrala Syed
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=20221209094037.1148-1-quic_mmitkov@quicinc.com \
--to=quic_mmitkov@quicinc.com \
--cc=agross@kernel.org \
--cc=akapatra@quicinc.com \
--cc=ayasan@qti.qualcomm.com \
--cc=bryan.odonoghue@linaro.org \
--cc=cgera@qti.qualcomm.com \
--cc=gchinnab@quicinc.com \
--cc=jzala@quicinc.com \
--cc=konrad.dybcio@somainline.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robert.foss@linaro.org \
--cc=todor.too@gmail.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