linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chanwoo Choi <cw00.choi@samsung.com>
To: Leonard Crestez <leonard.crestez@nxp.com>,
	MyungJoo Ham <myungjoo.ham@samsung.com>,
	Kyungmin Park <kyungmin.park@samsung.com>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	Enric Balletbo i Serra <enric.balletbo@collabora.com>,
	Dmitry Osipenko <digetx@gmail.com>,
	linux-pm@vger.kernel.org
Subject: Re: [PATCH] PM / devfreq: Kconfig: Drop explicit selection of PM_OPP
Date: Tue, 12 Nov 2019 09:40:16 +0900	[thread overview]
Message-ID: <2955f629-ffa2-fa5e-6734-a400428a2821@samsung.com> (raw)
In-Reply-To: <1fb316f5b2c4d36437a536cef46ce8e4567dee15.1573495711.git.leonard.crestez@nxp.com>

On 11/12/19 3:16 AM, Leonard Crestez wrote:
> CONFIG_PM_OPP is already selected by CONFIG_PM_DEVFREQ since
> commit b9c69e043266 ("PM / devfreq: Add dependency on PM_OPP")
> This means that individual drivers shouldn't "select PM_OPP" explicitly.
> 
> Signed-off-by: Leonard Crestez <leonard.crestez@nxp.com>
> 
> ---
> Spawned by review comments on a new driver:
> https://patchwork.kernel.org/patch/11235695/#22992159
> 
> This patch shouldn't have any dependencies.
> 
>  drivers/devfreq/Kconfig | 4 ----
>  1 file changed, 4 deletions(-)
> 
> diff --git a/drivers/devfreq/Kconfig b/drivers/devfreq/Kconfig
> index defe1d438710..066e6c4efaa2 100644
> --- a/drivers/devfreq/Kconfig
> +++ b/drivers/devfreq/Kconfig
> @@ -81,11 +81,10 @@ config ARM_EXYNOS_BUS_DEVFREQ
>  	depends on ARCH_EXYNOS || COMPILE_TEST
>  	select DEVFREQ_GOV_SIMPLE_ONDEMAND
>  	select DEVFREQ_GOV_PASSIVE
>  	select DEVFREQ_EVENT_EXYNOS_PPMU
>  	select PM_DEVFREQ_EVENT
> -	select PM_OPP
>  	help
>  	  This adds the common DEVFREQ driver for Exynos Memory bus. Exynos
>  	  Memory bus has one more group of memory bus (e.g, MIF and INT block).
>  	  Each memory bus group could contain many memoby bus block. It reads
>  	  PPMU counters of memory controllers by using DEVFREQ-event device
> @@ -96,22 +95,20 @@ config ARM_TEGRA_DEVFREQ
>  	tristate "NVIDIA Tegra30/114/124/210 DEVFREQ Driver"
>  	depends on ARCH_TEGRA_3x_SOC || ARCH_TEGRA_114_SOC || \
>  		ARCH_TEGRA_132_SOC || ARCH_TEGRA_124_SOC || \
>  		ARCH_TEGRA_210_SOC || \
>  		COMPILE_TEST
> -	select PM_OPP
>  	help
>  	  This adds the DEVFREQ driver for the Tegra family of SoCs.
>  	  It reads ACTMON counters of memory controllers and adjusts the
>  	  operating frequencies and voltages with OPP support.
>  
>  config ARM_TEGRA20_DEVFREQ
>  	tristate "NVIDIA Tegra20 DEVFREQ Driver"
>  	depends on (TEGRA_MC && TEGRA20_EMC) || COMPILE_TEST
>  	depends on COMMON_CLK
>  	select DEVFREQ_GOV_SIMPLE_ONDEMAND
> -	select PM_OPP
>  	help
>  	  This adds the DEVFREQ driver for the Tegra20 family of SoCs.
>  	  It reads Memory Controller counters and adjusts the operating
>  	  frequencies and voltages with OPP support.
>  
> @@ -119,11 +116,10 @@ config ARM_RK3399_DMC_DEVFREQ
>  	tristate "ARM RK3399 DMC DEVFREQ Driver"
>  	depends on ARCH_ROCKCHIP
>  	select DEVFREQ_EVENT_ROCKCHIP_DFI
>  	select DEVFREQ_GOV_SIMPLE_ONDEMAND
>  	select PM_DEVFREQ_EVENT
> -	select PM_OPP
>  	help
>            This adds the DEVFREQ driver for the RK3399 DMC(Dynamic Memory Controller).
>            It sets the frequency for the memory controller and reads the usage counts
>            from hardware.
>  
> 

Applied it. Thanks.

-- 
Best Regards,
Chanwoo Choi
Samsung Electronics

      reply	other threads:[~2019-11-12  0:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20191111181617epcas4p37a34e64e080e11e7f14754dd8dce7d27@epcas4p3.samsung.com>
2019-11-11 18:16 ` [PATCH] PM / devfreq: Kconfig: Drop explicit selection of PM_OPP Leonard Crestez
2019-11-12  0:40   ` Chanwoo Choi [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=2955f629-ffa2-fa5e-6734-a400428a2821@samsung.com \
    --to=cw00.choi@samsung.com \
    --cc=digetx@gmail.com \
    --cc=enric.balletbo@collabora.com \
    --cc=krzk@kernel.org \
    --cc=kyungmin.park@samsung.com \
    --cc=leonard.crestez@nxp.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=myungjoo.ham@samsung.com \
    --cc=rjw@rjwysocki.net \
    --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;
as well as URLs for NNTP newsgroup(s).