From: Xi Ruoyao <xry111@xry111.site>
To: Huacai Chen <chenhuacai@loongson.cn>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Huacai Chen <chenhuacai@kernel.org>
Cc: loongarch@lists.linux.dev, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, Xuerui Wang <kernel@xen0n.name>,
Jiaxun Yang <jiaxun.yang@flygoat.com>
Subject: Re: [PATCH 0/2] LoongArch: Add Loongson-3 CPUFreq driver support
Date: Mon, 24 Jun 2024 21:30:40 +0800 [thread overview]
Message-ID: <1dc3823c0f0a459ae033a69b2eeb3d2929254fc2.camel@xry111.site> (raw)
In-Reply-To: <20240612064205.2041548-1-chenhuacai@loongson.cn>
On Wed, 2024-06-12 at 14:42 +0800, Huacai Chen wrote:
> This series add architectural preparation and CPUFreq driver for
> Loongson-3 (based on LoongArch).
>
> Some of LoongArch processors support DVFS, their IOCSR.FEATURES has
> IOCSRF_FREQSCALE set. And they has a micro-core in the package called
> SMC (System Management Controller) to scale frequency, voltage, etc.
>
> Huacai Chen(2):
> LoongArch: Add architectural preparation for CPUFreq.
> cpufreq: Add Loongson-3 CPUFreq driver support.
>
> Signed-off-by: Huacai Chen <chenhuacai@loongson.cn>
A question: is it OK to enable cpufreq when overclocking is set via the
firmware?
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2024-06-24 13:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 6:42 Huacai Chen
2024-06-12 6:42 ` [PATCH 1/2] LoongArch: Add architectural preparation for CPUFreq Huacai Chen
2024-06-12 6:42 ` [PATCH 2/2] cpufreq: Add Loongson-3 CPUFreq driver support Huacai Chen
2024-06-21 9:48 ` Huacai Chen
2024-06-25 7:56 ` Viresh Kumar
2024-06-26 3:51 ` Huacai Chen
2024-06-26 4:34 ` Viresh Kumar
2024-06-29 14:14 ` Huacai Chen
2024-06-24 13:30 ` Xi Ruoyao [this message]
2024-06-24 13:59 ` [PATCH 0/2] LoongArch: " Huacai Chen
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=1dc3823c0f0a459ae033a69b2eeb3d2929254fc2.camel@xry111.site \
--to=xry111@xry111.site \
--cc=chenhuacai@kernel.org \
--cc=chenhuacai@loongson.cn \
--cc=jiaxun.yang@flygoat.com \
--cc=kernel@xen0n.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=rafael@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®