Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Wangao Wang" <wangao.wang@oss.qualcomm.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v8 4/5] arm64: dts: qcom: purwa: Override Iris clocks and operating points
Date: Fri, 29 May 2026 08:55:44 +0000	[thread overview]
Message-ID: <20260529085546.24FEB1F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260529-enable_iris_on_purwa-v8-4-b1b9670459ab@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The device tree references an undefined macro `VIDEO_CC_MVS0_BSE_CLK`, which will cause a build failure.
--

commit b94ef34ae2cd7814137efba66c178dd0760ea44d
Author: Wangao Wang <wangao.wang@oss.qualcomm.com>

arm64: dts: qcom: purwa: Override Iris clocks and operating points

This commit modifies the device tree for the Purwa platform to override the
Iris clocks and operating points. It provides a new OPP table specific to the
X1P42100 platform to ensure correct performance levels.

> diff --git a/arch/arm64/boot/dts/qcom/purwa.dtsi b/arch/arm64/boot/dts/qcom/purwa.dtsi
> index 9ab4f26b35f29..b842ce5e7262e 100644
> --- a/arch/arm64/boot/dts/qcom/purwa.dtsi
> +++ b/arch/arm64/boot/dts/qcom/purwa.dtsi

[ ... ]

> @@ -157,6 +158,55 @@ &gpucc {
>  	compatible = "qcom,x1p42100-gpucc";
>  };
>  
> +&iris {
> +	compatible = "qcom,x1p42100-iris";
> +
> +	clocks = <&gcc GCC_VIDEO_AXI0_CLK>,
> +		 <&videocc VIDEO_CC_MVS0C_CLK>,
> +		 <&videocc VIDEO_CC_MVS0_CLK>,
> +		 <&videocc VIDEO_CC_MVS0_BSE_CLK>;

[Severity: Low]
Is VIDEO_CC_MVS0_BSE_CLK defined anywhere in the kernel? 

It appears this macro might be missing from the clock dt-bindings headers, 
which would cause the C preprocessor to leave it unexpanded as a string 
literal. Does this cause a dtc syntax error and break the device tree build?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260529-enable_iris_on_purwa-v8-0-b1b9670459ab@oss.qualcomm.com?part=4

  reply	other threads:[~2026-05-29  8:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <keD2FYytnyM7Tuz-kCdnzVBtv7rq_24Kr2dEKBfOpBjqQnmRFqksX-dY7IE8TlIB4ke44GBSYStsHtoa0x4DJQ==@protonmail.internalid>
2026-05-29  7:34 ` [PATCH v8 0/5] media: iris: add support for purwa platform Wangao Wang
2026-05-29  7:34   ` [PATCH v8 1/5] dt-bindings: media: qcom,sm8550-iris: Add X1P42100 compatible Wangao Wang
2026-05-29  8:01     ` sashiko-bot
2026-05-29  7:34   ` [PATCH v8 2/5] media: iris: Add hardware power on/off ops for X1P42100 Wangao Wang
2026-05-29  8:19     ` sashiko-bot
2026-05-29  7:35   ` [PATCH v8 3/5] media: iris: Add platform data " Wangao Wang
2026-05-29  7:35   ` [PATCH v8 4/5] arm64: dts: qcom: purwa: Override Iris clocks and operating points Wangao Wang
2026-05-29  8:55     ` sashiko-bot [this message]
2026-05-29  7:35   ` [PATCH v8 5/5] arm64: dts: qcom: purwa-iot-som: enable video Wangao Wang
2026-05-29  8:46   ` [PATCH v8 0/5] media: iris: add support for purwa platform Jie Gan
2026-05-29  9:13     ` Bryan O'Donoghue
2026-05-29  9:15   ` Bryan O'Donoghue
2026-05-29  9:45     ` Wangao Wang

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=20260529085546.24FEB1F00893@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=wangao.wang@oss.qualcomm.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