[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bd8cd2836a219b36e14cddc504527dc3.sboyd@kernel.org>
Date: Wed, 06 Sep 2023 14:38:24 -0700
From: Stephen Boyd <sboyd@...nel.org>
To: Cristian Marussi <cristian.marussi@....com>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Cc: sudeep.holla@....com, james.quinlan@...adcom.com,
f.fainelli@...il.com, vincent.guittot@...aro.org,
etienne.carriere@...s.st.com, peng.fan@....nxp.com,
chuck.cannon@....com, souvik.chakravarty@....com,
nicola.mazzucato@....com,
Cristian Marussi <cristian.marussi@....com>,
Michael Turquette <mturquette@...libre.com>,
linux-clk@...r.kernel.org
Subject: Re: [PATCH v2 1/6] firmware: arm_scmi: Simplify enable/disable Clock operations
Quoting Cristian Marussi (2023-08-26 05:53:03)
> SCMI Clock enable/disable operations come in 2 different flavours which
> simply just differ in how the underlying SCMI transactions is carried on:
> atomic or not.
>
> Currently we expose such SCMI operations through 2 distinctly named
> wrappers, that, in turn, are wrapped into another couple of similarly and
> distinctly named callbacks inside SCMI Clock driver user.
>
> Reduce the churn of duplicated wrappers by adding a param to SCMI Clock
> enable/disable operations to ask for atomic operation while removing the
> _atomic version of such operations.
>
> No functional change.
>
> CC: Michael Turquette <mturquette@...libre.com>
> CC: Stephen Boyd <sboyd@...nel.org>
> CC: linux-clk@...r.kernel.org
> Signed-off-by: Cristian Marussi <cristian.marussi@....com>
> ---
Acked-by: Stephen Boyd <sboyd@...nel.org>
Powered by blists - more mailing lists