Received: by 2002:a6b:fb09:0:0:0:0:0 with SMTP id h9csp1285043iog; Tue, 14 Jun 2022 03:06:19 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwIQ48whO0WE47jZznLttQIBK/LBOA6mgAcwz4GUlksF2+Yv7UPHi5xRyCxAZBfanlFt/X+ X-Received: by 2002:a17:907:7eaa:b0:6df:e82c:f84 with SMTP id qb42-20020a1709077eaa00b006dfe82c0f84mr3591847ejc.590.1655201179224; Tue, 14 Jun 2022 03:06:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1655201179; cv=none; d=google.com; s=arc-20160816; b=LfYTn47Z5flZU4UR/LnhLgVaq5b3xysb+GB1fn7MMXePv8TKxgmSNgCRAatvmst4ls znzIIcajxf7apERz+YNDJ4m+jJvt5soxW26kK8glu6wYQtu/AOFVcR4qe8Gs7zbyWtvP yX16cw31j7pkFcbgiqSASmZz1GRedwCKIqt0WUYqJJI9MvO14xv/Of1QlOsMO3AyYz+7 ozDtzmqwqDnwZYAVZ7bHDmFq4g4Ia1EEOWok0S4kxXlfwiQtkSLhfiT46s3Hh7Wjpm9E eENvXMtcQRMqzIP0+9jx1WVX1ejxBx3EZ4j0w7Uji8xPXmZXnK8WZ/6lLgM0/0ql4IrU HnmA== 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=uRadd473PmDxa7xq2b3B0/WJpjQUQFR7YFCX4pWsX1I=; b=CNdQPj+oMNj2S5HMAbvABuExNC88fcm6dDmNdX+P63gTSIp0/VStI/eaJ0YvuNaD0d NAe0Ye1YbjDhG+lLQ23tNuIiGPlSHp6q70o05Ep5HqUzDq0pq29hzfKpW28n4VygLaHN /ZCdxsW2Z3V3tTO+UiaA2L3XHSsUaV6ahAbrcb7OPA+wJQ8MB061MdrzQPTFFAldAZ2t HKNKX291OQe8paQcDqeGaOzE+dRcVyE7bw0Qh9ZK5tmvJQJmKP478C1qPzNt4M/yzowe OoqqFVpHLcRuCMm6M07jUOiSWSBMVi+1CDWo3KlqX4Hys6eBWlm9mTxhX7QSvw5rCJmL 9LRA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@puri.sm header.s=comms header.b=m1KyYJfq; 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 gb21-20020a170907961500b006f3a874f673si10629847ejc.4.2022.06.14.03.05.46; Tue, 14 Jun 2022 03:06:19 -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=m1KyYJfq; 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 S241587AbiFNJ50 (ORCPT + 99 others); Tue, 14 Jun 2022 05:57:26 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43066 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238421AbiFNJ5Y (ORCPT ); Tue, 14 Jun 2022 05:57:24 -0400 Received: from comms.puri.sm (comms.puri.sm [159.203.221.185]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7583EB74; Tue, 14 Jun 2022 02:57:23 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by comms.puri.sm (Postfix) with ESMTP id 1D9B1E001A; Tue, 14 Jun 2022 02:57:23 -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 zmYV0_fNanVr; Tue, 14 Jun 2022 02:57:22 -0700 (PDT) Message-ID: <8024d9e3b885941084740cb0fb2fc9117acdd069.camel@puri.sm> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=puri.sm; s=comms; t=1655200642; bh=Rey8CK2/AutuqbNI1TttDkE+g6sTkkOOQ0cIeP09/Eg=; h=Subject:From:To:Cc:Date:In-Reply-To:References:From; b=m1KyYJfqGSa8yvppfGNN1HVrJe+k1SP09oiNB9b3GxttpaTCVbfZYSTeCOy19LdSh JjjjAE1SqtzvoPrrS4P7CPg6ERRkyaNUx9iLaxzIFblEVUYsOxGrpPQkryTkYkFw2x ekSi3VQUPNMKR8gwv+Scif1WeJqRUz5LArvWZHK4aBXpKF1Hb7/WKFFxfeEcjdbRk9 n1bDthsdG98QurGxSue03f5oVEVOZaoVLHqgmKVKg8kB7Vsx2S+Hs8tQbmw6fEn1QN 0410pLqoTaGzp2NtKZjlVYQDDmI7bcnr4nTjKmfMb2UsgUhwgErQzLF1afg2GKxJrm ntd7liWKyvYKQ== Subject: Re: regulator: BD71837 PMIC resume during noirq phase? From: Martin Kepplinger To: Mark Brown Cc: matti.vaittinen@fi.rohmeurope.com, lgirdwood@gmail.com, linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, arm-soc , Pengutronix Kernel Team Date: Tue, 14 Jun 2022 11:57:18 +0200 In-Reply-To: References: <573166b75e524517782471c2b7f96e03fd93d175.camel@puri.sm> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.38.3-1 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit 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 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 Dienstag, dem 14.06.2022 um 10:18 +0100 schrieb Mark Brown: > On Tue, Jun 14, 2022 at 11:06:06AM +0200, Martin Kepplinger wrote: > > > and regulator_enable() in imx-pgc is called from > > genpd_resume_noirq(). > > > > At this point, does any workaround or fix come to your mind I could > > test? I guess i2c needs to be resumed too... > > > > Why does power domain only implement resume_noirq? How could I > > untangle > > this? > > Indeed - if a power domain is controlling regulators then I'd not > expect > things to go well if it tries to resume without interrupts, there > will > be some things that can be done purely with GPIOs but that's > depending > on the hardware having wired things up that way and the operations > needed by the power domain mapping well onto what can be done with > GPIOs. and what's the danger when resuming power domains later?: --- a/drivers/base/power/domain.c +++ b/drivers/base/power/domain.c @@ -2062,8 +2062,8 @@ 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; + genpd->domain.ops.suspend = genpd_suspend_noirq; + genpd->domain.ops.resume = genpd_resume_noirq; genpd->domain.ops.freeze_noirq = genpd_freeze_noirq; genpd->domain.ops.thaw_noirq = genpd_thaw_noirq; genpd->domain.ops.poweroff_noirq = genpd_poweroff_noirq; thanks for taking the time, martin