From: Stephen Boyd <sboyd@kernel.org>
To: Cristian Marussi <cristian.marussi@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: sudeep.holla@arm.com, james.quinlan@broadcom.com,
f.fainelli@gmail.com, vincent.guittot@linaro.org,
etienne.carriere@foss.st.com, peng.fan@oss.nxp.com,
chuck.cannon@nxp.com, souvik.chakravarty@arm.com,
nicola.mazzucato@arm.com,
Cristian Marussi <cristian.marussi@arm.com>,
Michael Turquette <mturquette@baylibre.com>,
linux-clk@vger.kernel.org
Subject: Re: [PATCH v2 1/6] firmware: arm_scmi: Simplify enable/disable Clock operations
Date: Wed, 06 Sep 2023 14:38:24 -0700 [thread overview]
Message-ID: <bd8cd2836a219b36e14cddc504527dc3.sboyd@kernel.org> (raw)
In-Reply-To: <20230826125308.462328-2-cristian.marussi@arm.com>
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@baylibre.com>
> CC: Stephen Boyd <sboyd@kernel.org>
> CC: linux-clk@vger.kernel.org
> Signed-off-by: Cristian Marussi <cristian.marussi@arm.com>
> ---
Acked-by: Stephen Boyd <sboyd@kernel.org>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-09-06 21:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-26 12:53 [PATCH v2 0/6] Add SCMI v3.2 Clock new CONFIGs support Cristian Marussi
2023-08-26 12:53 ` [PATCH v2 1/6] firmware: arm_scmi: Simplify enable/disable Clock operations Cristian Marussi
2023-09-06 21:38 ` Stephen Boyd [this message]
2023-08-26 12:53 ` [PATCH v2 2/6] firmware: arm_scmi: Add Clock v3.2 CONFIG_SET support Cristian Marussi
2023-08-26 12:53 ` [PATCH v2 3/6] firmware: arm_scmi: Add v3.2 Clock CONFIG_GET support Cristian Marussi
2023-08-26 12:53 ` [PATCH v2 4/6] firmware: arm_scmi: Add Clock .state_get support to pre-v3.2 Cristian Marussi
2023-08-26 12:53 ` [PATCH v2 5/6] clk: scmi: Add support for .is_enabled clk_ops Cristian Marussi
2023-09-06 21:38 ` Stephen Boyd
2023-08-26 12:53 ` [PATCH v2 6/6] firmware: arm_scmi: Add Clock OEM config clock operations Cristian Marussi
2023-09-21 13:54 ` [PATCH v2 0/6] Add SCMI v3.2 Clock new CONFIGs support Sudeep Holla
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=bd8cd2836a219b36e14cddc504527dc3.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=chuck.cannon@nxp.com \
--cc=cristian.marussi@arm.com \
--cc=etienne.carriere@foss.st.com \
--cc=f.fainelli@gmail.com \
--cc=james.quinlan@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=nicola.mazzucato@arm.com \
--cc=peng.fan@oss.nxp.com \
--cc=souvik.chakravarty@arm.com \
--cc=sudeep.holla@arm.com \
--cc=vincent.guittot@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).