From: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
To: bod@kernel.org, Robert Foss <rfoss@kernel.org>,
Todor Tomov <todor.too@gmail.com>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil@kernel.org>,
Loic Poulain <loic.poulain@oss.qualcomm.com>,
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>
Cc: linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v3 2/5] media: qcom: camss: Fix RDI streaming for CSID 340
Date: Thu, 9 Apr 2026 18:53:16 +0300 [thread overview]
Message-ID: <d3c22f40-28af-4ba5-90e4-61643ad6d82f@linaro.org> (raw)
In-Reply-To: <20260407-camss-rdi-fix-v3-2-08f72d1f3442@kernel.org>
On 4/7/26 13:34, bod@kernel.org wrote:
> From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
>
> Fix streaming from CSIDn RDI1 and RDI2 to VFEn RDI1 and RDI2. A pattern we
> have replicated throughout CAMSS where we use the VC number to populate
> both the VC fields and port fields of the CSID means that in practice only
> VC = 0 on CSIDn:RDI0 to VFEn:RDI0 works.
>
> Fix that for CSID 340 by separating VC and port. Fix to VC zero as a bugfix
> we will look to properly populate the VC field with follow on patches
> later.
>
> Fixes: f0fc808a466a ("media: qcom: camss: Add CSID 340 support")
> Cc: stable@vger.kernel.org
> Signed-off-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Reviewed-by: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
--
Best wishes,
Vladimir
next prev parent reply other threads:[~2026-04-09 15:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-07 10:34 [PATCH v3 0/5] media: qcom: camss: Fix RDI streaming for various CSIDs bod
2026-04-07 10:34 ` [PATCH v3 1/5] media: qcom: camss: Fix RDI streaming for CSID 680 bod
2026-04-07 13:28 ` Loic Poulain
2026-04-09 15:52 ` Vladimir Zapolskiy
2026-04-07 10:34 ` [PATCH v3 2/5] media: qcom: camss: Fix RDI streaming for CSID 340 bod
2026-04-07 13:28 ` Loic Poulain
2026-04-09 15:53 ` Vladimir Zapolskiy [this message]
2026-04-07 10:34 ` [PATCH v3 3/5] media: qcom: camss: Fix RDI streaming for CSID GEN2 bod
2026-04-07 13:29 ` Loic Poulain
2026-04-09 15:53 ` Vladimir Zapolskiy
2026-04-07 10:34 ` [PATCH v3 4/5] media: qcom: camss: Fix RDI streaming for CSID GEN3 bod
2026-04-07 13:29 ` Loic Poulain
2026-04-09 15:54 ` Vladimir Zapolskiy
2026-04-24 21:49 ` Vijay Kumar Tumati
2026-04-07 10:34 ` [PATCH v3 5/5] media: qcom: camss: csid: Rename en_vc to en_port bod
2026-04-07 13:30 ` Loic Poulain
2026-04-09 15:54 ` Vladimir Zapolskiy
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=d3c22f40-28af-4ba5-90e4-61643ad6d82f@linaro.org \
--to=vladimir.zapolskiy@linaro.org \
--cc=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 \
/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®