From: sashiko-bot@kernel.org
To: "Hangxiang Ma" <hangxiang.ma@oss.qualcomm.com>
Cc: robh@kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 3/3] arm64: dts: qcom: sm8750: Add camera MCLK pinctrl
Date: Tue, 19 May 2026 07:52:17 +0000 [thread overview]
Message-ID: <20260519075218.11318C2BCB3@smtp.kernel.org> (raw)
In-Reply-To: <20260519-pakala-camera-v1-3-b6d897864916@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Incorrect pinctrl function names `cam_asc_mclk2` and `cam_asc_mclk4` used for camera MCLK on pins 91 and 93.
--
commit e6d2727b68fe7979bbe116baa48b879e9333356a
Author: Hangxiang Ma <hangxiang.ma@oss.qualcomm.com>
arm64: dts: qcom: sm8750: Add camera MCLK pinctrl
This commit defines pinctrl definitions to enable camera master clocks on
SM8750.
> diff --git a/arch/arm64/boot/dts/qcom/sm8750.dtsi b/arch/arm64/boot/dts/qcom/sm8750.dtsi
> index e45f0d33714c5..f1e34d2860beb 100644
> --- a/arch/arm64/boot/dts/qcom/sm8750.dtsi
> +++ b/arch/arm64/boot/dts/qcom/sm8750.dtsi
[ ... ]
> @@ -3850,6 +3850,62 @@ tlmm: pinctrl@f100000 {
[ ... ]
> + cam2_default: cam2-default-state {
> + pins = "gpio91";
> + function = "cam_asc_mclk2";
Is this function name correct? The pinctrl subsystem relies on strict
string matching to map devicetree functions to driver functions.
According to the SM8750 pinctrl driver and bindings, the function for
this pin appears to be defined as cam_aon_mclk2. Using a non-existent name
will cause devicetree schema validation to fail and result in runtime errors,
preventing the camera clock from being configured.
> + drive-strength = <2>;
> + bias-disable;
> + };
[ ... ]
> + cam4_default: cam4-default-state {
> + pins = "gpio93";
> + function = "cam_asc_mclk4";
Does this function also need to be updated to cam_aon_mclk4?
> + drive-strength = <2>;
> + bias-disable;
> + };
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260519-pakala-camera-v1-0-b6d897864916@oss.qualcomm.com?part=3
prev parent reply other threads:[~2026-05-19 7:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 7:17 [PATCH 0/3] Add CCI and CAMSS support for SM8750 Hangxiang Ma
2026-05-19 7:17 ` [PATCH 1/3] arm64: dts: qcom: sm8750: Add camss node Hangxiang Ma
2026-05-19 7:29 ` sashiko-bot
2026-05-19 7:17 ` [PATCH 2/3] arm64: dts: qcom: sm8750: Add CCI definitions Hangxiang Ma
2026-05-19 7:17 ` [PATCH 3/3] arm64: dts: qcom: sm8750: Add camera MCLK pinctrl Hangxiang Ma
2026-05-19 7:52 ` 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=20260519075218.11318C2BCB3@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hangxiang.ma@oss.qualcomm.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