From: Anusha Arun Nandi <anusha.nandi@oss.qualcomm.com>
To: david@ixit.cz, andersson@kernel.org, konradybcio@kernel.org,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
bod@kernel.org, vladimir.zapolskiy@linaro.org,
loic.poulain@oss.qualcomm.com, mchehab@kernel.org
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
gjorgji.rosikopulos@oss.qualcomm.com,
jigarkumar.zala@oss.qualcomm.com,
hariram.purushothaman@oss.qualcomm.com, akapatra@quicinc.com,
bryan.odonoghue@linaro.org, linux-media@vger.kernel.org,
krzysztof.kozlowski@oss.qualcomm.com, daniel@quora.org,
konrad.dybcio@oss.qualcomm.com, christopher.obbard@linaro.org,
alex.vinarskis@gmail.com
Subject: [PATCH 0/2] media: qcom: camss: track PHY type and scale link frequency for C-PHY
Date: Fri, 16 Oct 2026 20:52:19 -0700 [thread overview]
Message-ID: <20261017035221.3816464-1-anusha.nandi@oss.qualcomm.com> (raw)
This series lays the CAMSS-side groundwork for MIPI C-PHY sensors.
Patch 1 records whether a CSIPHY endpoint is D-PHY or C-PHY from its
device-tree bus-type property (instead of rejecting anything that
isn't D-PHY), storing it in struct csiphy_lanes_cfg.
Patch 2 threads that PHY type through to link-frequency calculation:
camss_get_link_freq() gains a cphy parameter and scales its per-lane
divisor to match C-PHY's 16-bits-per-7-symbols encoding (vs. D-PHY's
1 bit/symbol), and the CSID gen3 RX front-end's CSI2_RX_CFG0 register
is programmed with the matching PHY_TYPE_SEL bit so C-PHY streams are
actually decoded as C-PHY instead of silently defaulting to D-PHY.
Referenced using David's C-PHY support(v9)
Link: https://lore.kernel.org/all/20260617-qcom-cphy-v9-0-83da8a8e4e44@ixit.cz/
Depends-on: https://lore.kernel.org/all/20261017001116.2318647-1-anusha.nandi@oss.qualcomm.com/
Depends-on: https://lore.kernel.org/all/20261016235502.2274268-1-anusha.nandi@oss.qualcomm.com/
David Heidelberg (2):
media: qcom: camss: csiphy: record PHY type from device-tree bus-type
media: qcom: camss: account for C-PHY when calculating link frequency
Anusha Arun Nandi (2):
media: qcom: camss: csiphy: record PHY type from device-tree bus-type
media: qcom: camss: account for C-PHY when calculating link frequency
.../platform/qcom/camss/camss-csid-gen3.c | 2 ++
.../media/platform/qcom/camss/camss-csid.c | 4 ++-
.../media/platform/qcom/camss/camss-csid.h | 1 +
.../media/platform/qcom/camss/camss-csiphy.c | 8 +++---
.../media/platform/qcom/camss/camss-csiphy.h | 2 ++
drivers/media/platform/qcom/camss/camss.c | 25 +++++++++++++++----
drivers/media/platform/qcom/camss/camss.h | 2 +-
7 files changed, 34 insertions(+), 10 deletions(-)
Best regards,
--
Anusha Arun Nandi <anusha.nandi@oss.qualcomm.com>
--
2.34.1
next reply other threads:[~2026-10-17 3:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-17 3:52 Anusha Arun Nandi [this message]
2026-10-17 3:52 ` [PATCH 1/2] media: qcom: camss: csiphy: record PHY type from device-tree bus-type Anusha Arun Nandi
2026-10-17 3:52 ` [PATCH 2/2] media: qcom: camss: account for C-PHY when calculating link frequency Anusha Arun Nandi
2026-10-17 10:12 ` George Neacsu
2026-10-17 17:30 ` [PATCH 0/2] media: qcom: camss: track PHY type and scale link frequency for C-PHY Nihal Kumar Gupta
2026-10-17 17:35 ` Krzysztof Kozlowski
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=20261017035221.3816464-1-anusha.nandi@oss.qualcomm.com \
--to=anusha.nandi@oss.qualcomm.com \
--cc=akapatra@quicinc.com \
--cc=alex.vinarskis@gmail.com \
--cc=andersson@kernel.org \
--cc=bod@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=christopher.obbard@linaro.org \
--cc=conor+dt@kernel.org \
--cc=daniel@quora.org \
--cc=david@ixit.cz \
--cc=devicetree@vger.kernel.org \
--cc=gjorgji.rosikopulos@oss.qualcomm.com \
--cc=hariram.purushothaman@oss.qualcomm.com \
--cc=jigarkumar.zala@oss.qualcomm.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--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=robh@kernel.org \
--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
all inboxes | Powered by JetHome®