linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Kepplinger <martin.kepplinger@puri.sm>
To: matti.vaittinen@fi.rohmeurope.com, lgirdwood@gmail.com,
	broonie@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
	arm-soc <linux-arm-kernel@lists.infradead.org>,
	Pengutronix Kernel Team <kernel@pengutronix.de>
Subject: regulator: BD71837 PMIC resume during noirq phase?
Date: Tue, 14 Jun 2022 11:06:06 +0200	[thread overview]
Message-ID: <573166b75e524517782471c2b7f96e03fd93d175.camel@puri.sm> (raw)

hi Matti,

I heard you've been helpful in the past - thank for that! Here's a
question I'm currently stuck at: In short, imx8mq can't yet resume from
suspend when using the bd71839 pmic via i2c. The original report here,
just for the background:

https://lore.kernel.org/linux-arm-kernel/2d5d3bbec443742506e39488dbfbf724bb4ca93f.camel@puri.sm/T/#u

But here's what I *think* is going on: When the (buck3) regulator from
bd71839 is the power-supply for a power domain (gpu), the power domain
driver can't resume because buck3 can't be enabled when the pmic isn't
running yet. I'm still a bit uncertain, but here's the logs when simply
printing in the respective suspend/resume callbacks:

[  452.199600] bd718xx-pmic bd71837-pmic.2.auto: bd718xx_resume_noirq
[  452.301450] imx-pgc imx-pgc-domain.5: failed to enable regulator: -
ETIMEDOUT
[  452.320593] imx-i2c 30a20000.i2c: i2c_imx_resume
[  452.322152] bd718xx-pmic bd71837-pmic.2.auto: bd718xx_resume
[  452.323853] imx-i2c 30a30000.i2c: i2c_imx_resume
[  452.324778] imx-i2c 30a40000.i2c: i2c_imx_resume
[  452.325017] imx-i2c 30a50000.i2c: i2c_imx_resume

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?

thank you very much,

                            martin



             reply	other threads:[~2022-06-14  9:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-14  9:06 Martin Kepplinger [this message]
2022-06-14  9:18 ` regulator: BD71837 PMIC resume during noirq phase? Mark Brown
2022-06-14  9:47   ` Vaittinen, Matti
2022-06-14  9:57   ` Martin Kepplinger
2022-06-14 10:16     ` Mark Brown
2022-07-11  9:52       ` Martin Kepplinger
2022-06-14  9:38 ` Vaittinen, Matti

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=573166b75e524517782471c2b7f96e03fd93d175.camel@puri.sm \
    --to=martin.kepplinger@puri.sm \
    --cc=broonie@kernel.org \
    --cc=kernel@pengutronix.de \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=matti.vaittinen@fi.rohmeurope.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).