From: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
To: Abhash Kumar Jha <a-kumar2@ti.com>
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Laurent.pinchart@ideasonboard.com, jonas@kwiboo.se,
jernej.skrabec@gmail.com, s-jain1@ti.com, p-mantena@ti.com,
aradhya.bhatia@linux.dev, p.zabel@pengutronix.de,
andrzej.hajda@intel.com, neil.armstrong@linaro.org,
rfoss@kernel.org, mripard@kernel.org, tzimmermann@suse.de,
airlied@gmail.com, simona@ffwll.ch, devarsht@ti.com,
u-kumar1@ti.com
Subject: Re: [PATCH v2] drm/bridge: cdns-dsi: Split pm_ops into runtime_pm and system_sleep ops
Date: Fri, 16 Jan 2026 13:57:08 +0200 [thread overview]
Message-ID: <e319d432-8687-462d-9bce-660de01c6696@ideasonboard.com> (raw)
In-Reply-To: <20260112091210.3505622-1-a-kumar2@ti.com>
Hi,
On 12/01/2026 11:12, Abhash Kumar Jha wrote:
> If runtime-pm has already suspended the device and a system suspend
> occurs, then we see a kernel crash when disabling and unpreparing the
> clocks.
>
> Use pm_runtime_force_suspend/resume in system_sleep pm callbacks to let
> runtime-pm take care of the coordination between system suspend and
> itself. This ensures that they do not interfere with each other.
>
> Signed-off-by: Abhash Kumar Jha <a-kumar2@ti.com>
> ---
> Hi,
>
> If a device is runtime_pm suspended and a system wide suspend is triggered,
> we see a kernel crash. Hence split the power management ops into separate
> system_sleep and runtime_pm ops.
>
> Changes in v2:
> - Improve the commit description and subject.
> - Link to v1: https://lore.kernel.org/all/20260109060312.2853133-1-a-kumar2@ti.com/
See:
https://lore.kernel.org/all/20250512083215.436149-1-ivitro%40gmail.com/
I think that's a better fix.
Tomi
>
> Thanks,
> Abhash
>
> .../gpu/drm/bridge/cadence/cdns-dsi-core.c | 32 +++++++++++++------
> 1 file changed, 23 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/gpu/drm/bridge/cadence/cdns-dsi-core.c b/drivers/gpu/drm/bridge/cadence/cdns-dsi-core.c
> index 09b289f0fcbf..25eaf0192013 100644
> --- a/drivers/gpu/drm/bridge/cadence/cdns-dsi-core.c
> +++ b/drivers/gpu/drm/bridge/cadence/cdns-dsi-core.c
> @@ -1230,7 +1230,18 @@ static const struct mipi_dsi_host_ops cdns_dsi_ops = {
> .transfer = cdns_dsi_transfer,
> };
>
> -static int __maybe_unused cdns_dsi_resume(struct device *dev)
> +static int cdns_dsi_runtime_suspend(struct device *dev)
> +{
> + struct cdns_dsi *dsi = dev_get_drvdata(dev);
> +
> + clk_disable_unprepare(dsi->dsi_sys_clk);
> + clk_disable_unprepare(dsi->dsi_p_clk);
> + reset_control_assert(dsi->dsi_p_rst);
> +
> + return 0;
> +}
> +
> +static int cdns_dsi_runtime_resume(struct device *dev)
> {
> struct cdns_dsi *dsi = dev_get_drvdata(dev);
>
> @@ -1241,18 +1252,21 @@ static int __maybe_unused cdns_dsi_resume(struct device *dev)
> return 0;
> }
>
> -static int __maybe_unused cdns_dsi_suspend(struct device *dev)
> +static int cdns_dsi_suspend(struct device *dev)
> {
> - struct cdns_dsi *dsi = dev_get_drvdata(dev);
> + return pm_runtime_force_suspend(dev);
> +}
>
> - clk_disable_unprepare(dsi->dsi_sys_clk);
> - clk_disable_unprepare(dsi->dsi_p_clk);
> - reset_control_assert(dsi->dsi_p_rst);
> - return 0;
> +static int cdns_dsi_resume(struct device *dev)
> +{
> + return pm_runtime_force_resume(dev);
> }
>
> -static UNIVERSAL_DEV_PM_OPS(cdns_dsi_pm_ops, cdns_dsi_suspend, cdns_dsi_resume,
> - NULL);
> +static const struct dev_pm_ops cdns_dsi_pm_ops = {
> + SET_RUNTIME_PM_OPS(cdns_dsi_runtime_suspend,
> + cdns_dsi_runtime_resume, NULL)
> + SET_SYSTEM_SLEEP_PM_OPS(cdns_dsi_suspend, cdns_dsi_resume)
> +};
>
> static int cdns_dsi_drm_probe(struct platform_device *pdev)
> {
prev parent reply other threads:[~2026-01-16 11:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 9:12 Abhash Kumar Jha
2026-01-13 9:53 ` Kumar, Udit
2026-01-16 11:57 ` Tomi Valkeinen [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=e319d432-8687-462d-9bce-660de01c6696@ideasonboard.com \
--to=tomi.valkeinen@ideasonboard.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=a-kumar2@ti.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=aradhya.bhatia@linux.dev \
--cc=devarsht@ti.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=p-mantena@ti.com \
--cc=p.zabel@pengutronix.de \
--cc=rfoss@kernel.org \
--cc=s-jain1@ti.com \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=u-kumar1@ti.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
all inboxes | Powered by JetHome®