devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Raghav Sharma" <raghav.s@samsung.com>
Cc: linux-clk@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v2 11/14] arm64: dts: exynos8855: add cmu_top & cmu_peric clock DT nodes
Date: Fri, 09 Oct 2026 12:57:40 +0000	[thread overview]
Message-ID: <sashiko-outbox-165576@kernel.org> (raw)
In-Reply-To: <20261009120137.2801911-12-raghav.s@samsung.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dts: missing samsung,sysreg in exynos8855-clock DT binding schema
--

commit 66386d316c3e67ff06e1d52fb1215f90cf5a7e17
Author: Raghav Sharma <raghav.s@samsung.com>

arm64: dts: exynos8855: add cmu_top & cmu_peric clock DT nodes

This commit adds the required device tree nodes for the cmu_top and
cmu_peric blocks. It also adds the sysreg_peric node, which contains
the DRCG and MEMCLK SFR bits used in the clock driver.

> diff --git a/arch/arm64/boot/dts/exynos/exynos8855.dtsi b/arch/arm64/boot/dts/exynos/exynos8855.dtsi
> index 0333b80eba845..2e5dc79d66bc7 100644
> --- a/arch/arm64/boot/dts/exynos/exynos8855.dtsi
> +++ b/arch/arm64/boot/dts/exynos/exynos8855.dtsi
[ ... ]
> @@ -170,12 +171,43 @@ pinctrl_cmgp: pinctrl@12030000 {
[ ... ]
> +		cmu_peric: clock-controller@15400000 {
> +			compatible = "samsung,exynos8855-cmu-peric";
> +			reg = <0x15400000 0x10000>;
> +			#clock-cells = <1>;
> +
> +			clocks = <&oscclk>,
> +				 <&cmu_top CLKCMU_DOUT_PERIC_NOC>,
> +				 <&cmu_top CLKCMU_DOUT_PERIC_MMC_CARD>,
> +				 <&cmu_top CLKCMU_DOUT_PERIC_IP>;
> +			clock-names = "oscclk",
> +				      "bus",
> +				      "mmc_card",
> +				      "ip";
> +			samsung,sysreg = <&sysreg_peric>;

[Severity: Low]
Does this undocumented property cause make dtbs_check validation to fail?

The samsung,sysreg property is assigned here in the cmu_peric device tree
node, but it does not appear to be defined in the corresponding binding schema
Documentation/devicetree/bindings/clock/samsung,exynos8855-clock.yaml.

Since the schema enforces additionalProperties: false, adding an undocumented
property here violates the schema. It also appears follow-up patches in the
series continue to add samsung,sysreg properties for other CMU blocks (e.g.,
sysreg_usb, sysreg_peris) without updating the schema to allow it. Should the
binding schema be updated to define samsung,sysreg?

> +		};
> +
> +		sysreg_peric: syscon@15420000 {
> +			compatible = "samsung,exynos8855-peric-sysreg",
> +				      "syscon";
> +			reg = <0x15420000 0x10000>;
> +			clocks = <&cmu_peric CLK_GOUT_SYSREG_PERIC>;
> +		};

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261009120137.2801911-1-raghav.s@samsung.com?part=11

  reply	other threads:[~2026-10-09 12:57 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20261009114331epcas5p37f60df8cdaf502a0cc492ad5eacf5e05@epcas5p3.samsung.com>
2026-10-09 12:01 ` [PATCH v2 00/14] Add clock support for Exynos8855 SoC Raghav Sharma
2026-10-09 12:01   ` [PATCH v2 01/14] dt-bindings: soc: samsung: Exynos8855 SYSREG compatibles Raghav Sharma
2026-10-09 12:01   ` [PATCH v2 02/14] dt-bindings: clock: exynos8855: add top & peric clock definitions Raghav Sharma
2026-10-09 12:01   ` [PATCH v2 03/14] dt-bindings: clock: exynos8855: add peris " Raghav Sharma
2026-10-09 12:01   ` [PATCH v2 04/14] dt-bindings: clock: exynos8855: add hsi " Raghav Sharma
2026-10-09 12:01   ` [PATCH v2 05/14] dt-bindings: clock: exynos8855: add usb " Raghav Sharma
2026-10-09 12:01   ` [PATCH v2 06/14] clk: samsung: clk-pll: Add support for pll_4313 Raghav Sharma
2026-10-09 12:01   ` [PATCH v2 07/14] clk: samsung: exynos8855: add block top and peric clock support Raghav Sharma
2026-10-09 12:12     ` sashiko-bot
2026-10-09 12:01   ` [PATCH v2 08/14] clk: samsung: exynos8855: add block peris " Raghav Sharma
2026-10-09 12:23     ` sashiko-bot
2026-10-09 12:01   ` [PATCH v2 09/14] clk: samsung: exynos8855: add block hsi " Raghav Sharma
2026-10-09 12:30     ` sashiko-bot
2026-10-09 12:01   ` [PATCH v2 10/14] clk: samsung: exynos8855: add block usb " Raghav Sharma
2026-10-09 12:48     ` sashiko-bot
2026-10-09 12:01   ` [PATCH v2 11/14] arm64: dts: exynos8855: add cmu_top & cmu_peric clock DT nodes Raghav Sharma
2026-10-09 12:57     ` sashiko-bot [this message]
2026-10-09 12:01   ` [PATCH v2 12/14] arm64: dts: exynos8855: add cmu_peris " Raghav Sharma
2026-10-09 12:01   ` [PATCH v2 13/14] arm64: dts: exynos8855: add cmu_hsi " Raghav Sharma
2026-10-09 13:11     ` sashiko-bot
2026-10-09 12:01   ` [PATCH v2 14/14] arm64: dts: exynos8855: add cmu_usb " Raghav Sharma

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=sashiko-outbox-165576@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=raghav.s@samsung.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;
as well as URLs for NNTP newsgroup(s).