All of lore.kernel.org
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Magnus Damm <magnus.damm@gmail.com>,
	Tho Vu <tho.vu.wh@renesas.com>,
	linux-renesas-soc@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: dts: renesas: r8a779f0: Add CA55 operating points
Date: Thu, 1 Dec 2022 07:33:47 +0530	[thread overview]
Message-ID: <20221201020347.dpoaccvkzuss3jpk@vireshk-i7> (raw)
In-Reply-To: <ae78351d702a53702a1d5fa26675fe982b99cdf5.1669817508.git.geert+renesas@glider.be>

On 30-11-22, 15:16, Geert Uytterhoeven wrote:
> Add operating points for running the Cortex-A55 CPU cores on R-Car S4-8
> at various speeds, up to the maximum supported frequency (1200 MHz).
> 
> R-Car S4-8 has 8 Cortex-A55 cores, grouped in 4 clusters.
> CA55 Sub-System 0 (first 2 clusters / CPU cores 0-3) is clocked by Z0φ.
> CA55 Sub-System 1 (last 2 clusters / CPU cores 4-7) is clocked by Z1φ.
> 
> As the two sets of clusters are driven by separate clocks, this requires
> specifying two separate tables (using the same operating performance
> point values), with "opp-shared" to indicate that the CPU cores in each
> set share state.
> 
> Based on a patch in the BSP by Tho Vu.
> 
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> To be queued in renesas-devel for v6.3.
> 
> Changes compared to the BSP:
>   - Use two tables.
> 
> Tested on the Renesas Spider development board by using the CPUfreq
> userspace governor, writing the desired CPU clock rate to the CPUfreq
> policy's "scaling_setspeed" file in sysfs, verifying the clock rate of
> the Z0φ and Z1φ clocks in debugfs, and running the dhrystones benchmark
> on the various CPU cores.
> 
> The Linux cpufreq driver creates two policies under
> /sys/devices/system/cpu/cpufreq/: "policy0" and "policy4".
> 
> With a single table and "opp-shared", only "policy0" would be created,
> and clock Z1φ would never be changed.
> With a single table and without "opp-shared", 8 policies would be
> created, and the rate of clocks Z0φ and Z1φ would reflect the value for
> the last touched CPU core from the corresponding set.
> ---
>  arch/arm64/boot/dts/renesas/r8a779f0.dtsi | 62 +++++++++++++++++++++++
>  1 file changed, 62 insertions(+)

Acked-by: Viresh Kumar <viresh.kumar@linaro.org>

-- 
viresh

WARNING: multiple messages have this Message-ID (diff)
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Magnus Damm <magnus.damm@gmail.com>,
	Tho Vu <tho.vu.wh@renesas.com>,
	linux-renesas-soc@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: dts: renesas: r8a779f0: Add CA55 operating points
Date: Thu, 1 Dec 2022 07:33:47 +0530	[thread overview]
Message-ID: <20221201020347.dpoaccvkzuss3jpk@vireshk-i7> (raw)
In-Reply-To: <ae78351d702a53702a1d5fa26675fe982b99cdf5.1669817508.git.geert+renesas@glider.be>

On 30-11-22, 15:16, Geert Uytterhoeven wrote:
> Add operating points for running the Cortex-A55 CPU cores on R-Car S4-8
> at various speeds, up to the maximum supported frequency (1200 MHz).
> 
> R-Car S4-8 has 8 Cortex-A55 cores, grouped in 4 clusters.
> CA55 Sub-System 0 (first 2 clusters / CPU cores 0-3) is clocked by Z0φ.
> CA55 Sub-System 1 (last 2 clusters / CPU cores 4-7) is clocked by Z1φ.
> 
> As the two sets of clusters are driven by separate clocks, this requires
> specifying two separate tables (using the same operating performance
> point values), with "opp-shared" to indicate that the CPU cores in each
> set share state.
> 
> Based on a patch in the BSP by Tho Vu.
> 
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> To be queued in renesas-devel for v6.3.
> 
> Changes compared to the BSP:
>   - Use two tables.
> 
> Tested on the Renesas Spider development board by using the CPUfreq
> userspace governor, writing the desired CPU clock rate to the CPUfreq
> policy's "scaling_setspeed" file in sysfs, verifying the clock rate of
> the Z0φ and Z1φ clocks in debugfs, and running the dhrystones benchmark
> on the various CPU cores.
> 
> The Linux cpufreq driver creates two policies under
> /sys/devices/system/cpu/cpufreq/: "policy0" and "policy4".
> 
> With a single table and "opp-shared", only "policy0" would be created,
> and clock Z1φ would never be changed.
> With a single table and without "opp-shared", 8 policies would be
> created, and the rate of clocks Z0φ and Z1φ would reflect the value for
> the last touched CPU core from the corresponding set.
> ---
>  arch/arm64/boot/dts/renesas/r8a779f0.dtsi | 62 +++++++++++++++++++++++
>  1 file changed, 62 insertions(+)

Acked-by: Viresh Kumar <viresh.kumar@linaro.org>

-- 
viresh

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-12-01  2:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-30 14:16 [PATCH] arm64: dts: renesas: r8a779f0: Add CA55 operating points Geert Uytterhoeven
2022-11-30 14:16 ` Geert Uytterhoeven
2022-12-01  2:03 ` Viresh Kumar [this message]
2022-12-01  2:03   ` Viresh Kumar

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=20221201020347.dpoaccvkzuss3jpk@vireshk-i7 \
    --to=viresh.kumar@linaro.org \
    --cc=geert+renesas@glider.be \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=tho.vu.wh@renesas.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 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.