From: sashiko-bot@kernel.org
To: "Hangxiang Ma" <hangxiang.ma@oss.qualcomm.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org,
krzk+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH 1/3] arm64: dts: qcom: kaanapali: Add camss node
Date: Fri, 08 May 2026 19:31:53 +0000 [thread overview]
Message-ID: <20260508193154.63486C2BCB0@smtp.kernel.org> (raw)
In-Reply-To: <20260508-knp-camera-v1-1-a18e289163fd@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The commit adds a new compatible string 'qcom,kaanapali-camss' without providing the corresponding YAML device tree binding schema.
--
commit a3fc6582c63ecf6be414df632ff7d8a517115d29
Author: Hangxiang Ma <hangxiang.ma@oss.qualcomm.com>
arm64: dts: qcom: kaanapali: Add camss node
This commit adds the camss device tree node for the Kaanapali camera
subsystem, defining its registers, clocks, interrupts, interconnects,
and power domains.
> diff --git a/arch/arm64/boot/dts/qcom/kaanapali.dtsi b/arch/arm64/boot/dts/qcom/kaanapali.dtsi
> index 7cc326aa1a1aa..9d8aee202797f 100644
> --- a/arch/arm64/boot/dts/qcom/kaanapali.dtsi
> +++ b/arch/arm64/boot/dts/qcom/kaanapali.dtsi
> @@ -3138,6 +3138,207 @@ opp-202000000 {
> };
> };
>
> + camss: isp@9253000 {
> + compatible = "qcom,kaanapali-camss";
Is there a corresponding YAML device tree binding patch for this new
compatible string?
Without the binding schema for qcom,kaanapali-camss, dt_binding_check
cannot validate the hardware description. Should the schema be included
in this patch series to ensure the node properties can be verified?
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260508-knp-camera-v1-0-a18e289163fd@oss.qualcomm.com?part=1
next prev parent reply other threads:[~2026-05-08 19:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 8:36 [PATCH 0/3] Add CCI and CAMSS support for Kaanapali Hangxiang Ma
2026-05-08 8:36 ` [PATCH 1/3] arm64: dts: qcom: kaanapali: Add camss node Hangxiang Ma
2026-05-08 10:45 ` Vladimir Zapolskiy
2026-05-08 19:31 ` sashiko-bot [this message]
2026-05-08 8:36 ` [PATCH 2/3] arm64: dts: qcom: kaanapali: Add CCI definitions Hangxiang Ma
2026-05-08 10:44 ` Vladimir Zapolskiy
2026-05-08 8:36 ` [PATCH 3/3] arm64: dts: qcom: kaanapali: Add camera MCLK pinctrl Hangxiang Ma
2026-05-08 10:40 ` Vladimir Zapolskiy
2026-05-08 19:50 ` 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=20260508193154.63486C2BCB0@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=krzk+dt@kernel.org \
--cc=robh@kernel.org \
--cc=sashiko@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.