From: sashiko-bot@kernel.org
To: "Xin Xu" <xxsemail@qq.com>
Cc: robh@kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: sm8250-xiaomi-elish: Remove camera_front_active pinctrl
Date: Fri, 10 Jul 2026 06:32:18 +0000 [thread overview]
Message-ID: <20260710063219.49ED11F000E9@smtp.kernel.org> (raw)
In-Reply-To: <tencent_AEB4238D8669271E5C1CD19C2C61A45AD108@qq.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Removal of explicit electrical pin configuration for camera reset GPIO
--
--- Patch [1]: [PATCH] arm64: dts: qcom: sm8250-xiaomi-elish: Remove camera_front_active pinctrl ---
commit 0022e4fa862c463785a16fefb223c9ad61f2fc67
Author: Xin Xu <xxsemail@qq.com>
arm64: dts: qcom: sm8250-xiaomi-elish: Remove camera_front_active pinctrl
This commit removes the camera_front_active pinctrl node and its reference,
stating that the GPIO 109 configuration duplicates the reset-gpios property.
> diff --git a/arch/arm64/boot/dts/qcom/sm8250-xiaomi-elish-common.dtsi b/arch/arm64/boot/dts/qcom/sm8250-xiaomi-elish-common.dtsi
> index 19aff83ecf7b6..26801d6a1ec5f 100644
> --- a/arch/arm64/boot/dts/qcom/sm8250-xiaomi-elish-common.dtsi
> +++ b/arch/arm64/boot/dts/qcom/sm8250-xiaomi-elish-common.dtsi
> @@ -570,7 +570,7 @@ camera_front: camera@10 {
>
> reset-gpios = <&tlmm 109 GPIO_ACTIVE_LOW>;
>
> - pinctrl-0 = <&cam_mclk3_default &camera_front_active>;
> + pinctrl-0 = <&cam_mclk3_default>;
> pinctrl-names = "default";
>
> orientation = <0>; /* Front facing */
[ ... ]
> @@ -947,13 +947,6 @@ pm8008_reset_default: pm8008-reset-default-state {
> bias-pull-up;
> };
>
> - camera_front_active: camera-front-active-state {
> - pins = "gpio109";
> - function = "gpio";
> - drive-strength = <2>;
> - bias-disable;
> - };
> -
[Severity: Medium]
Does removing this pinctrl node leave the pin without a guaranteed electrical
configuration?
The reset-gpios property configures pin routing and logical polarity, but it
doesn't apply explicit electrical properties like drive-strength and
bias-disable.
If the bootloader leaves a pull-up or pull-down resistor enabled on this GPIO,
could the GPIO output driver end up fighting it and causing constant power
leakage?
> wlan_en_state: wlan-default-state {
> pins = "gpio20";
> function = "gpio";
--
Sashiko AI review · https://sashiko.dev/#/patchset/tencent_AEB4238D8669271E5C1CD19C2C61A45AD108@qq.com?part=1
next prev parent reply other threads:[~2026-07-10 6:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 6:22 [PATCH] arm64: dts: qcom: sm8250-xiaomi-elish: Remove camera_front_active pinctrl Xin Xu
2026-07-10 6:32 ` sashiko-bot [this message]
2026-07-10 8:45 ` Konrad Dybcio
2026-07-10 12:25 ` Xin Xu
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=20260710063219.49ED11F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=xxsemail@qq.com \
/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