Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Henrik Grimler" <henrik.grimler@axis.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 08/17] ARM: dts: samsung: exynos4210: use operating-points-v2
Date: Sun, 04 Oct 2026 20:25:30 +0000	[thread overview]
Message-ID: <20261004202530.B1CE11F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20261004-exynos-arm-cleanup-v1-8-45e435353c56@axis.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] dts: missing opp-shared property causes conflicting cpufreq policies
--

commit fcba4068b9646df5bfbec161d06e3521379f32ed
Author: Henrik Grimler <henrik.grimler@axis.com>

ARM: dts: samsung: exynos4210: use operating-points-v2

This commit updates the exynos4210 device tree to use operating-points-v2
instead of the deprecated operating-points (v1) format. This resolves dt-check
style warnings about continuation-alignment.

> diff --git a/arch/arm/boot/dts/samsung/exynos4210.dtsi b/arch/arm/boot/dts/samsung/exynos4210.dtsi
> index d37ac0c97dbcf..4981bbb7cf311 100644
> --- a/arch/arm/boot/dts/samsung/exynos4210.dtsi
> +++ b/arch/arm/boot/dts/samsung/exynos4210.dtsi

[ ... ]

> @@ -263,6 +247,46 @@ opp-200000000 {
>  		};
>  	};
>  
> +	cpu_opp_table: opp-table-1 {
> +		compatible = "operating-points-v2";
> +

[Severity: High]
Does this new node need the opp-shared property?

CPU0 and CPU1 on this device share the CLK_ARM_CLK clock. When migrating to
operating-points-v2, the OPP framework relies on the opp-shared property to
know whether CPUs share the same clock line and therefore need a unified
cpufreq policy.

Without this property, the framework assumes the CPUs do not share the table:

drivers/opp/of.c:dev_pm_opp_of_get_sharing_cpus() {
    ...
    /* OPPs are shared ? */
    if (!of_property_read_bool(np, "opp-shared"))
        return 0;
    ...
}

Because the legacy v1 fallback logic is bypassed for v2 nodes, the cpufreq
driver will create independent policies and governors for CPU0 and CPU1. 

Since the cores share the same physical clock line, will this lead to the
independent governors issuing conflicting clk_set_rate requests, potentially
causing chaotic frequency switching and instability?

> +		opp-200000000 {
> +			opp-hz = /bits/ 64 <200000000>;
> +			opp-microvolt = <950000>;
> +			clock-latency-ns = <160000>;
> +		};

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261004-exynos-arm-cleanup-v1-0-45e435353c56@axis.com?part=8

  reply	other threads:[~2026-10-04 20:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-04 20:15 [PATCH 00/17] ARM: dts: samsung: cleanup Exynos 4210 dts'es Henrik Grimler
2026-10-04 20:15 ` [PATCH 01/17] ARM: dts: samsung: exynos4: add or remove empty lines Henrik Grimler
2026-10-04 20:15 ` [PATCH 02/17] ARM: dts: samsung: exynos4: order *-names properties Henrik Grimler
2026-10-04 20:16 ` [PATCH 03/17] ARM: dts: samsung: exynos4: sort all properties Henrik Grimler
2026-10-04 20:16 ` [PATCH 04/17] ARM: dts: samsung: exynos4-cpu-thermal: fix indentation and sort Henrik Grimler
2026-10-04 20:16 ` [PATCH 05/17] ARM: dts: samsung: exynos4210: sort nodes by address Henrik Grimler
2026-10-04 20:16 ` [PATCH 06/17] ARM: dts: samsung: exynos4210: add or remove empty lines Henrik Grimler
2026-10-04 20:16 ` [PATCH 07/17] ARM: dts: samsung: exynos4210: sort all properties Henrik Grimler
2026-10-04 20:16 ` [PATCH 08/17] ARM: dts: samsung: exynos4210: use operating-points-v2 Henrik Grimler
2026-10-04 20:25   ` sashiko-bot [this message]
2026-10-04 20:16 ` [PATCH 09/17] ARM: dts: samsung: exynos4210: align all multiline properties Henrik Grimler
2026-10-04 20:16 ` [PATCH 10/17] ARM: dts: samsung: exynos4210-pinctrl: align all continued lines Henrik Grimler
2026-10-04 20:16 ` [PATCH 11/17] ARM: dts: samsung: exynos4210-i9100: sort properties Henrik Grimler
2026-10-04 20:16 ` [PATCH 12/17] ARM: dts: samsung: exynos4210-trats: " Henrik Grimler
2026-10-04 20:16 ` [PATCH 13/17] ARM: dts: samsung: exynos4210-origen: " Henrik Grimler
2026-10-04 20:16 ` [PATCH 14/17] ARM: dts: samsung: exynos4210-universal_c210: " Henrik Grimler
2026-10-04 20:16 ` [PATCH 15/17] ARM: dts: samsung: exynos4210-smdkv310: " Henrik Grimler
2026-10-04 20:16 ` [PATCH 16/17] ARM: dts: samsung: exynos4210-smdkv310: sort child nodes Henrik Grimler
2026-10-04 20:16 ` [PATCH 17/17] ARM: dts: samsung: exynos4210-universal_c210: fix alignments Henrik Grimler

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=20261004202530.B1CE11F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=henrik.grimler@axis.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