From: Frank Li <Frank.li@nxp.com>
To: Laurentiu Palcu <laurentiu.palcu@oss.nxp.com>
Cc: imx@lists.linux.dev, Abel Vesa <abelvesa@kernel.org>,
Peng Fan <peng.fan@nxp.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
dri-devel@lists.freedesktop.org, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 02/10] clk: imx95-blk-ctl: Save/restore registers when RPM routines are called
Date: Thu, 17 Jul 2025 11:38:15 -0400 [thread overview]
Message-ID: <aHkY51MOgl4v2Y9/@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <lp3m4bahzbwvb6nfu2o6hsr5cux3y4rgdasbgba2jc774iei5a@plfpzihh7pen>
On Thu, Jul 17, 2025 at 03:23:38PM +0300, Laurentiu Palcu wrote:
> Hi Frank,
>
> On Wed, Jul 16, 2025 at 02:29:01PM -0400, Frank Li wrote:
> > On Wed, Jul 16, 2025 at 11:15:06AM +0300, Laurentiu Palcu wrote:
> > > If runtime PM is used for the clock providers and they're part of a
> > > power domain, then the power domain supply will be cut off when runtime
> > > suspended. That means all BLK CTL registers belonging to that power
> > > domain will be reset. Save the registers, then, before entering suspend
> > > and restore them in resume.
> > >
> > > Also, fix the suspend/resume routines and make sure we disable/enable
> > > the clock correctly.
> > >
> > > Signed-off-by: Laurentiu Palcu <laurentiu.palcu@oss.nxp.com>
> > > ---
> > > drivers/clk/imx/clk-imx95-blk-ctl.c | 25 +++++++++++++------------
> > > 1 file changed, 13 insertions(+), 12 deletions(-)
> > >
> > > diff --git a/drivers/clk/imx/clk-imx95-blk-ctl.c b/drivers/clk/imx/clk-imx95-blk-ctl.c
> > > index c72debaf3a60b..3f6bcc33bbe99 100644
> > > --- a/drivers/clk/imx/clk-imx95-blk-ctl.c
> > > +++ b/drivers/clk/imx/clk-imx95-blk-ctl.c
> > > @@ -453,7 +453,9 @@ static int imx95_bc_runtime_suspend(struct device *dev)
> > > {
> > > struct imx95_blk_ctl *bc = dev_get_drvdata(dev);
> > >
> > > + bc->clk_reg_restore = readl(bc->base + bc->pdata->clk_reg_offset);
> > > clk_disable_unprepare(bc->clk_apb);
> > > +
> > > return 0;
> > > }
> > >
> > > @@ -461,7 +463,10 @@ static int imx95_bc_runtime_resume(struct device *dev)
> > > {
> > > struct imx95_blk_ctl *bc = dev_get_drvdata(dev);
> > >
> > > - return clk_prepare_enable(bc->clk_apb);
> > > + clk_prepare_enable(bc->clk_apb);
> >
> > Need check clk_prepare_enable()'s return value!
> >
> > > + writel(bc->clk_reg_restore, bc->base + bc->pdata->clk_reg_offset);
> > > +
> > > + return 0;
> > > }
> > > #endif
> > >
> > > @@ -469,17 +474,12 @@ static int imx95_bc_runtime_resume(struct device *dev)
> > > static int imx95_bc_suspend(struct device *dev)
> > > {
> > > struct imx95_blk_ctl *bc = dev_get_drvdata(dev);
> > > - int ret;
> > >
> > > - if (bc->pdata->rpm_enabled) {
> > > - ret = pm_runtime_get_sync(bc->dev);
> > > - if (ret < 0) {
> > > - pm_runtime_put_noidle(bc->dev);
> > > - return ret;
> > > - }
> > > - }
> > > + if (pm_runtime_suspended(dev))
> > > + return 0;
> > >
> > > bc->clk_reg_restore = readl(bc->base + bc->pdata->clk_reg_offset);
> > > + clk_disable_unprepare(bc->clk_apb);
> > >
> > > return 0;
> > > }
> > > @@ -488,10 +488,11 @@ static int imx95_bc_resume(struct device *dev)
> > > {
> > > struct imx95_blk_ctl *bc = dev_get_drvdata(dev);
> > >
> > > - writel(bc->clk_reg_restore, bc->base + bc->pdata->clk_reg_offset);
> > > + if (pm_runtime_suspended(dev))
> > > + return 0;
> > >
> > > - if (bc->pdata->rpm_enabled)
> > > - pm_runtime_put(bc->dev);
> > > + clk_prepare_enable(bc->clk_apb);
> > > + writel(bc->clk_reg_restore, bc->base + bc->pdata->clk_reg_offset);
> > >
> > > return 0;
> > > }
> >
> > Look like needn't imx95_bc_resume() and imx95_bc_suspend()
> >
> > DEFINE_RUNTIME_DEV_PM_OPS() will use pm_runtime_force_suspend(), which
> > do similar things with above logic.
>
> As I said for v1, we cannot use DEFINE_RUNTIME_DEV_PM_OPS(). This driver
> is used for various clock providers and RPM can be disabled for some of
> them (see rpm_enabled flag in platform data). When RPM is disabled and
> DEFINE_RUNTIME_DEV_PM_OPS() is used, pm_runtime_force_suspend() is
> called, as you pointed out, and suspend() is never called.
Sorry, I missed your message at v1. do you know which flag impact this?
Frank
>
> Thanks,
> Laurentiu
>
> >
> > Frank
> >
> >
> > > --
> > > 2.34.1
> > >
next prev parent reply other threads:[~2025-07-17 16:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 8:15 [PATCH v2 00/10] Add support for i.MX94 DCIF Laurentiu Palcu
2025-07-16 8:15 ` [PATCH v2 01/10] clk: imx95-blk-ctl: Save platform data in imx95_blk_ctl structure Laurentiu Palcu
2025-07-16 12:04 ` Abel Vesa
2025-07-16 17:03 ` Frank Li
2025-07-16 8:15 ` [PATCH v2 02/10] clk: imx95-blk-ctl: Save/restore registers when RPM routines are called Laurentiu Palcu
2025-07-16 12:05 ` Abel Vesa
2025-07-16 18:29 ` Frank Li
2025-07-17 12:23 ` Laurentiu Palcu
2025-07-17 15:38 ` Frank Li [this message]
2025-07-16 8:15 ` [PATCH v2 06/10] dt-bindings: display: imx: Add bindings for i.MX94 DCIF Laurentiu Palcu
2025-07-16 18:40 ` Frank Li
2025-07-16 19:40 ` Krzysztof Kozlowski
2025-07-16 8:15 ` [PATCH v2 07/10] drm/imx: Add support " Laurentiu Palcu
2025-07-16 18:58 ` Frank Li
2025-07-17 12:36 ` Laurentiu Palcu
2025-07-16 8:15 ` [PATCH v2 08/10] arm64: dts: imx943: Add display pipeline nodes Laurentiu Palcu
2025-07-16 19:02 ` Frank Li
2025-07-16 8:15 ` [PATCH v2 09/10] arm64: dts: imx943-evk: Add display support using IT6263 Laurentiu Palcu
2025-07-16 19:10 ` Frank Li
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=aHkY51MOgl4v2Y9/@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=abelvesa@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=laurentiu.palcu@oss.nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=peng.fan@nxp.com \
--cc=s.hauer@pengutronix.de \
--cc=sboyd@kernel.org \
--cc=shawnguo@kernel.org \
/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