From: Francesco Dolcini <francesco@dolcini.it>
To: Vitor Soares <ivitro@gmail.com>, Adam Ford <aford173@gmail.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Vitor Soares <vitor.soares@toradex.com>,
linux-pm@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Lucas Stach <l.stach@pengutronix.de>
Subject: Re: [PATCH v1] pmdomain: imx8m-blk-ctrl: fix suspend/resume order
Date: Wed, 8 May 2024 19:40:48 +0200 [thread overview]
Message-ID: <20240508174048.GA5257@francesco-nb> (raw)
In-Reply-To: <20240418155151.355133-1-ivitro@gmail.com>
On Thu, Apr 18, 2024 at 04:51:51PM +0100, Vitor Soares wrote:
> From: Vitor Soares <vitor.soares@toradex.com>
>
> During the probe, the genpd power_dev is added to the dpm_list after
> blk_ctrl due to its parent/child relationship. Making the blk_ctrl
> suspend after and resume before the genpd power_dev.
>
> As a consequence, the system hangs when resuming the VPU due to the
> power domain dependency.
>
> To ensure the proper suspend/resume order, add a device link betweem
> blk_ctrl and genpd power_dev. It guarantees genpd power_dev is suspended
> after and resumed before blk-ctrl.
>
Cc: Adam Ford
Francesco
next prev parent reply other threads:[~2024-05-08 17:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 15:51 [PATCH v1] pmdomain: imx8m-blk-ctrl: fix suspend/resume order Vitor Soares
2024-04-18 16:24 ` [PATCH] " Markus Elfring
2024-04-18 16:50 ` Vitor Soares
2024-05-08 17:40 ` Francesco Dolcini [this message]
2024-05-08 17:43 ` [PATCH v1] " Adam Ford
2024-05-08 17:46 ` Lucas Stach
2024-05-10 9:34 ` Ulf Hansson
2024-06-25 7:32 ` Vitor Soares
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=20240508174048.GA5257@francesco-nb \
--to=francesco@dolcini.it \
--cc=aford173@gmail.com \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=ivitro@gmail.com \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=stable@vger.kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=vitor.soares@toradex.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