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 9E0F7C43334 for ; Tue, 14 Jun 2022 10:16:24 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234474AbiFNKQX (ORCPT ); Tue, 14 Jun 2022 06:16:23 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:32894 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232416AbiFNKQX (ORCPT ); Tue, 14 Jun 2022 06:16:23 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [IPv6:2604:1380:4601:e00::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9E84A46C8B; Tue, 14 Jun 2022 03:16:22 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id 647E3B817E0; Tue, 14 Jun 2022 10:16:21 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 70B69C3411B; Tue, 14 Jun 2022 10:16:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1655201780; bh=9ERUcLB6d+TQPmFdYA4ZdtjoUd5ph1q6+6yNmsUj4O8=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=RGr2f0vmGyHowRBOd/c0Z2bqSbBm1sfbnO4qAg6g0qGxGBv6nseo1OazOpT/SYf7+ 56DCPlzjz5Ye0Emms2o9IBmCBjiczFyPWWCNbFaDZYipsLmBMAnXFADzUB0CHFbhNA ZrWOln6Yzho+tJS4ttL7Jh8oVryS0hvn3+OkAcSwwF2YgBCEGXQquwYoN1sDyGmYZD P5haf0phyHe4k9l/LvU2CFiKL8eyU/GUJwzSfaxFrBil8VquWVruvwiJHus67cnet9 rq7i0dyDfgGO33n6YlLbC67TuP4Zo+so0Hj/JDg04Ji9PnLz1NSeNiAwR+eKVsTG8K Cl2fspzdYzqXA== Date: Tue, 14 Jun 2022 11:16:15 +0100 From: Mark Brown To: Martin Kepplinger Cc: matti.vaittinen@fi.rohmeurope.com, lgirdwood@gmail.com, linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, arm-soc , Pengutronix Kernel Team Subject: Re: regulator: BD71837 PMIC resume during noirq phase? Message-ID: References: <573166b75e524517782471c2b7f96e03fd93d175.camel@puri.sm> <8024d9e3b885941084740cb0fb2fc9117acdd069.camel@puri.sm> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="FwJPrEqu2igwCvTs" Content-Disposition: inline In-Reply-To: <8024d9e3b885941084740cb0fb2fc9117acdd069.camel@puri.sm> X-Cookie: DYSLEXICS OF THE WORLD, UNTIE! Precedence: bulk List-ID: X-Mailing-List: linux-pm@vger.kernel.org --FwJPrEqu2igwCvTs Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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. >=20 > 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. --FwJPrEqu2igwCvTs Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmKoX+4ACgkQJNaLcl1U h9DzTAf/Z849hL5DvEmR4+zZ0xjMVbRyk6QwD+kgL6iJDZh56FTqanaJGZt+MdCp iaVFZxus2dh+BGlOtcK4GLiHcwKBOBqDpMvcbmDxhdORn/2tEGFfUudRZ3XUWHe8 3ZX/qeMZ+zcrPNh8HwKXKUeQ+jlj94q9fpe6kEBVR7qWHtDrREZdCWONoIv8dyVP Gw8MibcEoMDWOsEqIf0t0JrKNJdJwBNln7CwXCnpeoLfbtI3ovdxnAtzwsUDhfuv HqQik+m9bIgEDhvZL5ORm6SKsYC4YHYKI6mNDgxNKsVFoPP7zJIEVYA0+2zsHI0w IR50e/+h50xP1W6jkmkDA7S6bCBQAQ== =NKop -----END PGP SIGNATURE----- --FwJPrEqu2igwCvTs--