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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id F0D55EE49AB for ; Tue, 22 Aug 2023 20:22:56 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229491AbjHVUW5 (ORCPT ); Tue, 22 Aug 2023 16:22:57 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38902 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230478AbjHVUW5 (ORCPT ); Tue, 22 Aug 2023 16:22:57 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6A1E4CE5; Tue, 22 Aug 2023 13:22:55 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id EE95B651BE; Tue, 22 Aug 2023 20:22:54 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 4EBF2C433C7; Tue, 22 Aug 2023 20:22:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1692735774; bh=VN6UbrzxU3/tiuKAUGglA+ntmPXczUDP6h8hs5I/Jeo=; h=In-Reply-To:References:Subject:From:Cc:To:Date:From; b=nQ5zC2VwByHevveqEV3GftNQx7bHYHKnmz7qjnv3hOzzEIx69J1KNszwQC5taVoKg Fq+PKpEpB9aVZSaz3F7lJhpRN69EBwqEentgGDCzYhlHnzw3I8YPFlITcAmlSw74oa 6jgNJgAQ3snkI4pBEBWBIvEACo9Peb8BFsyammwIx5DDT2RpEpR2ZtODwd3EJOWJDD L38iVqfeIUuFa64XQAXB7yfHyk6eCMLmUpc4JOgLb72QfETl5FIvHnIGnpLAQfbAQ+ 2I2GjJCzdUpQeb0rF5PJMdo0iD32aLnnPVQU6sVnV0B5w3vtVtN0oJ6OkIlCYrhavv aXVEnUIRmeWHA== Message-ID: <98a734c6b1c9d8dc0bbdf976389c8af6.sboyd@kernel.org> Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable In-Reply-To: <20230811161446.636253-6-cristian.marussi@arm.com> References: <20230811161446.636253-1-cristian.marussi@arm.com> <20230811161446.636253-6-cristian.marussi@arm.com> Subject: Re: [PATCH 5/6] clk: scmi: Add support for .is_enabled clk_ops From: Stephen Boyd Cc: 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, Cristian Marussi , Michael Turquette , linux-clk@vger.kernel.org To: Cristian Marussi , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Date: Tue, 22 Aug 2023 13:22:52 -0700 User-Agent: alot/0.10 Precedence: bulk List-ID: X-Mailing-List: linux-clk@vger.kernel.org Quoting Cristian Marussi (2023-08-11 09:14:45) > Add support for .is_enabled atomic clk_ops using the related SCMI Clock > operation in atomic mode, if available. >=20 > Note that the .is_enabled callback will be supported by this SCMI Clock > driver only if the configured underlying SCMI transport does support atom= ic > operations. >=20 > CC: Michael Turquette > CC: Stephen Boyd > CC: linux-clk@vger.kernel.org > Signed-off-by: Cristian Marussi > --- Acked-by: Stephen Boyd