From: Jesse Casco <jesse.casco@gmail.com>
To: "Gjorgji Rosikopulos (Consultant)"
<gjorgji.rosikopulos@oss.qualcomm.com>
Cc: 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>,
Allan Siriani <allan@fatecpompeia.edu.br>,
linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 0/2] media: qcom: camss: Fix the X1E80100 lite CSID paths
Date: Fri, 20 Nov 2026 18:55:12 -0500 [thread overview]
Message-ID: <20261120235512.1230-1-jesse.casco@gmail.com> (raw)
In-Reply-To: <5485aa11-386e-4648-b27f-f4090bf90d66@oss.qualcomm.com>
On 11/20/2026 10:01 PM, Gjorgji Rosikopulos (Consultant) wrote:
> Just to note that my opinion is that CSID2 shall be removed from the
> resources since can not be used as of today. But others may share
> different opinion.
Hi Gjorgji,
Agreed, I'll drop CSID2 in v2. That also makes CSID n -> VFE n hold
again on X1E80100.
Jesse
prev parent reply other threads:[~2026-11-20 23:55 UTC|newest]
Thread overview: 11+ 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-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-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 [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=20261120235512.1230-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