From: sashiko-bot@kernel.org
To: "Gaurav Suman" <gauravsuman007@gmail.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org,
media-ci@linuxtv.org
Subject: Re: [PATCH 1/8] dt-bindings: media: Add qcom,sm8150-camss
Date: Mon, 09 Nov 2026 22:56:33 +0000 [thread overview]
Message-ID: <sashiko-outbox-205776@kernel.org> (raw)
In-Reply-To: <20261109-sm8150-camera-v1-1-3d2e7b407516@gmail.com>
Thank you for your contribution! Sashiko AI review found 2 potential
issues to consider:
- [Medium] dt-bindings: media: qcom,sm8150-camss: wrong CSIPHY regulator
supply voltages
- [Low] dt-bindings: media: qcom,sm8150-camss: drop non-programmable
clock-lanes
--
commit 0fb4333890ec99f90c8e1d28d189ea7add0c4129
Author: Gaurav Suman <gauravsuman007@gmail.com>
dt-bindings: media: Add qcom,sm8150-camss
This commit adds the Device Tree binding schema for the Qualcomm SM8150
Camera Subsystem (CAMSS).
> diff --git a/Documentation/devicetree/bindings/media/qcom,sm8150-camss.yaml b/Documentation/devicetree/bindings/media/qcom,sm8150-camss.yaml
> new file mode 100644
> index 0000000000000..e13bcd8d48adf
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/media/qcom,sm8150-camss.yaml
> @@ -0,0 +1,389 @@
[ ... ]
> + vdd-csiphy-1p2-supply:
> + description:
> + Phandle to a 1.2V regulator supply to CSI PHYs.
> +
> + vdd-csiphy-1p8-supply:
> + description:
> + Phandle to a 1.8V regulator supply to CSI PHYs pll block.
[Severity: Medium]
Are these the right CSIPHY supply voltages for SM8150?
On SM8150 boards (such as sm8150-hdk.dts and sm8150-mtp.dts), the four CSI
PHY core rails (vdda_csi_0_0p9 through vdda_csi_3_0p9) are supplied by the
0.88V PM8150 LDO5 regulator (vreg_l5a_0p875), and the PLL supply on 3PH
CSIPHY hardware is 1.2V rather than 1.8V. Requiring 1.2V and 1.8V supplies
here (and wiring them to vreg_l3c_1p2 and vreg_l1c_1p8 in the example) leaves
the 0.88V CSIPHY core rail undescribed and unpowered.
> +
> + ports:
> + $ref: /schemas/graph.yaml#/properties/ports
> +
> + description:
> + CSI input ports.
> +
> + properties:
> + port@0:
> + $ref: /schemas/graph.yaml#/$defs/port-base
> + unevaluatedProperties: false
> + description:
> + Input port for receiving CSI data from CSIPHY0.
> +
> + properties:
> + endpoint:
> + $ref: video-interfaces.yaml#
> + unevaluatedProperties: false
> +
> + properties:
> + clock-lanes:
> + maxItems: 1
> +
> + data-lanes:
> + minItems: 1
> + maxItems: 4
[Severity: Low]
Should clock-lanes be dropped from port@0 through port@3 and from the
example below?
On Qualcomm 3PH CSIPHY hardware the clock lane position is fixed in
hardware and not programmable by the CAMSS driver, which is why commit
336136e197e2 ("media: dt-bindings: media: camss: Remove clock-lane
property") and commit b8ef764aff5be ("dt-bindings: media:
qcom,x1e80100-camss: Remove clock-lanes port property") removed it from the
other CAMSS bindings.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261109-sm8150-camera-v1-0-3d2e7b407516@gmail.com?part=1
next prev parent reply other threads:[~2026-11-09 22:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 22:38 [PATCH 0/8] Add SM8150 CAMSS and LG G8x ThinQ camera sensors Gaurav Suman via B4 Relay
2026-11-09 22:38 ` [PATCH 1/8] dt-bindings: media: Add qcom,sm8150-camss Gaurav Suman via B4 Relay
2026-11-09 22:56 ` sashiko-bot [this message]
2026-11-10 8:13 ` Krzysztof Kozlowski
2026-11-09 22:38 ` [PATCH 2/8] media: qcom: camss: Add SM8150 support Gaurav Suman via B4 Relay
2026-11-09 22:56 ` sashiko-bot
2026-11-10 0:00 ` Bryan O'Donoghue
2026-11-09 22:38 ` [PATCH 3/8] dt-bindings: media: i2c: Add Samsung S5K3M3 image sensor Gaurav Suman via B4 Relay
2026-11-09 22:43 ` sashiko-bot
2026-11-10 8:16 ` Krzysztof Kozlowski
2026-11-09 22:38 ` [PATCH 4/8] media: i2c: Add Samsung S5K3M3 image sensor driver Gaurav Suman via B4 Relay
2026-11-09 22:52 ` sashiko-bot
2026-11-10 0:04 ` Bryan O'Donoghue
2026-11-10 8:18 ` Krzysztof Kozlowski
2026-11-09 22:38 ` [PATCH 5/8] dt-bindings: media: i2c: Add Samsung S5KGD1 image sensor Gaurav Suman via B4 Relay
2026-11-10 8:18 ` Krzysztof Kozlowski
2026-11-09 22:38 ` [PATCH 6/8] media: i2c: Add Samsung S5KGD1 image sensor driver Gaurav Suman via B4 Relay
2026-11-09 22:54 ` sashiko-bot
2026-11-09 22:38 ` [PATCH 7/8] dt-bindings: media: i2c: Add ON Semiconductor LC898123F40 Gaurav Suman via B4 Relay
2026-11-10 8:20 ` Krzysztof Kozlowski
2026-11-09 22:38 ` [PATCH 8/8] media: i2c: Add ON Semiconductor LC898123F40 lens autofocus driver Gaurav Suman via B4 Relay
2026-11-09 22:49 ` sashiko-bot
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=sashiko-outbox-205776@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gauravsuman007@gmail.com \
--cc=media-ci@linuxtv.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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