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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 039B1C32771 for ; Fri, 19 Aug 2022 14:54:39 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1349066AbiHSOyi (ORCPT ); Fri, 19 Aug 2022 10:54:38 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36964 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1348729AbiHSOyh (ORCPT ); Fri, 19 Aug 2022 10:54:37 -0400 Received: from mail-lj1-x234.google.com (mail-lj1-x234.google.com [IPv6:2a00:1450:4864:20::234]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3797DD126C for ; Fri, 19 Aug 2022 07:54:36 -0700 (PDT) Received: by mail-lj1-x234.google.com with SMTP id s9so4750719ljs.6 for ; Fri, 19 Aug 2022 07:54:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc; bh=RB7AhKhD6AGVN/FWM8EefpXqGSUdKLi/83gJNo8P8A8=; b=ukZZs/HNQ7J9Zv6RG2j0LdMZFmvFxJrKEWtRHDYURQ+zit353wTcB/yZf7UbnuMtCC IYIAQXew86cYDr2fvuAWbPb0YSbeZOImE906+CpGl/s7BZJPgv6GTV+O91jj2CIGU7L5 OFB/YM9cZB5zAy2zgPH+5dCfYRlL1TduBVITtEXjwc6RlDOcqm/4TuFj05rhAMj5Ih4r 61hw0HWDzrg37O1peBmsoSw7bUdkVmrDPYGBE5p80Glr3gqwNl+pUyN3LEmSRj/+larM M3vNc4bh5+WTZms2a7uHR4oWU5xJY6qIhYaIYmyW0PhNkRQTscAnwi81KlFbl/+9kP6M LZoA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc; bh=RB7AhKhD6AGVN/FWM8EefpXqGSUdKLi/83gJNo8P8A8=; b=b08EwnBPviw2herioa+tlkc+InnZ1w2HqduPSHpuqwasPHia3r0Xz348+LrtOABSSV bHGPZZqZdgO7YutMRUtj/++j02JBBctQzsC/Uhb9d1Io2edW4V1WE/T39UmA0rzH7EH/ KDyBXCCrBUxx4DDVF6y0jUWCbpbGB1Zx7iJiOdQv7MEH1Yd2ZhDajvmO7rWcE+U5lRvO 7BkqJp9FbzqOKtzW0nprgFqy8k9yY7lVdWZ5a9zS1OSkZ58KO9lderaseWpEhV8ZUEui aU/HnQ6q71g48VI5yiZI7MNtAb8q1DjzihsIvFPYV9n+HgSH8npXZZTwCNVnZ1slOrWF OnPg== X-Gm-Message-State: ACgBeo3zOiDc/7Sc1ERcZPPwbEjMRY3R8SRMm9cxL+Mys0/kEofDCUWM Rk1Mkoji5D0Rlb0njEH4GjK73d/vc+5FENDytUqxizWxmpWLzw== X-Google-Smtp-Source: AA6agR4LKuTTBMhjnkTTLmdSIUoln5Khx5nC3j9KNqc8+z3/j2pYHnYHmoYM6uxvbd4BKVFc1yC9kLBk0j+xNy3GIBE= X-Received: by 2002:a05:651c:223:b0:261:beb4:1c85 with SMTP id z3-20020a05651c022300b00261beb41c85mr751234ljn.463.1660920874560; Fri, 19 Aug 2022 07:54:34 -0700 (PDT) MIME-Version: 1.0 References: <20220726083257.1730630-1-martin.kepplinger@puri.sm> <20220726083257.1730630-2-martin.kepplinger@puri.sm> In-Reply-To: From: Ulf Hansson Date: Fri, 19 Aug 2022 16:53:58 +0200 Message-ID: Subject: Re: [PATCH v6 1/2] power: domain: handle genpd correctly when needing interrupts To: Martin Kepplinger 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 Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org 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. Kind regards Uffe