Received: by 2002:a6b:500f:0:0:0:0:0 with SMTP id e15csp932179iob; Wed, 18 May 2022 16:54:05 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyPSajXuMkveO9Y8Pb0vyTpi56Z+mtCOvLWk9P+yCa4TUdQ1E9TZb1H4mEXwA4USNhTRDK8 X-Received: by 2002:a17:90a:e54c:b0:1df:9f47:41bc with SMTP id ei12-20020a17090ae54c00b001df9f4741bcmr2075170pjb.142.1652918045148; Wed, 18 May 2022 16:54:05 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1652918045; cv=none; d=google.com; s=arc-20160816; b=Brl4qCccO1mRorMpOYonYki33ccBHgErgP/vqcCQWgTKSPmsL+z5DM73aq9ia9toiD L2klWYxvioJT1tMOyvNizqZEVxt5bBduxBXAK090Vhms6+eSBwWwMwOgYobqYnaAyMsY GmgpqoNX1off6OlXZ2QlkQPRukok5RxBckhBSQmcu804QbbAraMx4H/pFkUbtg1MsCJI PYZi+F2U9wleuNAeyRozKP3u7LM7aXRxwQcXZwfac+NUe4dU0CZsqR7mWBOx/Ikan/l7 vm7Z14TBxf+POW2iRqMZVhSOVEwPLfMU72i20ypVHz8tzSHBqyD0Pr/Gr/HCXTk6BOoX UTBw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=r48GKaexilEZNN+sQI3f0KxD7Fc9KKp25yevrNkJt6M=; b=j8wvVPAFWaAwIUyG6ZW7g/KIJvIUlzTPnbupYOpgeUiSJzujJD/5E0FTWLk2fMRi3e 8Z7GNpBO7udpOf0L3B/bu+D/pFxKNgIvINqKUjJwVo0txo7OnStJHwI6o1VYNJi0NoD7 5HzHuNzWEOi7Ew8z5T9sfuoztimtnOIgJXQjNdSY/Sk5uNoy/FM2zZqpGzh7/OYwDCpB MYRE+o3/kKIwOqC/0ntEG4q8481/tBJ3vba0R007UV3o0e3g4mqP0UbaAPHGKZjZe4SI mtQmEszk6U/HkN8I6MV7PIWf69uvzB4HtnozNChlfYNLCR9eAEYjYp2r9+OJgfCgHQYA lEdA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=Uzpo+Wgk; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id x40-20020a056a0018a800b0050de3100e2asi5595136pfh.97.2022.05.18.16.53.46; Wed, 18 May 2022 16:54:05 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=Uzpo+Wgk; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230114AbiERWq2 (ORCPT + 99 others); Wed, 18 May 2022 18:46:28 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59236 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229885AbiERWq0 (ORCPT ); Wed, 18 May 2022 18:46:26 -0400 Received: from mail-yb1-xb2e.google.com (mail-yb1-xb2e.google.com [IPv6:2607:f8b0:4864:20::b2e]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0B5B07DE23; Wed, 18 May 2022 15:46:25 -0700 (PDT) Received: by mail-yb1-xb2e.google.com with SMTP id q135so6093612ybg.10; Wed, 18 May 2022 15:46:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=r48GKaexilEZNN+sQI3f0KxD7Fc9KKp25yevrNkJt6M=; b=Uzpo+Wgkuo7R9nwjoHz1Ywf5spGLvNmVK+Xc6NxnoGeZGsW9V8khu/KycVadRKaXiy iq3kVj+dY8e4KMrH8HSV5JV/KPPFunpcLjWea7QhqBHGggAcffOYB2Frt9evVt/HhO2Y 0mulST3hR6HRg4ftUvKogatrBdZfVpv2crnQuJml1ybZmKZl2IRfEam1UbH4Fx5sR9GC ARYrsqhHqqY40hR95yK83uSNwJfkOYJoQDmM5Axo3wMICESqCKQ1dVYgAzqypMr8X8FG a5E6revze3QNx75jZgt2mFBXg70+yGgDA1RC+Xd+9z9CclvEK2CPPj8s4XAUsjliPJZa p1fg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=r48GKaexilEZNN+sQI3f0KxD7Fc9KKp25yevrNkJt6M=; b=Msogf2aF+VwbXxeH/WG8iErOR5qsUImIkPLZWVWm/SUkDE34iatdYRJKZ2Sq5/lvRL x+0Ws6VO3q7RvlTaHGwXHDMmEV87bhdkDwpkII0aCEWtF5K8gQmsy+5XKnzFyGm88oMA gMgrQlTZZkkZFetLO3nCLimWMKyEHN0Ro5II+hRVVXRh3VnDzVoSLlzzR65Y5F6keczR m4vi+AyegTVj2WESP+pQk8XpVeP5MEjmGQ9QMQVZ5EPmMXgxwzJIrcWrfYBQFnv82sa4 BMoCDiYeClw7cfq+q6piVFkGRcz+OzdHpjSYrD1hKq2rtI+x8vT86vd0/l0aidJScwHN ftJQ== X-Gm-Message-State: AOAM533uiE6pa45OCBjpfJ9MtgkwszDnX2ERq8NOBjtI2CEDxNv9Mb8e 6Zs3zT8+NWeKIfCzmZY2ONT4IulRce7wpzp/PBFKhiEl X-Received: by 2002:a25:748b:0:b0:64d:b0ec:2c68 with SMTP id p133-20020a25748b000000b0064db0ec2c68mr1790213ybc.173.1652913984223; Wed, 18 May 2022 15:46:24 -0700 (PDT) MIME-Version: 1.0 References: <20220415104951.27104-1-linux@fw-web.de> <20220415104951.27104-2-linux@fw-web.de> <11363549.CDJkKcVGEf@phil> In-Reply-To: <11363549.CDJkKcVGEf@phil> From: Peter Geis Date: Wed, 18 May 2022 18:46:12 -0400 Message-ID: Subject: Re: [PATCH 1/3] arm64: dts: rockchip: set display regulators to always-on on BPI-R2-Pro To: Heiko Stuebner Cc: Frank Wunderlich , Frank Wunderlich , Rob Herring , Krzysztof Kozlowski , devicetree , arm-mail-list , "open list:ARM/Rockchip SoC..." , Linux Kernel Mailing List Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, May 17, 2022 at 2:47 PM Heiko Stuebner wrote: > > Am Freitag, 15. April 2022, 12:49:49 CEST schrieb Frank Wunderlich: > > From: Frank Wunderlich > > > > Set display related regulators to always-on on Banana PI R2 Pro > > board. > > Hmm, I'd expect some sort of explanation for the "why" here. > It looks like both the gpu patch as well as the vop patch do > reference the relevant regulators for the gpu+hdmi nodes, > so in theory this shouldn't be necessary anymore? I agree the hdmi power nodes don't need to be always on, if the hdmi driver is handling them correctly. Unfortunately the gpu power supply needs to stay always on until the issues with power-domains not being regulator aware is resolved. Otherwise we run into issues like the one mentioned in Lee's email, and issues where the gpu-regulator gets shut down and we start getting mmu faults. > > > > > Signed-off-by: Frank Wunderlich > > --- > > arch/arm64/boot/dts/rockchip/rk3568-bpi-r2-pro.dts | 3 +++ > > 1 file changed, 3 insertions(+) > > > > diff --git a/arch/arm64/boot/dts/rockchip/rk3568-bpi-r2-pro.dts b/arch/arm64/boot/dts/rockchip/rk3568-bpi-r2-pro.dts > > index 2700fb18a3bc..0950f9659bb4 100644 > > --- a/arch/arm64/boot/dts/rockchip/rk3568-bpi-r2-pro.dts > > +++ b/arch/arm64/boot/dts/rockchip/rk3568-bpi-r2-pro.dts > > @@ -225,6 +225,7 @@ regulator-state-mem { > > > > vdd_gpu: DCDC_REG2 { > > regulator-name = "vdd_gpu"; > > + regulator-always-on; > > regulator-init-microvolt = <900000>; > > regulator-initial-mode = <0x2>; > > regulator-min-microvolt = <500000>; > > @@ -274,6 +275,7 @@ regulator-state-mem { > > > > vdda0v9_image: LDO_REG1 { > > regulator-name = "vdda0v9_image"; > > + regulator-always-on; > > regulator-min-microvolt = <900000>; > > regulator-max-microvolt = <900000>; > > > > @@ -369,6 +371,7 @@ regulator-state-mem { > > > > vcca1v8_image: LDO_REG9 { > > regulator-name = "vcca1v8_image"; > > + regulator-always-on; > > regulator-min-microvolt = <1800000>; > > regulator-max-microvolt = <1800000>; > > > > > > > >