linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Walter Lozano <walter.lozano@collabora.com>
Cc: rjw@rjwysocki.net, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org, kernel@collabora.com
Subject: Re: [PATCH] cpufreq: imx: Select NVMEM_IMX_OCOTP
Date: Wed, 15 Jul 2020 09:14:18 +0530	[thread overview]
Message-ID: <20200715034418.fnpoaqynvxlkcype@vireshk-i7> (raw)
In-Reply-To: <20200714184356.32749-1-walter.lozano@collabora.com>

On 14-07-20, 15:43, Walter Lozano wrote:
> When probing cpufreq for iMX6 the values in the efuse needs to be
> read which requires NVMEM_IMX_OCOTP. If this option is not enabled,
> the probe will be deferred forever and cpufreq won't be available.
> 
> This patch forces the selection of the required configuration option.
> 
> Signed-off-by: Walter Lozano <walter.lozano@collabora.com>
> ---
>  drivers/cpufreq/Kconfig.arm | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/cpufreq/Kconfig.arm b/drivers/cpufreq/Kconfig.arm
> index c6cbfc8baf72..ce0227c429cf 100644
> --- a/drivers/cpufreq/Kconfig.arm
> +++ b/drivers/cpufreq/Kconfig.arm
> @@ -93,6 +93,7 @@ config ARM_IMX6Q_CPUFREQ
>  	tristate "Freescale i.MX6 cpufreq support"
>  	depends on ARCH_MXC
>  	depends on REGULATOR_ANATOP
> +	select NVMEM_IMX_OCOTP
>  	select PM_OPP
>  	help
>  	  This adds cpufreq driver support for Freescale i.MX6 series SoCs.

Applied. Thanks.

-- 
viresh

      reply	other threads:[~2020-07-15  3:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-14 18:43 [PATCH] cpufreq: imx: Select NVMEM_IMX_OCOTP Walter Lozano
2020-07-15  3:44 ` Viresh Kumar [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=20200715034418.fnpoaqynvxlkcype@vireshk-i7 \
    --to=viresh.kumar@linaro.org \
    --cc=kernel@collabora.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=walter.lozano@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).