From: Bryan O'Donoghue <bod@kernel.org>
To: Loic Poulain <loic.poulain@oss.qualcomm.com>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Cc: Robert Foss <rfoss@kernel.org>, Todor Tomov <todor.too@gmail.com>,
Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil@kernel.org>,
Hans Verkuil <hverkuil+cisco@kernel.org>,
Gjorgji Rosikopulos <quic_grosikop@quicinc.com>,
Milen Mitkov <quic_mmitkov@quicinc.com>,
Depeng Shao <quic_depengs@quicinc.com>,
Yongsheng Li <quic_yon@quicinc.com>,
linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 0/5] media: qcom: camss: Fix RDI streaming for various CSIDs
Date: Tue, 7 Apr 2026 10:34:18 +0100 [thread overview]
Message-ID: <1f839244-ff46-4b9e-bb93-65785ee8bb2c@kernel.org> (raw)
In-Reply-To: <CAFEp6-1HVph_+278jXCb-G-XDc=Bg1X0y9hSq79qr6WG+nJ3bQ@mail.gmail.com>
On 07/04/2026 09:49, Loic Poulain wrote:
> Okay, then that does reduce the usefulness somewhat... Another point I
> hadn’t initially considered is that we may also want to support
> different data types on the same VC. For example, metadata, stats, and
> image data could be transmitted over the same VC/stream? That seems
> like a valid use case enabled by your fix, and it might be worth
> explicitly mentioning it.
Yes true you can also separate out based on DT.
We could have different data-types on the same VC but of course you'd
see the DT field in data-stream change and then we'd route that to a
different rdi on the VFE.
Should be possible to interpret that data from the streams API and route
but it is indeed VC+DT to vfe_rdiX where both determine X not just the VC.
---
bod
prev parent reply other threads:[~2026-04-07 9:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-06 21:55 [PATCH 0/5] media: qcom: camss: Fix RDI streaming for various CSIDs bod
2026-04-06 21:55 ` [PATCH 1/5] media: qcom: camss: Fix RDI streaming for CSID 680 bod
2026-04-06 22:41 ` Vladimir Zapolskiy
2026-04-07 7:43 ` Bryan O'Donoghue
2026-04-06 21:55 ` [PATCH 2/5] media: qcom: camss: Fix RDI streaming for CSID 340 bod
2026-04-06 21:55 ` [PATCH 3/5] media: qcom: camss: Fix RDI streaming for CSID GEN2 bod
2026-04-06 21:55 ` [PATCH 4/5] media: qcom: camss: Fix RDI streaming for CSID GEN3 bod
2026-04-07 8:16 ` [PATCH 0/5] media: qcom: camss: Fix RDI streaming for various CSIDs Loic Poulain
2026-04-07 8:36 ` Bryan O'Donoghue
2026-04-07 8:49 ` Loic Poulain
2026-04-07 9:34 ` Bryan O'Donoghue [this message]
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=1f839244-ff46-4b9e-bb93-65785ee8bb2c@kernel.org \
--to=bod@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=hverkuil+cisco@kernel.org \
--cc=hverkuil@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=loic.poulain@oss.qualcomm.com \
--cc=mchehab@kernel.org \
--cc=quic_depengs@quicinc.com \
--cc=quic_grosikop@quicinc.com \
--cc=quic_mmitkov@quicinc.com \
--cc=quic_yon@quicinc.com \
--cc=rfoss@kernel.org \
--cc=stable@vger.kernel.org \
--cc=todor.too@gmail.com \
--cc=vladimir.zapolskiy@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox