soc.lore.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh@nvidia.com>
To: Dmitry Osipenko <digetx@gmail.com>,
	Thierry Reding <treding@nvidia.com>,
	Arnd Bergmann <arnd@kernel.org>
Cc: Mark Brown <broonie@kernel.org>, <soc@kernel.org>,
	<linux-kernel@vger.kernel.org>, <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH v2] soc/tegra: Make regulator couplers depend on CONFIG_REGULATOR
Date: Thu, 22 Jul 2021 11:49:30 +0100	[thread overview]
Message-ID: <770eb9dc-ba9a-acfd-b73a-23e7628dbcb1@nvidia.com> (raw)
In-Reply-To: <20210721232616.1935-1-digetx@gmail.com>


On 22/07/2021 00:26, Dmitry Osipenko wrote:
> The regulator coupler drivers now use regulator-driver API function that
> isn't available during compile-testing. Make regulator coupler drivers
> dependent on CONFIG_REGULATOR in Kconfig.
> 
> Fixes: 03978d42ed0d ("soc/tegra: regulators: Bump voltages on system reboot")
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
> ---
> 
> Changelog:
> 
> v2: - No changes. Re-sending to Arnd Bergmann and soc@kernel.org.
> 
>  drivers/soc/tegra/Kconfig | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/soc/tegra/Kconfig b/drivers/soc/tegra/Kconfig
> index db49075b1946..1224e1c8c2c9 100644
> --- a/drivers/soc/tegra/Kconfig
> +++ b/drivers/soc/tegra/Kconfig
> @@ -15,7 +15,7 @@ config ARCH_TEGRA_2x_SOC
>  	select PL310_ERRATA_769419 if CACHE_L2X0
>  	select SOC_TEGRA_FLOWCTRL
>  	select SOC_TEGRA_PMC
> -	select SOC_TEGRA20_VOLTAGE_COUPLER
> +	select SOC_TEGRA20_VOLTAGE_COUPLER if REGULATOR
>  	select TEGRA_TIMER
>  	help
>  	  Support for NVIDIA Tegra AP20 and T20 processors, based on the
> @@ -29,7 +29,7 @@ config ARCH_TEGRA_3x_SOC
>  	select PL310_ERRATA_769419 if CACHE_L2X0
>  	select SOC_TEGRA_FLOWCTRL
>  	select SOC_TEGRA_PMC
> -	select SOC_TEGRA30_VOLTAGE_COUPLER
> +	select SOC_TEGRA30_VOLTAGE_COUPLER if REGULATOR
>  	select TEGRA_TIMER
>  	help
>  	  Support for NVIDIA Tegra T30 processor family, based on the
> @@ -154,7 +154,9 @@ config SOC_TEGRA_POWERGATE_BPMP
>  config SOC_TEGRA20_VOLTAGE_COUPLER
>  	bool "Voltage scaling support for Tegra20 SoCs"
>  	depends on ARCH_TEGRA_2x_SOC || COMPILE_TEST
> +	depends on REGULATOR
>  
>  config SOC_TEGRA30_VOLTAGE_COUPLER
>  	bool "Voltage scaling support for Tegra30 SoCs"
>  	depends on ARCH_TEGRA_3x_SOC || COMPILE_TEST
> +	depends on REGULATOR
> 


Acked-by: Jon Hunter <jonathanh@nvidia.com>

Thanks!
Jon

-- 
nvpublic

  reply	other threads:[~2021-07-22 10:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-21 23:26 [PATCH v2] soc/tegra: Make regulator couplers depend on CONFIG_REGULATOR Dmitry Osipenko
2021-07-22 10:49 ` Jon Hunter [this message]
2021-08-02 14:36 ` Thierry Reding
2021-08-02 15:03   ` Arnd Bergmann
2021-08-02 15:05     ` Arnd Bergmann
2021-08-02 16:23       ` Thierry Reding

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=770eb9dc-ba9a-acfd-b73a-23e7628dbcb1@nvidia.com \
    --to=jonathanh@nvidia.com \
    --cc=arnd@kernel.org \
    --cc=broonie@kernel.org \
    --cc=digetx@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=soc@kernel.org \
    --cc=treding@nvidia.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).