From: Sudeep Holla <sudeep.holla@arm.com>
To: Chukun Pan <amadeus@jmu.edu.cn>
Cc: Heiko Stuebner <heiko@sntech.de>, Yao Zi <ziyao@disroot.org>,
Sudeep Holla <sudeep.holla@arm.com>,
Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-rockchip@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>
Subject: Re: [PATCH 1/1] arm64: dts: rockchip: enable SCMI clk for RK3528 SoC
Date: Thu, 6 Mar 2025 14:54:50 +0000 [thread overview]
Message-ID: <Z8m3OkHAedbQyKbu@bogus> (raw)
In-Reply-To: <20250306131016.281290-2-amadeus@jmu.edu.cn>
On Thu, Mar 06, 2025 at 09:10:16PM +0800, Chukun Pan wrote:
> Same as RK3568, RK3528 uses SCMI clk instead of ARMCLK.
> Add SCMI clk for CPU, GPU and RNG will also use it.
>
It is highly recommended not to use clock protocol for CPUs and GPUs
especially if the plan is to drive regulators separately. Please use
the performance protocol instead which can abstract the clock and the
regulator details for the OS.
--
Regards,
Sudeep
prev parent reply other threads:[~2025-03-06 14:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 13:10 [PATCH 0/1] arm64: dts: rockchip: enable SCMI clk for RK3528 SoC Chukun Pan
2025-03-06 13:10 ` [PATCH 1/1] " Chukun Pan
2025-03-06 13:29 ` Heiko Stübner
2025-03-06 13:40 ` Chukun Pan
2025-03-06 13:45 ` Krzysztof Kozlowski
2025-03-06 14:20 ` Chukun Pan
2025-03-06 14:25 ` Heiko Stübner
2025-03-06 14:50 ` Chukun Pan
2025-03-06 13:51 ` Heiko Stübner
2025-03-06 13:54 ` Krzysztof Kozlowski
2025-03-06 13:57 ` Heiko Stübner
2025-03-06 14:54 ` Jonas Karlman
2025-03-06 14:54 ` Sudeep Holla [this message]
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=Z8m3OkHAedbQyKbu@bogus \
--to=sudeep.holla@arm.com \
--cc=amadeus@jmu.edu.cn \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@kernel.org \
--cc=ziyao@disroot.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 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).