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;
Message-ID: <dda3847e74ddbcde86342210e44247973a24e5f6.camel@puri.sm>
Subject: Re: regulator: BD71837 PMIC resume during noirq phase?
From:   Martin Kepplinger <martin.kepplinger@puri.sm>
To:     Mark Brown <broonie@kernel.org>
Cc:     matti.vaittinen@fi.rohmeurope.com, lgirdwood@gmail.com,
        linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
        arm-soc <linux-arm-kernel@lists.infradead.org>,
        Pengutronix Kernel Team <kernel@pengutronix.de>
Date:   Mon, 11 Jul 2022 11:52:10 +0200
In-Reply-To: <Yqhf7/3B0l9+3dQH@sirena.org.uk>
References: <573166b75e524517782471c2b7f96e03fd93d175.camel@puri.sm>
         <YqhSXuHMR6kuFu/A@sirena.org.uk>
         <8024d9e3b885941084740cb0fb2fc9117acdd069.camel@puri.sm>
         <Yqhf7/3B0l9+3dQH@sirena.org.uk>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.38.3-1 
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

Am Dienstag, dem 14.06.2022 um 11:16 +0100 schrieb Mark Brown:
> On Tue, Jun 14, 2022 at 11:57:18AM +0200, Martin Kepplinger wrote:
> > Am Dienstag, dem 14.06.2022 um 10:18 +0100 schrieb Mark Brown:
> 
> > > 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?:
> 
> If there's a device that needs to early resume in a power domain that
> needs to do something on resume then presumably this will mess up the
> ordering.  You probably need a separate power domain type, or both
> operations.

hi Mark, the followup to this would be my first try to fix this:

https://lore.kernel.org/linux-arm-kernel/20220711094549.3445566-1-martin.kepplinger@puri.sm/T/#t

thank you for you help so far,

                             martin