From: Shawn Guo <shawnguo@kernel.org>
To: Lucas Stach <l.stach@pengutronix.de>
Cc: Yannic Moog <Y.Moog@phytec.de>,
Fabio Estevam <festevam@gmail.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
NXP Linux Team <linux-imx@nxp.com>,
linux-arm-kernel@lists.infradead.org,
patchwork-lst@pengutronix.de
Subject: Re: [PATCH] soc: imx: imx8mp-blk-ctrl: register HSIO PLL clock as bus_power_dev child
Date: Wed, 19 Jul 2023 15:45:03 +0800 [thread overview]
Message-ID: <20230719074503.GL151430@dragon> (raw)
In-Reply-To: <20230717145409.2804424-1-l.stach@pengutronix.de>
On Mon, Jul 17, 2023 at 04:54:09PM +0200, Lucas Stach wrote:
> The blk-ctrl device is deliberately placed outside of the GPC power
> domain as it needs to control the power sequencing of the blk-ctrl
> domains together with the GPC domains.
>
> Clock runtime PM works by operating on the clock parent device, which
> doesn't translate into the neccessary GPC power domain action if the
> clk parent is not part of the GPC power domain. Use the bus_power_device
> as the parent for the clock to trigger the proper GPC domain actions on
> clock runtime power management.
>
> Fixes: 2cbee26e5d59 ("soc: imx: imx8mp-blk-ctrl: expose high performance PLL clock")
> Reported-by: Yannic Moog <Y.Moog@phytec.de>
> Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
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 7:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 14:54 [PATCH] soc: imx: imx8mp-blk-ctrl: register HSIO PLL clock as bus_power_dev child Lucas Stach
2023-07-18 6:23 ` Yannic Moog
2023-07-19 7:45 ` 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=20230719074503.GL151430@dragon \
--to=shawnguo@kernel.org \
--cc=Y.Moog@phytec.de \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=patchwork-lst@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 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).