From: sashiko-bot@kernel.org
To: "Pengyu Luo" <mitltlatltl@gmail.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: qcom: sc8280xp-x13s: Use predefined MCLK pinctrl
Date: Sun, 07 Jun 2026 16:10:06 +0000 [thread overview]
Message-ID: <20260607161007.6AB841F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260607160435.36546-2-mitltlatltl@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Silent reduction of camera MCLK drive strength from 16 mA to 6 mA.
--
commit 68374459d8e6941a056f52b1b8fa71811fd7137a
Author: Pengyu Luo <mitltlatltl@gmail.com>
arm64: dts: qcom: sc8280xp-x13s: Use predefined MCLK pinctrl
This commit switches the ThinkPad X13s to use the predefined MCLK pinctrl
configuration from the sc8280xp SoC DTSI. It drops the local MCLK pin
definition from the camera pinctrl node.
> diff --git a/arch/arm64/boot/dts/qcom/sc8280xp-lenovo-thinkpad-x13s.dts b/arch/arm64/boot/dts/qcom/sc8280xp-lenovo-thinkpad-x13s.dts
> index d84ca010ab9dc..1e256b16b3e6f 100644
> --- a/arch/arm64/boot/dts/qcom/sc8280xp-lenovo-thinkpad-x13s.dts
> +++ b/arch/arm64/boot/dts/qcom/sc8280xp-lenovo-thinkpad-x13s.dts
> @@ -674,8 +674,9 @@ camera@10 {
> reg = <0x10>;
>
> reset-gpios = <&tlmm 15 GPIO_ACTIVE_LOW>;
> +
> + pinctrl-0 = <&cam_rgb_default>, <&cam_mclk3_default>;
> pinctrl-names = "default";
> - pinctrl-0 = <&cam_rgb_default>;
>
> leds = <&privacy_led>;
> led-names = "privacy";
[ ... ]
> @@ -1552,13 +1553,6 @@ cam_indicator_en: cam-indicator-en-state {
> };
>
> cam_rgb_default: cam-rgb-default-state {
> - mclk-pins {
> - pins = "gpio17";
> - function = "cam_mclk";
> - drive-strength = <16>;
> - bias-disable;
> - };
> -
[Severity: High]
Does this unintentionally reduce the camera MCLK drive strength?
The commit message notes this is dropping a duplicate MCLK pin definition, but
the generic cam_mclk3_default definition in sc8280xp.dtsi now used by the
camera node defaults to a lower drive strength of 6 mA:
arch/arm64/boot/dts/qcom/sc8280xp.dtsi:
cam_mclk3_default: cam-mclk3-default-state {
pins = "gpio17";
function = "cam_mclk";
drive-strength = <6>;
bias-disable;
};
Reducing the drive capability from 16 mA to 6 mA for a high-frequency master
clock signal routed over long traces might degrade signal integrity.
Could this lead to intermittent or complete camera initialization failures on
this hardware?
> sc-rgb-xshut-n-pins {
> pins = "gpio15";
> function = "gpio";
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260607160435.36546-1-mitltlatltl@gmail.com?part=2
prev parent reply other threads:[~2026-06-07 16:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-07 16:04 [PATCH 1/2] arm64: dts: qcom: sc8280xp: Add camera MCLK pinctrl Pengyu Luo
2026-06-07 16:04 ` [PATCH 2/2] arm64: dts: qcom: sc8280xp-x13s: Use predefined " Pengyu Luo
2026-06-07 16:10 ` sashiko-bot [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=20260607161007.6AB841F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=mitltlatltl@gmail.com \
--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