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 98080C54EE9 for ; Tue, 13 Sep 2022 10:26:51 +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:MIME-Version:References:In-Reply-To: Message-Id:Date:Subject:Cc:To:From:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=f/NVed0MXCviJGHmxi2THXLImTdPJbj2IUSka5uVulY=; b=Zi6/1NYqfdpDAM rhl+pmyIkwSzrj8z/TYP/qrceY0eJByRlhZrClPtRLWKpXTipQM02Wc3D/dxg6/08hmNC6VN/K4X+ s+hRLTfaxn0aVVa5Lx1LYeyy03csanB2+h8Cr0NpIpjLji3SDExyQGZps0Jfoqjyp4wWGPIuwC8B5 BVNdQOMsb8KAIrlHBxbLgV3o/LwrLtgfFBuAiraMQGGOMzoCEzBh8SRRwP/6yl8Y00/MhweGlEKjU r1Ue+4SS+jpbYYccPVFUnbzoTTUGcedM2OeD8Y+RTgOOXZsZrH4tIchf4D4EvsNMoaZk06JkOrg7N hR2vkUzScc6R+EPOG10w==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1oY36e-006UqZ-SL; Tue, 13 Sep 2022 10:25:29 +0000 Received: from metis.ext.pengutronix.de ([2001:67c:670:201:290:27ff:fe1d:cc33]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1oY33G-006SUn-7F for linux-arm-kernel@lists.infradead.org; Tue, 13 Sep 2022 10:22:01 +0000 Received: from drehscheibe.grey.stw.pengutronix.de ([2a0a:edc0:0:c01:1d::a2]) by metis.ext.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oY334-0002vk-TH; Tue, 13 Sep 2022 12:21:46 +0200 Received: from [2a0a:edc0:0:1101:1d::28] (helo=dude02.red.stw.pengutronix.de) by drehscheibe.grey.stw.pengutronix.de with esmtp (Exim 4.94.2) (envelope-from ) id 1oY335-000TmK-In; Tue, 13 Sep 2022 12:21:46 +0200 Received: from mfe by dude02.red.stw.pengutronix.de with local (Exim 4.94.2) (envelope-from ) id 1oY333-004prz-BM; Tue, 13 Sep 2022 12:21:45 +0200 From: Marco Felsch To: krzysztof.kozlowski+dt@linaro.org, robh+dt@kernel.org, abelvesa@kernel.org, abel.vesa@linaro.org, mturquette@baylibre.com, sboyd@kernel.org, shawnguo@kernel.org, s.hauer@pengutronix.de, kernel@pengutronix.de, festevam@gmail.com Cc: linux-kernel@vger.kernel.org, Peng Fan , linux-imx@nxp.com, linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org Subject: [RFC PATCH 1/2] clk: add support for critical always-on clocks Date: Tue, 13 Sep 2022 12:21:40 +0200 Message-Id: <20220913102141.971148-2-m.felsch@pengutronix.de> X-Mailer: git-send-email 2.30.2 In-Reply-To: <20220913102141.971148-1-m.felsch@pengutronix.de> References: <20220913102141.971148-1-m.felsch@pengutronix.de> MIME-Version: 1.0 X-SA-Exim-Connect-IP: 2a0a:edc0:0:c01:1d::a2 X-SA-Exim-Mail-From: mfe@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false X-PTX-Original-Recipient: linux-arm-kernel@lists.infradead.org X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220913_032158_299869_63570324 X-CRM114-Status: GOOD ( 13.78 ) 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 Add support to mark specific clocks as always-on (critical), like the regulator-alawys-on property. So the platform integrators can specify the property on a per device basis by specifying it within the firmware and not only within the driver. Unlike the regulator framework the clock framework uses a 1:n matching, which means 1 firmware node can provide up to n clock providers. Therefore the binding uses a string-array so we can specify n clock providers as critical. Signed-off-by: Marco Felsch --- drivers/clk/clk.c | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/drivers/clk/clk.c b/drivers/clk/clk.c index 7fc191c15507..c3651bf96f90 100644 --- a/drivers/clk/clk.c +++ b/drivers/clk/clk.c @@ -3825,6 +3825,22 @@ static int clk_cpy_name(const char **dst_p, const char *src, bool must_exist) return 0; } +static void clk_core_check_critical(struct clk_core *core) +{ + struct fwnode_handle *fwnode = of_fwnode_handle(core->of_node); + const char *prop = "clocks-always-on"; + int ret; + + /* Very early added clocks don't have a fwnode */ + if (!fwnode || !fwnode_property_present(fwnode, prop)) + return; + + /* Mark clock as critical if listed within the clocks-always-on array */ + ret = fwnode_property_match_string(fwnode, prop, core->name); + if (!ret) + core->flags |= CLK_IS_CRITICAL; +} + static int clk_core_populate_parent_map(struct clk_core *core, const struct clk_init_data *init) { @@ -3946,6 +3962,8 @@ __clk_register(struct device *dev, struct device_node *np, struct clk_hw *hw) core->min_rate = 0; core->max_rate = ULONG_MAX; + clk_core_check_critical(core); + ret = clk_core_populate_parent_map(core, init); if (ret) goto fail_parents; -- 2.30.2 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel