From: sashiko-bot@kernel.org
To: "Nihal Kumar Gupta" <nihal.gupta@oss.qualcomm.com>
Cc: imx@lists.linux.dev, conor+dt@kernel.org, Frank.Li@kernel.org,
robh@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v5 2/6] arm64: dts: qcom: shikra: Add CAMSS node
Date: Mon, 13 Jul 2026 09:39:19 +0000 [thread overview]
Message-ID: <20260713093919.B71F41F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260713-shikra-camss-review-v5-2-db53be15dc4f@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The `camss@5c11000` node is placed out of order in `shikra.dtsi`, violating device tree sorting rules.
--
--- Patch [2]: [PATCH v5 2/6] arm64: dts: qcom: shikra: Add CAMSS node ---
commit 3b1defa09283750cdb86a9b19398c488f2a5fdb0
Author: Nihal Kumar Gupta <nihal.gupta@oss.qualcomm.com>
arm64: dts: qcom: shikra: Add CAMSS node
This patch adds the Camera Subsystem (CAMSS) node for Shikra. It specifies
that Shikra shares the same IP as QCM2290 but drops CDM and OPE blocks,
requiring only a single IOMMU context bank.
> diff --git a/arch/arm64/boot/dts/qcom/shikra.dtsi b/arch/arm64/boot/dts/qcom/shikra.dtsi
> index 4e5bc9e17c8ed..6335caca32980 100644
> --- a/arch/arm64/boot/dts/qcom/shikra.dtsi
> +++ b/arch/arm64/boot/dts/qcom/shikra.dtsi
> @@ -604,6 +604,106 @@ opp-384000000 {
> };
> };
>
> + camss: camss@5c11000 {
> + compatible = "qcom,shikra-camss", "qcom,qcm2290-camss";
[Severity: Low]
Could this node be placed out of order?
Device tree node unit-addresses are generally sorted numerically, but here
camss@5c11000 is placed before the geniqup@4ac0000 node, which breaks the
numerical sorting under the soc node.
[ ... ]
> + };
> +
> qupv3_0: geniqup@4ac0000 {
> compatible = "qcom,geni-se-qup";
> reg = <0x0 0x04ac0000 0x0 0x2000>;
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260713-shikra-camss-review-v5-0-db53be15dc4f@oss.qualcomm.com?part=2
next prev parent reply other threads:[~2026-07-13 9:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 9:28 [PATCH v5 0/6] Add CAMSS and IMX577 sensor support for Shikra EVK Nihal Kumar Gupta
2026-07-13 9:28 ` [PATCH v5 1/6] dt-bindings: media: qcom: Add Shikra CAMSS compatible Nihal Kumar Gupta
2026-07-13 9:41 ` sashiko-bot
2026-07-13 10:38 ` Nihal Kumar Gupta
2026-07-13 9:28 ` [PATCH v5 2/6] arm64: dts: qcom: shikra: Add CAMSS node Nihal Kumar Gupta
2026-07-13 9:39 ` sashiko-bot [this message]
2026-07-13 11:50 ` Nihal Kumar Gupta
2026-07-13 9:28 ` [PATCH v5 3/6] arm64: dts: qcom: shikra: Add CCI definitions Nihal Kumar Gupta
2026-07-13 9:28 ` [PATCH v5 4/6] arm64: dts: qcom: shikra: Add pin configuration for mclks Nihal Kumar Gupta
2026-07-13 9:28 ` [PATCH v5 5/6] arm64: dts: qcom: shikra-cqm-cqs-evk-imx577-camera: Add DT overlay Nihal Kumar Gupta
2026-07-13 9:28 ` [PATCH v5 6/6] arm64: dts: qcom: shikra-iqs-evk-imx577-camera: " Nihal Kumar Gupta
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=20260713093919.B71F41F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=nihal.gupta@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