All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Charkov <alchark@gmail.com>
To: "Heiko Stübner" <heiko@sntech.de>
Cc: Rob Herring <robh+dt@kernel.org>,
	 Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	 Daniel Lezcano <daniel.lezcano@linaro.org>,
	Dragan Simic <dsimic@manjaro.org>,
	 Viresh Kumar <viresh.kumar@linaro.org>,
	devicetree@vger.kernel.org,
	 linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org,
	 linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/4] arm64: dts: rockchip: Add OPP data for CPU cores on RK3588
Date: Wed, 31 Jan 2024 13:34:34 +0400	[thread overview]
Message-ID: <CABjd4YzR6KuqqXQQaTt5Fw_QKwkSf4iaBiM_KXX_sFoD4bNX9A@mail.gmail.com> (raw)
In-Reply-To: <2168725.pYTLVKaXyH@diego>

On Wed, Jan 31, 2024 at 1:12 PM Heiko Stübner <heiko@sntech.de> wrote:
>
> Am Dienstag, 30. Januar 2024, 19:21:15 CET schrieb Alexey Charkov:
> > By default the CPUs on RK3588 start up in a conservative performance
> > mode. Add frequency and voltage mappings to the device tree to enable
> > dynamic scaling via cpufreq
>
> Please add a paragraph describing where the opp values comes from.
> Probably just the vendor kernel, which is fine, but I really like to
> document that these values have some sort of grounds ;-)

Will do, thank you! Yes, these are from the vendor kernel, namely from
Radxa's version [1].

[1] https://github.com/radxa/kernel/blob/stable-5.10-rock5/arch/arm64/boot/dts/rockchip/rk3588s.dtsi

Best regards,
Alexey

WARNING: multiple messages have this Message-ID (diff)
From: Alexey Charkov <alchark@gmail.com>
To: "Heiko Stübner" <heiko@sntech.de>
Cc: Rob Herring <robh+dt@kernel.org>,
	 Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	 Daniel Lezcano <daniel.lezcano@linaro.org>,
	Dragan Simic <dsimic@manjaro.org>,
	 Viresh Kumar <viresh.kumar@linaro.org>,
	devicetree@vger.kernel.org,
	 linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org,
	 linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/4] arm64: dts: rockchip: Add OPP data for CPU cores on RK3588
Date: Wed, 31 Jan 2024 13:34:34 +0400	[thread overview]
Message-ID: <CABjd4YzR6KuqqXQQaTt5Fw_QKwkSf4iaBiM_KXX_sFoD4bNX9A@mail.gmail.com> (raw)
In-Reply-To: <2168725.pYTLVKaXyH@diego>

On Wed, Jan 31, 2024 at 1:12 PM Heiko Stübner <heiko@sntech.de> wrote:
>
> Am Dienstag, 30. Januar 2024, 19:21:15 CET schrieb Alexey Charkov:
> > By default the CPUs on RK3588 start up in a conservative performance
> > mode. Add frequency and voltage mappings to the device tree to enable
> > dynamic scaling via cpufreq
>
> Please add a paragraph describing where the opp values comes from.
> Probably just the vendor kernel, which is fine, but I really like to
> document that these values have some sort of grounds ;-)

Will do, thank you! Yes, these are from the vendor kernel, namely from
Radxa's version [1].

[1] https://github.com/radxa/kernel/blob/stable-5.10-rock5/arch/arm64/boot/dts/rockchip/rk3588s.dtsi

Best regards,
Alexey

_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

WARNING: multiple messages have this Message-ID (diff)
From: Alexey Charkov <alchark@gmail.com>
To: "Heiko Stübner" <heiko@sntech.de>
Cc: Rob Herring <robh+dt@kernel.org>,
	 Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	 Daniel Lezcano <daniel.lezcano@linaro.org>,
	Dragan Simic <dsimic@manjaro.org>,
	 Viresh Kumar <viresh.kumar@linaro.org>,
	devicetree@vger.kernel.org,
	 linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org,
	 linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/4] arm64: dts: rockchip: Add OPP data for CPU cores on RK3588
Date: Wed, 31 Jan 2024 13:34:34 +0400	[thread overview]
Message-ID: <CABjd4YzR6KuqqXQQaTt5Fw_QKwkSf4iaBiM_KXX_sFoD4bNX9A@mail.gmail.com> (raw)
In-Reply-To: <2168725.pYTLVKaXyH@diego>

On Wed, Jan 31, 2024 at 1:12 PM Heiko Stübner <heiko@sntech.de> wrote:
>
> Am Dienstag, 30. Januar 2024, 19:21:15 CET schrieb Alexey Charkov:
> > By default the CPUs on RK3588 start up in a conservative performance
> > mode. Add frequency and voltage mappings to the device tree to enable
> > dynamic scaling via cpufreq
>
> Please add a paragraph describing where the opp values comes from.
> Probably just the vendor kernel, which is fine, but I really like to
> document that these values have some sort of grounds ;-)

