From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Tommaso Merciai <tommaso.merciai.xr@bp.renesas.com>
Cc: tomm.merciai@gmail.com, geert@linux-m68k.org,
linux-renesas-soc@vger.kernel.org, biju.das.jz@bp.renesas.com,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm: rz-du: Ensure correct suspend/resume ordering with VSP
Date: Tue, 24 Mar 2026 21:33:11 +0200 [thread overview]
Message-ID: <20260324193311.GB2461076@killaraus.ideasonboard.com> (raw)
In-Reply-To: <20260324180512.2277875-1-tommaso.merciai.xr@bp.renesas.com>
On Tue, Mar 24, 2026 at 07:05:05PM +0100, Tommaso Merciai wrote:
> The VSP serves as an interface to memory and a compositor to the DU. It
> therefore needs to be suspended after and resumed before the DU, to be
> properly stopped and restarted in a controlled fashion driven by the DU
> driver. This currently works by chance. Avoid relying on luck by
> enforcing the correct suspend/resume ordering with device links.
>
> Based on similar work done by Laurent Pinchart for R-Car DU.
If the R-Car DU patch gets merged before this one, you could mention the
commit ID here.
>
> Signed-off-by: Tommaso Merciai <tommaso.merciai.xr@bp.renesas.com>
Reviewed-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
> ---
> drivers/gpu/drm/renesas/rz-du/rzg2l_du_vsp.c | 16 ++++++++++++++++
> drivers/gpu/drm/renesas/rz-du/rzg2l_du_vsp.h | 2 ++
> 2 files changed, 18 insertions(+)
>
> diff --git a/drivers/gpu/drm/renesas/rz-du/rzg2l_du_vsp.c b/drivers/gpu/drm/renesas/rz-du/rzg2l_du_vsp.c
> index bd486377f037..eb626c3cc421 100644
> --- a/drivers/gpu/drm/renesas/rz-du/rzg2l_du_vsp.c
> +++ b/drivers/gpu/drm/renesas/rz-du/rzg2l_du_vsp.c
> @@ -20,6 +20,7 @@
> #include <drm/drm_vblank.h>
>
> #include <linux/bitops.h>
> +#include <linux/device.h>
> #include <linux/dma-mapping.h>
> #include <linux/of_platform.h>
> #include <linux/platform_device.h>
> @@ -293,6 +294,9 @@ static void rzg2l_du_vsp_cleanup(struct drm_device *dev, void *res)
> {
> struct rzg2l_du_vsp *vsp = res;
>
> + if (vsp->link)
> + device_link_del(vsp->link);
> +
> put_device(vsp->vsp);
> }
>
> @@ -317,6 +321,18 @@ int rzg2l_du_vsp_init(struct rzg2l_du_vsp *vsp, struct device_node *np,
> if (ret < 0)
> return ret;
>
> + /*
> + * Enforce suspend/resume ordering between the DU (consumer) and the
> + * VSP (supplier). The DU will be suspended before and resume after the
> + * VSP.
> + */
> + vsp->link = device_link_add(rcdu->dev, vsp->vsp, DL_FLAG_STATELESS);
> + if (!vsp->link) {
> + dev_err(rcdu->dev, "Failed to create device link to VSP %s\n",
> + dev_name(vsp->vsp));
> + return -EINVAL;
> + }
> +
> ret = vsp1_du_init(vsp->vsp);
> if (ret < 0)
> return ret;
> diff --git a/drivers/gpu/drm/renesas/rz-du/rzg2l_du_vsp.h b/drivers/gpu/drm/renesas/rz-du/rzg2l_du_vsp.h
> index 322eb80dcbaf..a22aaf0843ed 100644
> --- a/drivers/gpu/drm/renesas/rz-du/rzg2l_du_vsp.h
> +++ b/drivers/gpu/drm/renesas/rz-du/rzg2l_du_vsp.h
> @@ -15,6 +15,7 @@
> #include <linux/scatterlist.h>
>
> struct device;
> +struct device_link;
> struct drm_framebuffer;
> struct rzg2l_du_device;
> struct rzg2l_du_format_info;
> @@ -29,6 +30,7 @@ struct rzg2l_du_vsp_plane {
> struct rzg2l_du_vsp {
> unsigned int index;
> struct device *vsp;
> + struct device_link *link;
> struct rzg2l_du_device *dev;
> };
>
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2026-03-24 19:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 18:05 [PATCH] drm: rz-du: Ensure correct suspend/resume ordering with VSP Tommaso Merciai
2026-03-24 19:33 ` Laurent Pinchart [this message]
2026-03-24 20:34 ` Claude review: " Claude Code Review Bot
2026-03-24 20:34 ` Claude Code Review Bot
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=20260324193311.GB2461076@killaraus.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=tomm.merciai@gmail.com \
--cc=tommaso.merciai.xr@bp.renesas.com \
--cc=tzimmermann@suse.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