From: Cristian Marussi <cristian.marussi@arm.com>
To: Stephen Boyd <sboyd@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, sudeep.holla@arm.com,
james.quinlan@broadcom.com, f.fainelli@gmail.com,
vincent.guittot@linaro.org, peng.fan@oss.nxp.com,
michal.simek@amd.com, quic_sibis@quicinc.com,
quic_nkela@quicinc.com, souvik.chakravarty@arm.com,
mturquette@baylibre.com
Subject: Re: [PATCH v2 2/5] clk: scmi: Add support for state control restricted clocks
Date: Mon, 8 Apr 2024 19:26:09 +0100 [thread overview]
Message-ID: <ZhQ2wRVtKDbenU6q@pluto> (raw)
In-Reply-To: <90ac6d2dce33e8078db7cb5681fb94d7.sboyd@kernel.org>
On Sun, Apr 07, 2024 at 09:48:59PM -0700, Stephen Boyd wrote:
> Quoting Cristian Marussi (2024-03-25 14:00:22)
> > Some exposed SCMI Clocks could be marked as non-supporting state changes.
> > Configure a clk_ops descriptor which does not provide the state change
> > callbacks for such clocks when registering with CLK framework.
> >
> > 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>
> > ---
> > drivers/clk/clk-scmi.c | 22 +++++++++++++++-------
> > 1 file changed, 15 insertions(+), 7 deletions(-)
> >
> > diff --git a/drivers/clk/clk-scmi.c b/drivers/clk/clk-scmi.c
> > index d5d369b052bd..fc9603988d91 100644
> > --- a/drivers/clk/clk-scmi.c
> > +++ b/drivers/clk/clk-scmi.c
> > @@ -18,6 +18,7 @@
> >
> > enum scmi_clk_feats {
> > SCMI_CLK_ATOMIC_SUPPORTED,
> > + SCMI_CLK_STATE_CTRL_FORBIDDEN,
>
> Can it be positive, i.e. SCMI_CLK_STATE_CTRL_SUPPORTED?
Yes of course.
>
> > SCMI_CLK_MAX_FEATS
> > };
> >
> > @@ -230,15 +231,19 @@ scmi_clk_ops_alloc(struct device *dev, unsigned long feats_key)
> > * only the prepare/unprepare API, as allowed by the clock framework
> > * when atomic calls are not available.
> > */
> > - if (feats_key & BIT(SCMI_CLK_ATOMIC_SUPPORTED)) {
> > - ops->enable = scmi_clk_atomic_enable;
> > - ops->disable = scmi_clk_atomic_disable;
> > - ops->is_enabled = scmi_clk_atomic_is_enabled;
> > - } else {
> > - ops->prepare = scmi_clk_enable;
> > - ops->unprepare = scmi_clk_disable;
> > + if (!(feats_key & BIT(SCMI_CLK_STATE_CTRL_FORBIDDEN))) {
> > + if (feats_key & BIT(SCMI_CLK_ATOMIC_SUPPORTED)) {
> > + ops->enable = scmi_clk_atomic_enable;
> > + ops->disable = scmi_clk_atomic_disable;
> > + } else {
> > + ops->prepare = scmi_clk_enable;
> > + ops->unprepare = scmi_clk_disable;
> > + }
> > }
> >
> > + if (feats_key & BIT(SCMI_CLK_ATOMIC_SUPPORTED))
> > + ops->is_enabled = scmi_clk_atomic_is_enabled;
> > +
> > /* Rate ops */
> > ops->recalc_rate = scmi_clk_recalc_rate;
> > ops->round_rate = scmi_clk_round_rate;
> > @@ -288,6 +293,9 @@ scmi_clk_ops_select(struct scmi_clk *sclk, bool atomic_capable,
> > if (atomic_capable && ci->enable_latency <= atomic_threshold)
> > feats_key |= BIT(SCMI_CLK_ATOMIC_SUPPORTED);
> >
> > + if (ci->state_ctrl_forbidden)
>
> Then this is negated.
>
I will rework accordingly
Thanks,
Cristian
next prev parent reply other threads:[~2024-04-08 18:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 21:00 [PATCH v2 0/5] Rework SCMI Clock driver clk_ops setup procedure Cristian Marussi
2024-03-25 21:00 ` [PATCH v2 1/5] clk: scmi: Allocate CLK operations dynamically Cristian Marussi
2024-03-30 3:42 ` Florian Fainelli
2024-04-08 4:38 ` Stephen Boyd
2024-04-08 18:23 ` Cristian Marussi
2024-03-25 21:00 ` [PATCH v2 2/5] clk: scmi: Add support for state control restricted clocks Cristian Marussi
2024-03-30 3:43 ` Florian Fainelli
2024-04-08 4:48 ` Stephen Boyd
2024-04-08 18:26 ` Cristian Marussi [this message]
2024-03-25 21:00 ` [PATCH v2 3/5] clk: scmi: Add support for rate change " Cristian Marussi
2024-03-30 3:43 ` Florian Fainelli
2024-03-25 21:00 ` [PATCH v2 4/5] clk: scmi: Add support for re-parenting " Cristian Marussi
2024-03-30 3:43 ` Florian Fainelli
2024-03-25 21:00 ` [PATCH v2 5/5] clk: scmi: Add support for get/set duty_cycle operations Cristian Marussi
2024-03-30 3:44 ` Florian Fainelli
2024-04-04 14:25 ` [PATCH v2 0/5] Rework SCMI Clock driver clk_ops setup procedure 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=ZhQ2wRVtKDbenU6q@pluto \
--to=cristian.marussi@arm.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=michal.simek@amd.com \
--cc=mturquette@baylibre.com \
--cc=peng.fan@oss.nxp.com \
--cc=quic_nkela@quicinc.com \
--cc=quic_sibis@quicinc.com \
--cc=sboyd@kernel.org \
--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).