Will do, thank you! Yes, these are from the vendor kernel, namely from
Radxa's version [1].

[1] https://github.com/radxa/kernel/blob/stable-5.10-rock5/arch/arm64/boot/dts/rockchip/rk3588s.dtsi

Best regards,
Alexey

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

  reply	other threads:[~2024-01-31  9:34 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-30 18:21 [PATCH v2 0/4] RK3588 and Rock 5B dts additions: thermal, OPP and fan Alexey Charkov
2024-01-30 18:21 ` Alexey Charkov
2024-01-30 18:21 ` Alexey Charkov
2024-01-30 18:21 ` [PATCH v2 1/4] arm64: dts: rockchip: enable built-in thermal monitoring on rk3588 Alexey Charkov
2024-01-30 18:21   ` Alexey Charkov
2024-01-30 18:21   ` Alexey Charkov
2024-01-31  5:05   ` Dragan Simic
2024-01-31  5:05     ` Dragan Simic
2024-01-31  5:05     ` Dragan Simic
2024-01-31  9:56     ` Alexey Charkov
2024-01-31  9:56       ` Alexey Charkov
2024-01-31  9:56       ` Alexey Charkov
2024-01-31 10:08       ` Dragan Simic
2024-01-31 10:08         ` Dragan Simic
2024-01-31 10:08         ` Dragan Simic
2024-01-30 18:21 ` [PATCH v2 2/4] arm64: dts: rockchip: enable temperature driven fan control on Rock 5B Alexey Charkov
2024-01-30 18:21   ` Alexey Charkov
2024-01-30 18:21   ` Alexey Charkov
2024-01-31  5:08   ` Dragan Simic
2024-01-31  5:08     ` Dragan Simic
2024-01-31  5:08     ` Dragan Simic
2024-01-31  9:43     ` Alexey Charkov
2024-01-31  9:43       ` Alexey Charkov
2024-01-31  9:43       ` Alexey Charkov
2024-02-01 14:26   ` Chen-Yu Tsai
2024-02-01 14:26     ` Chen-Yu Tsai
2024-02-01 14:26     ` Chen-Yu Tsai
2024-02-01 17:34     ` Dragan Simic
2024-02-01 17:34       ` Dragan Simic
2024-02-01 17:34       ` Dragan Simic
2024-02-01 19:15       ` Alexey Charkov
2024-02-01 19:15         ` Alexey Charkov
2024-02-01 19:15         ` Alexey Charkov
2024-02-01 19:31         ` Dragan Simic
2024-02-01 19:31           ` Dragan Simic
2024-02-01 19:31           ` Dragan Simic
2024-02-01 19:43           ` Dragan Simic
2024-02-01 19:43             ` Dragan Simic
2024-02-01 19:43             ` Dragan Simic
2024-02-02 14:42             ` Alexey Charkov
2024-02-02 14:42               ` Alexey Charkov
2024-02-02 14:42               ` Alexey Charkov
2024-02-02 20:14               ` Dragan Simic
2024-02-02 20:14                 ` Dragan Simic
2024-02-02 20:14                 ` Dragan Simic
2024-01-30 18:21 ` [PATCH v2 3/4] arm64: dts: rockchip: Add OPP data for CPU cores on RK3588 Alexey Charkov
2024-01-30 18:21   ` Alexey Charkov
2024-01-30 18:21   ` Alexey Charkov
2024-01-31  9:12   ` Heiko Stübner
2024-01-31  9:12     ` Heiko Stübner
2024-01-31  9:12     ` Heiko Stübner
2024-01-31  9:34     ` Alexey Charkov [this message]
2024-01-31  9:34       ` Alexey Charkov
2024-01-31  9:34       ` Alexey Charkov
2024-01-30 18:21 ` [PATCH v2 4/4] arm64: dts: rockchip: Add further granularity in RK3588 CPU OPPs Alexey Charkov
2024-01-30 18:21   ` Alexey Charkov
2024-01-30 18:21   ` Alexey Charkov
2024-01-31  5:08   ` Dragan Simic
2024-01-31  5:08     ` Dragan Simic
2024-01-31  5:08     ` Dragan Simic
2024-02-08 12:19     ` Dragan Simic
2024-02-08 12:19       ` Dragan Simic
2024-02-08 12:19       ` Dragan Simic

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=CABjd4YzR6KuqqXQQaTt5Fw_QKwkSf4iaBiM_KXX_sFoD4bNX9A@mail.gmail.com \
    --to=alchark@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dsimic@manjaro.org \
    --cc=heiko@sntech.de \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=robh+dt@kernel.org \
    --cc=viresh.kumar@linaro.org \
    /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.