From: Brandon Cheo Fusi <fusibrandon13@gmail.com>
To: viresh.kumar@linaro.org
Cc: aou@eecs.berkeley.edu, conor+dt@kernel.org,
devicetree@vger.kernel.org, fusibrandon13@gmail.com,
jernej.skrabec@gmail.com, krzysztof.kozlowski+dt@linaro.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
linux-riscv@lists.infradead.org, linux-sunxi@lists.linux.dev,
palmer@dabbelt.com, paul.walmsley@sifive.com, rafael@kernel.org,
robh+dt@kernel.org, samuel@sholland.org, tiny.windzz@gmail.com,
wens@csie.org
Subject: Re: [PATCH 4/5] cpufreq: Add support for RISC-V CPU Frequency scaling drivers
Date: Fri, 15 Dec 2023 16:17:23 +0100 [thread overview]
Message-ID: <20231215151723.46409-1-fusibrandon13@gmail.com> (raw)
In-Reply-To: <20231214111702.xdd7qlcrpqh74i3j@vireshk-i7>
On Thu, Dec 14, 2023 at 12:17 PM Viresh Kumar <viresh.kumar@linaro.org> wrote:
>
> On 14-12-23, 11:33, Brandon Cheo Fusi wrote:
> > Add Kconfig file for cpufreq scaling drivers that can handle RISC-V
> > CPUs. An entry is included for the Allwinner H6 cpufreq driver that
> > works with D1.
> >
> > Signed-off-by: Brandon Cheo Fusi <fusibrandon13@gmail.com>
> > ---
> > drivers/cpufreq/Kconfig | 4 ++++
> > drivers/cpufreq/Kconfig.riscv | 16 ++++++++++++++++
> > 2 files changed, 20 insertions(+)
> > create mode 100644 drivers/cpufreq/Kconfig.riscv
>
> We don't have a separate kconfig file for each architecture. Only if
> there are too many entries for an architecture, we add a new file.
>
> --
> viresh
The sun50i cpufreq driver is currently only available when CONFIG_ARM or
CONFIG_ARM64 is selected, so this was the only decent way I could think
of making it accessible on either one of CONFIG_(ARM | ARM64 | RISC-V).
Any suggestions for a better workaround ?
Also I think future cpufreq drivers for RISC-V are going to happen, so we
might as well have the Kconfig file.
Kind Regards,
Brandon.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-12-15 15:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 10:33 [PATCH 0/5] cpufreq support for the D1 Brandon Cheo Fusi
2023-12-14 10:33 ` [PATCH 1/5] riscv: dts: allwinner: Update opp table to allow CPU frequency scaling Brandon Cheo Fusi
2023-12-14 11:14 ` Viresh Kumar
2023-12-14 13:47 ` Conor Dooley
2023-12-14 16:36 ` Jernej Škrabec
2023-12-15 15:18 ` Brandon Cheo Fusi
2023-12-15 15:12 ` Brandon Cheo Fusi
2023-12-14 10:33 ` [PATCH 2/5] cpufreq: sun50i: Add D1 support Brandon Cheo Fusi
2023-12-14 16:29 ` Jernej Škrabec
2023-12-14 16:40 ` Andre Przywara
2023-12-14 17:15 ` Jernej Škrabec
2023-12-14 10:33 ` [PATCH 3/5] cpufreq: dt-platdev: Blocklist allwinner,sun20i-d1 SoC Brandon Cheo Fusi
2023-12-14 16:30 ` Jernej Škrabec
2023-12-14 10:33 ` [PATCH 4/5] cpufreq: Add support for RISC-V CPU Frequency scaling drivers Brandon Cheo Fusi
2023-12-14 11:17 ` Viresh Kumar
2023-12-15 15:17 ` Brandon Cheo Fusi [this message]
2023-12-15 21:09 ` Samuel Holland
2023-12-18 6:09 ` Viresh Kumar
2023-12-14 10:33 ` [PATCH 5/5] cpufreq: Make sun50i h6 cpufreq Kconfig option generic Brandon Cheo Fusi
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=20231215151723.46409-1-fusibrandon13@gmail.com \
--to=fusibrandon13@gmail.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jernej.skrabec@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=samuel@sholland.org \
--cc=tiny.windzz@gmail.com \
--cc=viresh.kumar@linaro.org \
--cc=wens@csie.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).