From: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
To: dri-devel@lists.freedesktop.org
Cc: linux-renesas-soc@vger.kernel.org,
Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>,
Tommaso Merciai <tommaso.merciai.xr@bp.renesas.com>,
Biju Das <biju.das.jz@bp.renesas.com>
Subject: [PATCH v2 0/4] drm: rcar-du: Improve device_link handling
Date: Mon, 23 Mar 2026 18:45:22 +0200 [thread overview]
Message-ID: <20260323164526.2292491-1-laurent.pinchart+renesas@ideasonboard.com> (raw)
Hello,
This small patch series came out of the review of [1].
I noticed that the DU driver enforces suspend/resume ordering with the
CMMs but not with the VSPs, which patch 1/4 fixes. This in turn made me
notice that the driver leaks the device_link instances to the CMM.
Patches 2/4 and 3/4 refactor CMM handling a bit, to prepare for 4/4 that
fixes the leak.
Changes compared to v1 are minor, see individual patches for details.
[1] https://lore.kernel.org/r/02669d4630e04fe24c17dd2576ec8b27ded458f0.1765541401.git.tommaso.merciai.xr@bp.renesas.com
Laurent Pinchart (4):
drm: rcar-du: Ensure correct suspend/resume ordering with VSP
drm: rcar-du: Store CMM device pointer instead of platform_device
drm: rcar-du: Use __free() to simplify device_node handling
drm: rcar-du: Don't leak device_link to CMM
drivers/gpu/drm/renesas/rcar-du/rcar_cmm.c | 26 +++++-----
drivers/gpu/drm/renesas/rcar-du/rcar_cmm.h | 18 +++----
.../gpu/drm/renesas/rcar-du/rcar_du_crtc.c | 16 +++---
.../gpu/drm/renesas/rcar-du/rcar_du_crtc.h | 3 +-
drivers/gpu/drm/renesas/rcar-du/rcar_du_drv.h | 8 ++-
drivers/gpu/drm/renesas/rcar-du/rcar_du_kms.c | 52 +++++++++----------
drivers/gpu/drm/renesas/rcar-du/rcar_du_vsp.c | 16 ++++++
drivers/gpu/drm/renesas/rcar-du/rcar_du_vsp.h | 2 +
8 files changed, 81 insertions(+), 60 deletions(-)
base-commit: 25854131c04a5aa25a41cf527aab269aadb86699
--
Regards,
Laurent Pinchart
next reply other threads:[~2026-03-23 16:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 16:45 Laurent Pinchart [this message]
2026-03-23 16:45 ` [PATCH v2 1/4] drm: rcar-du: Ensure correct suspend/resume ordering with VSP Laurent Pinchart
2026-03-24 21:42 ` Claude review: " Claude Code Review Bot
2026-03-23 16:45 ` [PATCH v2 2/4] drm: rcar-du: Store CMM device pointer instead of platform_device Laurent Pinchart
2026-03-24 21:42 ` Claude review: " Claude Code Review Bot
2026-03-23 16:45 ` [PATCH v2 3/4] drm: rcar-du: Use __free() to simplify device_node handling Laurent Pinchart
2026-03-24 21:42 ` Claude review: " Claude Code Review Bot
2026-03-23 16:45 ` [PATCH v2 4/4] drm: rcar-du: Don't leak device_link to CMM Laurent Pinchart
2026-03-24 21:42 ` Claude review: " Claude Code Review Bot
2026-03-24 21:42 ` Claude review: drm: rcar-du: Improve device_link handling 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=20260323164526.2292491-1-laurent.pinchart+renesas@ideasonboard.com \
--to=laurent.pinchart+renesas@ideasonboard.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=tommaso.merciai.xr@bp.renesas.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