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 DF13AC433F5 for ; Wed, 5 Oct 2022 23:07:20 +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:Message-Id:Date:To:Cc:From:Subject: References:In-Reply-To:MIME-Version:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=1hkRTEJwNGXrQ5M0XzqrKNHqGOFiei0oeB9qm8mc+4M=; b=wIxfT7cX0eZ8sx sIHBjBC4n6hVuVdmrbg1RSDfgrJoWQPZXP0zU5ZIfK7k6ah/6PprrB0bBdba/Gi0AT2M4NjloRNKr rHsr5ITZr3vDxoQFYQ2eOZE1ttmd8kqhC6Q3tGb2nk8FeTnZytmmHruzn1lqAuhVIE+WDb71GZwLS 19HBXPY5uCQlq6/20kuCtq9Q1llk6h539pDLdzZHG+Rnle3V/GgXRDx6pSfx8tyzeurmJvTa9r0qe gy4a2e7qEIWZW6diNUnuhsk+Ix7HusBNgtvoc1pZNeEjsLbKbK65eerRtamnbBUygj/YlA/96dG3+ INIgf1UGDfc/gMa6+7mA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1ogDSx-00GRoZ-74; Wed, 05 Oct 2022 23:06:15 +0000 Received: from ams.source.kernel.org ([145.40.68.75]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1ogDSu-00GRo8-64 for linux-arm-kernel@lists.infradead.org; Wed, 05 Oct 2022 23:06:13 +0000 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id B5AB8B81F7C; Wed, 5 Oct 2022 23:06:10 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 5BA04C433D6; Wed, 5 Oct 2022 23:06:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1665011169; bh=sId7vCZ/BscO4odCRyqbx9YmALMG5hZdxlSUO6EQ//k=; h=In-Reply-To:References:Subject:From:Cc:To:Date:From; b=g0SA5pkg14SPD2N4jgjqhXZIKasfHYgz2p6Jivm4cuDWdSsvZbwtySQtbDTvgmkFk V5b3vcoaT+9b53lICzCBJhsASgNwGkFt1hTB7kyqDVOsaGtlI8mfBpj+bBIyptBFO0 lKSiUnQQDJzLiLpKAvmUBvXEbB2CeKx3Eo+jEib1rn6eoxZYItSWBYSPp7y9HPvWgP uY19coLL0VAnTB6zu+Ft9/81o+baIY4Wkt4+yHOlBC+wiDH71df43M4qRt0F5WK5pX sMsjDMwQ898nucgBzM2GZaR5KQV9GhZtJOFm010ZYJ8g2zphx6ZkgMOEK7vM/InsD1 Hgvi4olUjv7zQ== MIME-Version: 1.0 In-Reply-To: <20221005082348.v43xbjrhbdlbaohv@pengutronix.de> References: <20220913102141.971148-1-m.felsch@pengutronix.de> <20221005082348.v43xbjrhbdlbaohv@pengutronix.de> Subject: Re: [RFC PATCH 0/2] Propose critical clocks From: Stephen Boyd Cc: Peng Fan , linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-imx@nxp.com, Marek Vasut To: Marco Felsch , abel.vesa@linaro.org, abelvesa@kernel.org, festevam@gmail.com, kernel@pengutronix.de, krzysztof.kozlowski+dt@linaro.org, mturquette@baylibre.com, robh+dt@kernel.org, s.hauer@pengutronix.de, shawnguo@kernel.org Date: Wed, 05 Oct 2022 16:06:07 -0700 User-Agent: alot/0.10 Message-Id: <20221005230609.5BA04C433D6@smtp.kernel.org> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20221005_160612_383373_B32F84D0 X-CRM114-Status: GOOD ( 13.02 ) 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 Quoting Marco Felsch (2022-10-05 01:23:48) > Hi Stephen, Michael, > > I know it is a busy time right now, but maybe you have a few minutes for > this RFC. I know it is incomplete, but the interessting part is there > and it would fix a real issue we encountered on the imx8mm-evk's. > There's another approach by Marek[1]. Can you work together on a solution? I think we should step away from trying to make the critical flag work during clk registration, and turn on the clk during provider registration instead. That hopefully makes it simpler. We can keep the clk flag of course, so that the clk can't be turned off, but otherwise we shouldn't need to make registration path check for the property. [1] https://lore.kernel.org/all/20220924174517.458657-1-marex@denx.de/ _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel