From: Shawn Guo <shawnguo@kernel.org>
To: Alexander Stein <alexander.stein@ew.tq-group.com>
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>, Peng Fan <peng.fan@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
NXP Linux Team <linux-imx@nxp.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/1] soc: imx: imx93-blk-ctrl: Add dedicated lockdep class for nested genpd locks
Date: Tue, 18 Jul 2023 15:00:07 +0800 [thread overview]
Message-ID: <20230718070007.GO9559@dragon> (raw)
In-Reply-To: <20230706074629.3527654-1-alexander.stein@ew.tq-group.com>
On Thu, Jul 06, 2023 at 09:46:29AM +0200, Alexander Stein wrote:
> This is the same approach as being used within imx8mp-blk-ctrl. This fixes
> the lockdep warning about 'possible recursive locking detected' with the
> following (reduced) backtrace:
> genpd_lock_mtx+0x14/0x1c
> genpd_runtime_resume+0x108/0x308
> __rpm_callback+0x44/0x19c
> rpm_callback+0x64/0x70
> rpm_resume+0x438/0x6d8
> __pm_runtime_resume+0x54/0xb0
> imx93_blk_ctrl_power_on+0x100/0x294
> _genpd_power_on+0x8c/0x16c
> genpd_power_on.part.0+0xa0/0x1a0
> __genpd_dev_pm_attach+0x14c/0x2e4
> genpd_dev_pm_attach+0x58/0x64
> dev_pm_domain_attach+0x1c/0x2c
>
> Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.com>
Applied, thanks!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-07-19 6:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 7:46 [PATCH 1/1] soc: imx: imx93-blk-ctrl: Add dedicated lockdep class for nested genpd locks Alexander Stein
2023-07-18 7:00 ` Shawn Guo [this message]
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=20230718070007.GO9559@dragon \
--to=shawnguo@kernel.org \
--cc=alexander.stein@ew.tq-group.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=peng.fan@nxp.com \
--cc=s.hauer@pengutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.