From: Matthias Brugger <matthias.bgg@gmail.com>
To: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel@collabora.com
Subject: Re: [PATCH] arm64: defconfig: Enable cpufreq for MediaTek
Date: Wed, 29 Dec 2021 20:54:52 +0100 [thread overview]
Message-ID: <af4243f6-a4cd-a51e-0ee0-d5f0dec074ff@gmail.com> (raw)
In-Reply-To: <20211217154452.868419-1-nfraprado@collabora.com>
On 17/12/2021 16:44, Nícolas F. R. A. Prado wrote:
> The MediaTek CPUFreq driver provides control of CPU frequency/voltage
> on MediaTek SoCs. Since there's no device-tree node to bind it to, the
> driver needs to be enabled built-in. Enable it so.
>
> Signed-off-by: Nícolas F. R. A. Prado <nfraprado@collabora.com>
Queued now in v5.16-tmp/defconfig
Thanks
> ---
> arch/arm64/configs/defconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
> index f2e2b9bdd702..829e8bc045f7 100644
> --- a/arch/arm64/configs/defconfig
> +++ b/arch/arm64/configs/defconfig
> @@ -96,6 +96,7 @@ CONFIG_ARM_QCOM_CPUFREQ_HW=y
> CONFIG_ARM_RASPBERRYPI_CPUFREQ=m
> CONFIG_ARM_SCMI_CPUFREQ=y
> CONFIG_ARM_TEGRA186_CPUFREQ=y
> +CONFIG_ARM_MEDIATEK_CPUFREQ=y
> CONFIG_QORIQ_CPUFREQ=y
> CONFIG_ARM_SCMI_PROTOCOL=y
> CONFIG_ARM_SCPI_PROTOCOL=y
>
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
prev parent reply other threads:[~2021-12-29 19:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 15:44 [PATCH] arm64: defconfig: Enable cpufreq for MediaTek Nícolas F. R. A. Prado
2021-12-29 19:54 ` Matthias Brugger [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=af4243f6-a4cd-a51e-0ee0-d5f0dec074ff@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=kernel@collabora.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=nfraprado@collabora.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 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).