From: Conor Dooley <conor.dooley@microchip.com>
To: Prabhakar <prabhakar.csengg@gmail.com>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Magnus Damm <magnus.damm@gmail.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
<linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<linux-renesas-soc@vger.kernel.org>, <devicetree@vger.kernel.org>,
Biju Das <biju.das.jz@bp.renesas.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: Re: [PATCH 1/3] riscv: Kconfig: Enable cpufreq kconfig menu
Date: Tue, 15 Nov 2022 10:59:51 +0000 [thread overview]
Message-ID: <Y3NxJ0FpDQMhP05+@wendy> (raw)
In-Reply-To: <20221115105135.1180490-2-prabhakar.mahadev-lad.rj@bp.renesas.com>
On Tue, Nov 15, 2022 at 10:51:33AM +0000, Prabhakar wrote:
> From: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
>
> Enable cpufreq kconfig menu for RISC-V.
Yes, please. It was on my todo list to dig this one out and un-archive
it on patchwork:
https://lore.kernel.org/linux-riscv/20220718180713.451507-1-mail@conchuod.ie/
Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
>
> Signed-off-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
> ---
> arch/riscv/Kconfig | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig
> index fa78595a6089..ce905454a3bf 100644
> --- a/arch/riscv/Kconfig
> +++ b/arch/riscv/Kconfig
> @@ -691,6 +691,8 @@ menu "CPU Power Management"
>
> source "drivers/cpuidle/Kconfig"
>
> +source "drivers/cpufreq/Kconfig"
> +
> endmenu # "CPU Power Management"
>
> source "arch/riscv/kvm/Kconfig"
> --
> 2.25.1
>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Conor Dooley <conor.dooley@microchip.com>
To: Prabhakar <prabhakar.csengg@gmail.com>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Magnus Damm <magnus.damm@gmail.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
<linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<linux-renesas-soc@vger.kernel.org>, <devicetree@vger.kernel.org>,
Biju Das <biju.das.jz@bp.renesas.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: Re: [PATCH 1/3] riscv: Kconfig: Enable cpufreq kconfig menu
Date: Tue, 15 Nov 2022 10:59:51 +0000 [thread overview]
Message-ID: <Y3NxJ0FpDQMhP05+@wendy> (raw)
In-Reply-To: <20221115105135.1180490-2-prabhakar.mahadev-lad.rj@bp.renesas.com>
On Tue, Nov 15, 2022 at 10:51:33AM +0000, Prabhakar wrote:
> From: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
>
> Enable cpufreq kconfig menu for RISC-V.
Yes, please. It was on my todo list to dig this one out and un-archive
it on patchwork:
https://lore.kernel.org/linux-riscv/20220718180713.451507-1-mail@conchuod.ie/
Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
>
> Signed-off-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
> ---
> arch/riscv/Kconfig | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig
> index fa78595a6089..ce905454a3bf 100644
> --- a/arch/riscv/Kconfig
> +++ b/arch/riscv/Kconfig
> @@ -691,6 +691,8 @@ menu "CPU Power Management"
>
> source "drivers/cpuidle/Kconfig"
>
> +source "drivers/cpufreq/Kconfig"
> +
> endmenu # "CPU Power Management"
>
> source "arch/riscv/kvm/Kconfig"
> --
> 2.25.1
>
next prev parent reply other threads:[~2022-11-15 11:04 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 10:51 [PATCH 0/3] RZ/Five: Enable ADC/CANFD/I2C/OPP/Thermal Zones/TSU Prabhakar
2022-11-15 10:51 ` Prabhakar
2022-11-15 10:51 ` [PATCH 1/3] riscv: Kconfig: Enable cpufreq kconfig menu Prabhakar
2022-11-15 10:51 ` Prabhakar
2022-11-15 10:59 ` Conor Dooley [this message]
2022-11-15 10:59 ` Conor Dooley
2022-11-15 10:51 ` [PATCH 2/3] riscv: dts: renesas: r9a07g043f/rzfive-smarc-som: Enable ADC/OPP/Thermal Zones/TSU Prabhakar
2022-11-15 10:51 ` Prabhakar
2022-11-16 9:03 ` Geert Uytterhoeven
2022-11-16 9:03 ` Geert Uytterhoeven
2022-11-16 9:06 ` Geert Uytterhoeven
2022-11-16 9:06 ` Geert Uytterhoeven
2022-11-15 10:51 ` [PATCH 3/3] riscv: dts: renesas: rzfive-smarc: Enable CANFD/I2C Prabhakar
2022-11-15 10:51 ` Prabhakar
2022-11-16 9:08 ` Geert Uytterhoeven
2022-11-16 9:08 ` Geert Uytterhoeven
2022-11-15 14:20 ` [PATCH 0/3] RZ/Five: Enable ADC/CANFD/I2C/OPP/Thermal Zones/TSU Conor Dooley
2022-11-15 14:20 ` Conor Dooley
2022-11-15 18:21 ` Lad, Prabhakar
2022-11-15 18:21 ` Lad, Prabhakar
2022-11-16 9:26 ` Geert Uytterhoeven
2022-11-16 9:26 ` Geert Uytterhoeven
2022-11-17 22:00 ` patchwork-bot+linux-riscv
2022-11-17 22:00 ` patchwork-bot+linux-riscv
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=Y3NxJ0FpDQMhP05+@wendy \
--to=conor.dooley@microchip.com \
--cc=aou@eecs.berkeley.edu \
--cc=biju.das.jz@bp.renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=magnus.damm@gmail.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=prabhakar.csengg@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh+dt@kernel.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.