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 X-Spam-Level: X-Spam-Status: No, score=-3.7 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 7FFC1C433EF for ; Fri, 17 Sep 2021 11:44:16 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 6A04861212 for ; Fri, 17 Sep 2021 11:44:16 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242002AbhIQLph (ORCPT ); Fri, 17 Sep 2021 07:45:37 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54452 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S241976AbhIQLpf (ORCPT ); Fri, 17 Sep 2021 07:45:35 -0400 Received: from metis.ext.pengutronix.de (metis.ext.pengutronix.de [IPv6:2001:67c:670:201:290:27ff:fe1d:cc33]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0E4DAC061574 for ; Fri, 17 Sep 2021 04:44:14 -0700 (PDT) Received: from gallifrey.ext.pengutronix.de ([2001:67c:670:201:5054:ff:fe8d:eefb] helo=[IPv6:::1]) by metis.ext.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mRCHo-0008GX-7t; Fri, 17 Sep 2021 13:44:08 +0200 Message-ID: <9bcf7b749dca57d42aa2e7afd88b5a26f3eeff2a.camel@pengutronix.de> Subject: Re: [PATCH] arm64: dts: imx8mm-kontron-n801x-som: do not allow to switch off buck2 From: Lucas Stach To: Heiko Thiery , Frieder Schrempf Cc: devicetree@vger.kernel.org, Guido =?ISO-8859-1?Q?G=FCnther?= , Fabio Estevam , Shengjiu Wang , "Angus Ainslie (Purism)" , linux-kernel@vger.kernel.org, Krzysztof Kozlowski , Joakim Zhang , Michael Walle , Rob Herring , NXP Linux Team , Pengutronix Kernel Team , Shawn Guo , Sascha Hauer , linux-arm-kernel@lists.infradead.org Date: Fri, 17 Sep 2021 13:44:04 +0200 In-Reply-To: References: <20210915120325.20248-1-heiko.thiery@gmail.com> <7e7ee4244ababc0a46e0875222c7e37d@walle.cc> <898fd5e0-2073-3689-89b6-2c5071773786@kontron.de> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.40.4 (3.40.4-1.fc34) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 2001:67c:670:201:5054:ff:fe8d:eefb X-SA-Exim-Mail-From: l.stach@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false X-PTX-Original-Recipient: linux-kernel@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am Freitag, dem 17.09.2021 um 09:28 +0200 schrieb Heiko Thiery: > Hi Frieder, > > Am Mi., 15. Sept. 2021 um 14:09 Uhr schrieb Frieder Schrempf > : > > > > On 15.09.21 14:05, Michael Walle wrote: > > > Am 2021-09-15 14:03, schrieb Heiko Thiery: > > > > The buck2 output of the PMIC is the VDD core voltage of the cpu. > > > > Switching off this will poweroff the CPU. Add the 'regulator-always-on' > > > > property to avoid this. > > > > > > Mh, have this ever worked? Is there a commit which introduced a regression? > > > > Yes, this did work before, even without 'regulator-always-on'. I > > currently don't understand why this is needed. The regulator is > > referenced in the CPU nodes as 'cpu-supply'. This should be enough to > > not disable it as long as the CPU is up. > > I rechecked that with 5.11, 5.10 and 5.9 and I see on all of them the > same issue: > > [ 31.716031] vdd-5v: disabling > [ 31.719032] rst-usb-eth2: disabling > [ 31.722553] buck2: disabling > > While on that I tried to compare with other boards and see that they > also have the cpu-voltage marked as "regulator-always-on". The only > exception in dts/freescale is in imx8mq-librem5-devkit.dts [1] that > has not set this property. > > I agree with you and don't understand why this is happening. Has > anyone else an explanation? > > [1] https://elixir.bootlin.com/linux/latest/source/arch/arm64/boot/dts/freescale/imx8mq-librem5-devkit.dts#L319 > Maybe your kernel config is missing the cpufreq driver, so you don't have a consumer of the regulator? Marking the regulator as always-on seems like the right thing to do, you don't want to depend on a consumer showing up to make sure that your CPU voltage isn't cut... Regards, Lucas 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 X-Spam-Level: X-Spam-Status: No, score=-4.1 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 13151C433EF for ; Fri, 17 Sep 2021 11:46:41 +0000 (UTC) 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 mail.kernel.org (Postfix) with ESMTPS id CB21061029 for ; Fri, 17 Sep 2021 11:46:40 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org CB21061029 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=pengutronix.de Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=lists.infradead.org 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: Date:Cc:To:From:Subject:Message-ID:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=O4JMz5jOSYLJW4b9+irbIj8jG4kpJeQLdOTGCfeORF8=; b=uNUMMOx7IpFeoV enmVJKAx7/pkdjXdqWEvtd7RNHHDNzvIolJBOwsbVTBc49R2zCMn20ij/qQps+6WMcvWlEhjeshz5 7TuLvmE8IaDbDkovhllJmBn6z8fmqHBfXVQvtHEjCGPptxauZesEnAjASntoy/BIIAB4jmdAti7sh xRdg0RTnZX4UdHAsAYC4wfixis5PWypnEoxUvbITb/S384YSXM5UL4hlIAjrh+lWrKfIFOvNyHvLQ sJglwjq4Ru50kylUHfQit/kBKfGOemZSPtwxQQprbr2Z1v+Bc0//P8Qvic2NTXEWFRS9qcNxlENgS J8bMRlunUFsPmm0wHUZw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1mRCI8-00DtBJ-1o; Fri, 17 Sep 2021 11:44:28 +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 1mRCI3-00DtAQ-MF for linux-arm-kernel@lists.infradead.org; Fri, 17 Sep 2021 11:44:25 +0000 Received: from gallifrey.ext.pengutronix.de ([2001:67c:670:201:5054:ff:fe8d:eefb] helo=[IPv6:::1]) by metis.ext.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mRCHo-0008GX-7t; Fri, 17 Sep 2021 13:44:08 +0200 Message-ID: <9bcf7b749dca57d42aa2e7afd88b5a26f3eeff2a.camel@pengutronix.de> Subject: Re: [PATCH] arm64: dts: imx8mm-kontron-n801x-som: do not allow to switch off buck2 From: Lucas Stach To: Heiko Thiery , Frieder Schrempf Cc: devicetree@vger.kernel.org, Guido =?ISO-8859-1?Q?G=FCnther?= , Fabio Estevam , Shengjiu Wang , "Angus Ainslie (Purism)" , linux-kernel@vger.kernel.org, Krzysztof Kozlowski , Joakim Zhang , Michael Walle , Rob Herring , NXP Linux Team , Pengutronix Kernel Team , Shawn Guo , Sascha Hauer , linux-arm-kernel@lists.infradead.org Date: Fri, 17 Sep 2021 13:44:04 +0200 In-Reply-To: References: <20210915120325.20248-1-heiko.thiery@gmail.com> <7e7ee4244ababc0a46e0875222c7e37d@walle.cc> <898fd5e0-2073-3689-89b6-2c5071773786@kontron.de> User-Agent: Evolution 3.40.4 (3.40.4-1.fc34) MIME-Version: 1.0 X-SA-Exim-Connect-IP: 2001:67c:670:201:5054:ff:fe8d:eefb X-SA-Exim-Mail-From: l.stach@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-20210917_044423_782414_367F3851 X-CRM114-Status: GOOD ( 23.19 ) 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 Am Freitag, dem 17.09.2021 um 09:28 +0200 schrieb Heiko Thiery: > Hi Frieder, > > Am Mi., 15. Sept. 2021 um 14:09 Uhr schrieb Frieder Schrempf > : > > > > On 15.09.21 14:05, Michael Walle wrote: > > > Am 2021-09-15 14:03, schrieb Heiko Thiery: > > > > The buck2 output of the PMIC is the VDD core voltage of the cpu. > > > > Switching off this will poweroff the CPU. Add the 'regulator-always-on' > > > > property to avoid this. > > > > > > Mh, have this ever worked? Is there a commit which introduced a regression? > > > > Yes, this did work before, even without 'regulator-always-on'. I > > currently don't understand why this is needed. The regulator is > > referenced in the CPU nodes as 'cpu-supply'. This should be enough to > > not disable it as long as the CPU is up. > > I rechecked that with 5.11, 5.10 and 5.9 and I see on all of them the > same issue: > > [ 31.716031] vdd-5v: disabling > [ 31.719032] rst-usb-eth2: disabling > [ 31.722553] buck2: disabling > > While on that I tried to compare with other boards and see that they > also have the cpu-voltage marked as "regulator-always-on". The only > exception in dts/freescale is in imx8mq-librem5-devkit.dts [1] that > has not set this property. > > I agree with you and don't understand why this is happening. Has > anyone else an explanation? > > [1] https://elixir.bootlin.com/linux/latest/source/arch/arm64/boot/dts/freescale/imx8mq-librem5-devkit.dts#L319 > Maybe your kernel config is missing the cpufreq driver, so you don't have a consumer of the regulator? Marking the regulator as always-on seems like the right thing to do, you don't want to depend on a consumer showing up to make sure that your CPU voltage isn't cut... Regards, Lucas _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel