Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp9777878rwd; Wed, 21 Jun 2023 11:42:52 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ64NEHgUT4lSzyL0eTUsj8fVVdyOTtK0rw+dieqJV/iDGvuXcrEz6bw1FpzJs9fCU8OIjKc X-Received: by 2002:a17:903:2343:b0:1b5:640a:887a with SMTP id c3-20020a170903234300b001b5640a887amr12553031plh.60.1687372972218; Wed, 21 Jun 2023 11:42:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1687372972; cv=none; d=google.com; s=arc-20160816; b=QJss3MIzK7mKiY643dmnmpn1bD6PTU0JCRZrX1Bo5RhQvPx8pSyYQ0wIG6Kk4Hwq5a 6t2SxkgfYWaRODAZUsQieHJ9p7Lntywg5RdF6r6kWgV5aLMJoKCXTMjm6OsHfNJ1j38e yUvIWdoOrT9gVQo7rOdIylAoA6CPiNbVqSwY4Cr6k1P2m6ZejPuw8qGg7sEPgwZUEBYw w2KZ7cwA47Mn1v23dR6wjvG3hWwes6nwu6QU6vrD07xSndRKNoaXR2KJa6O5zT3lbb8B hGi/ToccCQ6y6GyVNv7YOaJMwSrpp6yETHdYyFaX6GKI181/Q24VPJ4QDPgdt2Yaadso As6g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:date:cc:to:from:subject :dkim-signature:message-id; bh=AqL5jc1PZHDl/xcQeIJ7XwPJkeZ5gnlF6yI+4ZBlQU4=; b=D5mncFn0K1YHblrwJgZ2TvAU5vMt7HhIoBtucK3T1CKRl95DNBMTwYtpO2VA6aumVZ UKPLIkjmLkLtNEN+0tbRvFCzX6xHvM/WFWzKup3BurO986iUe3NLkZ4wAqrdTD62ubkU 9nELSPVBqv095xy2KC/PqVNje1Qa9MH63n5lbzcnvQ0lLs2l+RfjOXWAip7AqMWxRIT2 07qHlWkgxt9i9JjyIOIPO/cLjllOs0YYKNHBq/jiH7uAKa8AMoEM7r7vk6iBDCk7gqzh qNYLQ4UUGk9hX9AI5SAYArPgY06S0qgXFX9pJNbijjM+ACM3MAXdOtzZx3f0VEsv66vo Q/4g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@puri.sm header.s=comms header.b=SwYMtcS5; 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=NONE dis=NONE) header.from=puri.sm Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id u13-20020a170902a60d00b001a9265e6fdasi4466791plq.268.2023.06.21.11.42.40; Wed, 21 Jun 2023 11:42:52 -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=@puri.sm header.s=comms header.b=SwYMtcS5; 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=NONE dis=NONE) header.from=puri.sm Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229774AbjFUSVE (ORCPT + 99 others); Wed, 21 Jun 2023 14:21:04 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48574 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229564AbjFUSU7 (ORCPT ); Wed, 21 Jun 2023 14:20:59 -0400 Received: from comms.puri.sm (comms.puri.sm [159.203.221.185]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B9CCB1BE6; Wed, 21 Jun 2023 11:20:43 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by comms.puri.sm (Postfix) with ESMTP id 43677EB7B8; Wed, 21 Jun 2023 11:20:13 -0700 (PDT) Received: from comms.puri.sm ([127.0.0.1]) by localhost (comms.puri.sm [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P9NW0B-v-ump; Wed, 21 Jun 2023 11:20:12 -0700 (PDT) Message-ID: <1dec928bee02d46688a7041d64f2d951a44f8a9e.camel@puri.sm> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=puri.sm; s=comms; t=1687371612; bh=hogFmiQ6zlNCopb6QR0O5U1FyvV79n//bSPz0BhS3Gw=; h=Subject:From:To:Cc:Date:In-Reply-To:References:From; b=SwYMtcS5iybTRzfxIDZ9jWi4hRPFHNf6znD8CCy3CRVfCL+4y9uH2hnlAnjmTUL4+ zRcjMP3B2wxWGCXyb3Cxey8sy1FcosrO3YDjYqUwSYciu/bVMJJrlwya0D5emag4Wb OyssbFhTL2dvauDZxaV1Rz3sgWcEr++ssXxDkqJgEjcb37w81FvzGgz20xXniIiLjF ATmb94h9EsSTCfm6PvNdopatMxUfWNQOtudi9EtAZLgPrTfJpLO1kHauOMEgS0hA08 V5XrxfW82+pHJGot8B9+0Pgg/Yf3SRpixq8JjS6ubbYTcCH4Xaor8X7a8lEVkDwuWV TfnWhFTM/jWBA== Subject: Re: [PATCH v6 1/2] power: domain: handle genpd correctly when needing interrupts From: Martin Kepplinger To: Ulf Hansson Cc: rafael@kernel.org, khilman@kernel.org, robh@kernel.org, krzysztof.kozlowski@linaro.org, shawnguo@kernel.org, s.hauer@pengutronix.de, festevam@gmail.com, pavel@ucw.cz, kernel@puri.sm, linux-imx@nxp.com, broonie@kernel.org, l.stach@pengutronix.de, aford173@gmail.com, linux-pm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Date: Wed, 21 Jun 2023 20:20:06 +0200 In-Reply-To: References: <20220726083257.1730630-1-martin.kepplinger@puri.sm> <20220726083257.1730630-2-martin.kepplinger@puri.sm> <77baacb930bf2ba1a65cb1515e6795b48d2d4ed5.camel@puri.sm> <3bbba64dc4fd9ef37fb937f5176b1ef50b8b2d73.camel@puri.sm> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.38.3-1+deb11u2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE,URIBL_BLOCKED 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 Am Freitag, dem 23.09.2022 um 15:55 +0200 schrieb Ulf Hansson: > On Thu, 25 Aug 2022 at 09:06, Martin Kepplinger > wrote: > > > > Am Mittwoch, dem 24.08.2022 um 15:30 +0200 schrieb Ulf Hansson: > > > On Mon, 22 Aug 2022 at 10:38, Martin Kepplinger > > > wrote: > > > > > > > > Am Freitag, dem 19.08.2022 um 16:53 +0200 schrieb Ulf Hansson: > > > > > On Fri, 19 Aug 2022 at 11:17, Martin Kepplinger > > > > > wrote: > > > > > > > > > > > > Am Dienstag, dem 26.07.2022 um 17:07 +0200 schrieb Ulf > > > > > > Hansson: > > > > > > > On Tue, 26 Jul 2022 at 10:33, Martin Kepplinger > > > > > > > wrote: > > > > > > > > > > > > > > > > If for example the power-domains' power-supply node > > > > > > > > (regulator) > > > > > > > > needs > > > > > > > > interrupts to work, the current setup with noirq > > > > > > > > callbacks > > > > > > > > cannot > > > > > > > > work; for example a pmic regulator on i2c, when > > > > > > > > suspending, > > > > > > > > usually > > > > > > > > already > > > > > > > > times out during suspend_noirq: > > > > > > > > > > > > > > > > [   41.024193] buck4: failed to disable: -ETIMEDOUT > > > > > > > > > > > > > > > > So fix system suspend and resume for these power- > > > > > > > > domains by > > > > > > > > using > > > > > > > > the > > > > > > > > "outer" suspend/resume callbacks instead. Tested on the > > > > > > > > imx8mq- > > > > > > > > librem5 board, > > > > > > > > but by looking at the dts, this will fix imx8mq-evk and > > > > > > > > possibly > > > > > > > > many other > > > > > > > > boards too. > > > > > > > > > > > > > > > > This is designed so that genpd providers just say "this > > > > > > > > genpd > > > > > > > > needs > > > > > > > > interrupts" (by setting the flag) - without implying an > > > > > > > > implementation. > > > > > > > > > > > > > > > > Initially system suspend problems had been discussed at > > > > > > > > https://lore.kernel.org/linux-arm-kernel/20211002005954.1367653-8-l.stach@pengutronix.de/ > > > > > > > > which led to discussing the pmic that contains the > > > > > > > > regulators > > > > > > > > which > > > > > > > > serve as power-domain power-supplies: > > > > > > > > https://lore.kernel.org/linux-pm/573166b75e524517782471c2b7f96e03fd93d175.camel@puri.sm/T/ > > > > > > > > > > > > > > > > Signed-off-by: Martin Kepplinger > > > > > > > > > > > > > > > > --- > > > > > > > >  drivers/base/power/domain.c | 13 +++++++++++-- > > > > > > > >  include/linux/pm_domain.h   |  5 +++++ > > > > > > > >  2 files changed, 16 insertions(+), 2 deletions(-) > > > > > > > > > > > > > > > > diff --git a/drivers/base/power/domain.c > > > > > > > > b/drivers/base/power/domain.c > > > > > > > > index 5a2e0232862e..58376752a4de 100644 > > > > > > > > --- a/drivers/base/power/domain.c > > > > > > > > +++ b/drivers/base/power/domain.c > > > > > > > > @@ -130,6 +130,7 @@ static const struct genpd_lock_ops > > > > > > > > genpd_spin_ops = { > > > > > > > >  #define genpd_is_active_wakeup(genpd)  (genpd->flags & > > > > > > > > GENPD_FLAG_ACTIVE_WAKEUP) > > > > > > > >  #define genpd_is_cpu_domain(genpd)     (genpd->flags & > > > > > > > > GENPD_FLAG_CPU_DOMAIN) > > > > > > > >  #define genpd_is_rpm_always_on(genpd)  (genpd->flags & > > > > > > > > GENPD_FLAG_RPM_ALWAYS_ON) > > > > > > > > +#define genpd_irq_on(genpd)            (genpd->flags & > > > > > > > > GENPD_FLAG_IRQ_ON) > > > > > > > > > > > > > > > >  static inline bool irq_safe_dev_in_sleep_domain(struct > > > > > > > > device > > > > > > > > *dev, > > > > > > > >                 const struct generic_pm_domain *genpd) > > > > > > > > @@ -2065,8 +2066,15 @@ int pm_genpd_init(struct > > > > > > > > generic_pm_domain > > > > > > > > *genpd, > > > > > > > >         genpd->domain.ops.runtime_suspend = > > > > > > > > genpd_runtime_suspend; > > > > > > > >         genpd->domain.ops.runtime_resume = > > > > > > > > genpd_runtime_resume; > > > > > > > >         genpd->domain.ops.prepare = genpd_prepare; > > > > > > > > -       genpd->domain.ops.suspend_noirq = > > > > > > > > genpd_suspend_noirq; > > > > > > > > -       genpd->domain.ops.resume_noirq = > > > > > > > > genpd_resume_noirq; > > > > > > > > + > > > > > > > > +       if (genpd_irq_on(genpd)) { > > > > > > > > +               genpd->domain.ops.suspend = > > > > > > > > genpd_suspend_noirq; > > > > > > > > +               genpd->domain.ops.resume = > > > > > > > > genpd_resume_noirq; > > > > > > > > +       } else { > > > > > > > > +               genpd->domain.ops.suspend_noirq = > > > > > > > > genpd_suspend_noirq; > > > > > > > > +               genpd->domain.ops.resume_noirq = > > > > > > > > genpd_resume_noirq; > > > > > > > > > > > > > > As we discussed previously, I am thinking that it may be > > > > > > > better > > > > > > > to > > > > > > > move to using genpd->domain.ops.suspend_late and > > > > > > > genpd->domain.ops.resume_early instead. > > > > > > > > > > > > Wouldn't that better be a separate patch (on top)? Do you > > > > > > really > > > > > > want > > > > > > me to change the current behaviour (default case) to from > > > > > > noirq > > > > > > to > > > > > > late? Then I'll resend this series with such a patch added. > > > > > > > > > > Sorry, I wasn't clear enough, the default behaviour should > > > > > remain > > > > > as > > > > > is. > > > > > > > > > > What I meant was, when genpd_irq_on() is true, we should use > > > > > the > > > > > genpd->domain.ops.suspend_late and genpd- > > > > > > domain.ops.resume_early. > > > > > > > > Testing that shows that this isn't working. I can provide the > > > > logs > > > > later, but suspend fails and I think it makes sense: > > > > "suspend_late" > > > > is > > > > simply already too late when i2c (or any needed driver) uses > > > > "suspend". > > > > > > Okay, I see. > > > > > > The reason why I suggested moving the callbacks to > > > "suspend_late", > > > was > > > that I was worried that some of the attached devices to genpd > > > could > > > use "suspend_late" themselves. This is the case for some drivers > > > for > > > DMA/clock/gpio/pinctrl-controllers, for example. That said, I am > > > curious to look at the DT files for the platform you are running, > > > would you mind giving me a pointer? > > > > I'm running > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm64/boot/dts/freescale/imx8mq-librem5.dtsi > > with these (small) patches on top: > > https://source.puri.sm/martin.kepplinger/linux-next/-/commits/5.19.3/librem5 > > Thanks for sharing the information! > > > > > > > > > So, this made me think about this a bit more. In the end, just > > > using > > > different levels (suspend, suspend_late, suspend_noirq) of > > > callbacks > > > are just papering over the real *dependency* problem. > > > > true, it doesn't feel like a stable solution. > > > > > > > > What we need for the genpd provider driver, is to be asked to be > > > suspended under the following conditions: > > > 1. All consumer devices (and child-domains) for its corresponding > > > PM > > > domain have been suspended. > > > 2. All its supplier devices supplies must remain resumed, until > > > the > > > genpd provider has been suspended. > > > > > > Please allow me a few more days to think in more detail about > > > this. > > > > Thanks a lot for thinking about this! > > I have made some more thinking, but it's been a busy period for me, > so > unfortunately I need some additional time (another week). It seems > like I also need to do some prototyping, to convince myself about the > approach. > > So, my apologies for the delay! > > Kind regards > Uffe Hi Ulf and all interested, Has there been any development regarding this bug? - genpd that needs interrupts for power-on/off being run in noirq phases - you remember it? it's been a while :) Anyway I still run these patches and while it's a reasonable workaround IMO, I wanted to check whether you are aware of anything that might solve this. (or maybe it *is* solved and I simply overlooked because my patches still apply?) thanks! martin