All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cristian Marussi <cristian.marussi@arm.com>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: linux-clk@vger.kernel.org,
	Etienne Carriere <etienne.carriere@foss.st.com>,
	Gabriel Fernandez <gabriel.fernandez@foss.st.com>,
	Stephen Boyd <sboyd@kernel.org>
Subject: Re: [PATCH] clk: Drop unused COMMON_CLK_STM32MP157_SCMI config
Date: Fri, 15 Oct 2021 16:21:47 +0100	[thread overview]
Message-ID: <20211015152147.GD6376@e120937-lin> (raw)
In-Reply-To: <20211015150043.140793-1-sudeep.holla@arm.com>

On Fri, Oct 15, 2021 at 04:00:43PM +0100, Sudeep Holla wrote:
> Commit 21e743300dd0 ("clk: stm32mp1: new compatible for secure RCC support")
> introduced a new Kconfig option COMMON_CLK_STM32MP157_SCMI which is not
> used anywhere.
> 
> Further, it looks like this Kconfig option is just to select bunch of other
> options which doesn't sound correct to me. There is no need for another
> SCMI firmware based clock driver and hence the same applies for the config
> option too.
> 
> Let us just drop the unused COMMON_CLK_STM32MP157_SCMI before it gives
> someone idea to write a specific clock driver for this SoC/platform.
> 
> Cc: Etienne Carriere <etienne.carriere@foss.st.com>
> Cc: Gabriel Fernandez <gabriel.fernandez@foss.st.com>
> Cc: Stephen Boyd <sboyd@kernel.org>
> Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
> ---

LGTM.

Reviewed-by: Cristian Marussi <cristian.marussi@arm.com>

Looking at the original commit, and guessing its original aim,
is it not better to put some sort of WARN in the STM32MP157 driver
when the specific "rcc-secure" compatible is found configured BUT
!IS_ENABLED(COMMON_CLK_SCMI) ?

Thanks,
Cristian

>  drivers/clk/Kconfig | 10 ----------
>  1 file changed, 10 deletions(-)
> 
> diff --git a/drivers/clk/Kconfig b/drivers/clk/Kconfig
> index c5b3dc97396a..b64058d1af2d 100644
> --- a/drivers/clk/Kconfig
> +++ b/drivers/clk/Kconfig
> @@ -339,16 +339,6 @@ config COMMON_CLK_STM32MP157
>  	help
>  	  Support for stm32mp157 SoC family clocks
>  
> -config COMMON_CLK_STM32MP157_SCMI
> -	bool "stm32mp157 Clock driver with Trusted Firmware"
> -	depends on COMMON_CLK_STM32MP157
> -	select COMMON_CLK_SCMI
> -	select ARM_SCMI_PROTOCOL
> -	default y
> -	help
> -	  Support for stm32mp157 SoC family clocks with Trusted Firmware using
> -	  SCMI protocol.
> -
>  config COMMON_CLK_STM32F
>  	def_bool COMMON_CLK && (MACH_STM32F429 || MACH_STM32F469 || MACH_STM32F746)
>  	help
> -- 
> 2.25.1
> 

  reply	other threads:[~2021-10-15 15:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-15 15:00 [PATCH] clk: Drop unused COMMON_CLK_STM32MP157_SCMI config Sudeep Holla
2021-10-15 15:21 ` Cristian Marussi [this message]
2021-10-15 16:26   ` Sudeep Holla
2021-12-01 15:51 ` Sudeep Holla
2022-01-06  1:23 ` Stephen Boyd

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=20211015152147.GD6376@e120937-lin \
    --to=cristian.marussi@arm.com \
    --cc=etienne.carriere@foss.st.com \
    --cc=gabriel.fernandez@foss.st.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=sboyd@kernel.org \
    --cc=sudeep.holla@arm.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 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.