From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 41718C27C40 for ; Thu, 24 Aug 2023 14:26:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=4mfc2iJcV0QrOtEIwOKAZya71JVHqon6yGos3p3zaQU=; b=tbarWuTDtSgCfP RtSYyPpe/rTTc6Q7jS7RhC4jbr3YZVDztqPof4I54uVVeywg4VdNkeC+eeyPEU7nWpTDQziIM/2kn uF01JhpmB/QQdHAg5ewJvF+gTAAguNYALRG5A4NliBJkFkWHJTi2UYAPGVjVJeUoIMd+mrO7r7esq dL/b7Kwy/8fIRiYk/wC1BP9PSdurB1eXCuHke0iI1bxJI6flJdhUaCBpHjeqJXXm88SVcqBMnmpuI m6sTj18GFbQ9GSa11lRVPbi8GpiwaXdDmTZZ2B54NMlBVcDw1ThJajo9KsycylmvhNJu/Ydc419VB UVgtr/kbPv7r5B9USCMQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1qZBHB-003E6R-10; Thu, 24 Aug 2023 14:25:33 +0000 Received: from foss.arm.com ([217.140.110.172]) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1qZBH7-003E4m-12 for linux-arm-kernel@lists.infradead.org; Thu, 24 Aug 2023 14:25:31 +0000 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 09C2DD75; Thu, 24 Aug 2023 07:26:03 -0700 (PDT) Received: from pluto (unknown [172.31.20.19]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 07C9B3F762; Thu, 24 Aug 2023 07:25:20 -0700 (PDT) Date: Thu, 24 Aug 2023 15:25:21 +0100 From: Cristian Marussi To: Stephen Boyd Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, sudeep.holla@arm.com, james.quinlan@broadcom.com, f.fainelli@gmail.com, vincent.guittot@linaro.org, etienne.carriere@linaro.org, peng.fan@oss.nxp.com, chuck.cannon@nxp.com, souvik.chakravarty@arm.com, nicola.mazzucato@arm.com, Michael Turquette , linux-clk@vger.kernel.org Subject: Re: [PATCH 1/6] firmware: arm_scmi: Simplify enable/disable Clock operations Message-ID: References: <20230811161446.636253-1-cristian.marussi@arm.com> <20230811161446.636253-2-cristian.marussi@arm.com> <17bd83d833b59fd4f64eec433589fa55.sboyd@kernel.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20230824_072529_450650_186BA05D X-CRM114-Status: GOOD ( 34.96 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Wed, Aug 23, 2023 at 11:01:17AM -0700, Stephen Boyd wrote: > Quoting Cristian Marussi (2023-08-23 02:02:46) > > On Tue, Aug 22, 2023 at 01:17:15PM -0700, Stephen Boyd wrote: > > > Quoting Cristian Marussi (2023-08-11 09:14:41) > > > > Add a param to Clock enable/disable operation to ask for atomic operation > > > > and remove _atomic version of such operations. > > > > > > > Hi, > > Yo > > > > > > Why? > > > > > > > :D, given that the 2 flavours of SCMI enable/disable ops (and the upcoming > > state_get) just differ in their operating mode (atomic or not) and the > > Clock framework in turn wrap such calls into 4 related and explicitly > > named clk_ops (scmi_clock_enable/scmi_clock_atomic_enable etc) that hint > > at what is being done, seemed to me reasonable to reduce the churn and > > remove a bit of code wrappers in favour of a param. > > Please add these extra details to the commit text about why we're making > the change. > Sure I'll do. > > > > > > > > > > No functional change. > > > > > > > > CC: Michael Turquette > > > > CC: Stephen Boyd > > > > CC: linux-clk@vger.kernel.org > > > > Signed-off-by: Cristian Marussi > > > > --- > > > > drivers/clk/clk-scmi.c | 8 ++++---- > > > > drivers/firmware/arm_scmi/clock.c | 24 ++++++------------------ > > > > include/linux/scmi_protocol.h | 9 ++++----- > > > > 3 files changed, 14 insertions(+), 27 deletions(-) > > > > > > > > diff --git a/drivers/clk/clk-scmi.c b/drivers/clk/clk-scmi.c > > > > index 2c7a830ce308..ff003083e592 100644 > > > > --- a/drivers/clk/clk-scmi.c > > > > +++ b/drivers/clk/clk-scmi.c > > > > @@ -78,28 +78,28 @@ static int scmi_clk_enable(struct clk_hw *hw) > > > > { > > > > struct scmi_clk *clk = to_scmi_clk(hw); > > > > > > > > - return scmi_proto_clk_ops->enable(clk->ph, clk->id); > > > > + return scmi_proto_clk_ops->enable(clk->ph, clk->id, false); > > > > } > > > > > > > > static void scmi_clk_disable(struct clk_hw *hw) > > > > { > > > > struct scmi_clk *clk = to_scmi_clk(hw); > > > > > > > > - scmi_proto_clk_ops->disable(clk->ph, clk->id); > > > > + scmi_proto_clk_ops->disable(clk->ph, clk->id, false); > > > > > > I enjoyed how it was before because I don't know what 'false' means > > > without looking at the ops now. > > > > > > > Yes indeed, I can drop this and rework if you prefer to maintain the old > > API calls, but this would mean that whenever we'll add new atomic > > flavour to some new SCMI clk operations we'll have to add 2 ops instead > > of a parametrized one...this is what would happen also in this series > > with state_get (and what really triggered this refactor) > > > > (and please consider that on the SCMI side, for testing purposes, I would > > prefer to expose always both atomic and non-atomic flavours even if NOT > > both actively used by the Clock framework...like state_get() that can only > > be atomic for Clock frmwk...) > > > > Perhaps we need a local variable to make it more readable. > > static int scmi_clk_enable(struct clk_hw *hw) > { > bool can_sleep = false; > struct scmi_clk *clk = to_scmi_clk(hw); > > return scmi_proto_clk_ops->enable(clk->ph, clk->id, can_sleep); > } > > This let's the reader quickly understand what the parameter means. I'm > OK with adding the function parameter, but a plain 'true' or 'false' > doesn't help with clarity. Thanks for the suggestion, it would help definitely making it more readable, maybe a local define or enum could make it without even putting anything on the stack. Thanks, Cristian _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel