From: Jesse Casco <jesse.casco@gmail.com>
To: Allan Siriani <allan@fatecpompeia.edu.br>
Cc: "Gjorgji Rosikopulos (Consultant)"
<gjorgji.rosikopulos@oss.qualcomm.com>,
Loic Poulain <loic.poulain@oss.qualcomm.com>,
Bryan O'Donoghue <bod@kernel.org>,
Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Nihal Kumar Gupta <nihal.gupta@oss.qualcomm.com>,
linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 2/2] media: qcom: camss: Map each CSID to the VFE it feeds
Date: Sat, 21 Nov 2026 19:28:00 -0500 [thread overview]
Message-ID: <20261122002800.41569-1-jesse.casco@gmail.com> (raw)
In-Reply-To: <20261120220025.56887-1-allan@fatecpompeia.edu.br>
On Fri, Nov 20, 2026 at 07:00:25PM -0300, Allan Siriani wrote:
> I'll drop it if the parent is resolved from the link as in Jesse's 2/2.
Hi Allan, Gjorgji, and Loic,
Allan, my 2/2 mapped CSIDs to VFEs by index, not from the link, so
MSM8916 CSID1 would still fail. v2 drops CSID2 instead, as Gjorgji
suggested on 0/2, and leaves vfe_parent_dev_ops_get() alone, so please
keep your patch.
Loic, every CSID still links to every lite and full VFE today. I can
add a patch to v2 that skips links between lite and full blocks, but I
can only test Glymur. Are they never connected on any of the non-ISPIF
SoCs?
Jesse
next prev parent reply other threads:[~2026-11-22 0:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-20 17:40 [PATCH 0/2] media: qcom: camss: Fix the X1E80100 lite CSID paths Jesse Casco
2026-11-20 17:40 ` [PATCH 1/2] media: qcom: camss: x1e80100: Use the lite clocks for the lite CSIDs Jesse Casco
2026-11-20 19:29 ` Loic Poulain
2026-11-21 9:44 ` Bryan O'Donoghue
2026-11-20 17:40 ` [PATCH 2/2] media: qcom: camss: Map each CSID to the VFE it feeds Jesse Casco
2026-11-20 19:39 ` Loic Poulain
2026-11-20 19:56 ` Gjorgji Rosikopulos (Consultant)
2026-11-20 20:32 ` Gjorgji Rosikopulos (Consultant)
2026-11-20 20:51 ` Gjorgji Rosikopulos (Consultant)
2026-11-20 22:00 ` Allan Siriani
2026-11-22 0:28 ` Jesse Casco [this message]
2026-11-20 20:01 ` [PATCH 0/2] media: qcom: camss: Fix the X1E80100 lite CSID paths Gjorgji Rosikopulos (Consultant)
2026-11-20 23:55 ` Jesse Casco
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=20261122002800.41569-1-jesse.casco@gmail.com \
--to=jesse.casco@gmail.com \
--cc=allan@fatecpompeia.edu.br \
--cc=bod@kernel.org \
--cc=gjorgji.rosikopulos@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=loic.poulain@oss.qualcomm.com \
--cc=mchehab@kernel.org \
--cc=nihal.gupta@oss.qualcomm.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