All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Thomas Zimmermann" <tzimmermann@suse.de>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 2/7] drm/kms-helper: Remove struct drm_simple_display_pipe and helpers
Date: Fri, 02 Oct 2026 12:55:57 +0000	[thread overview]
Message-ID: <20261002125557.D45D71F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20261002124456.741011-3-tzimmermann@suse.de>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] build: imx-lcdc broken due to removed drm_simple_display_pipe
--

commit 34fb6e586b77e29b94177632c0a641cf060ef4ce
Author: Thomas Zimmermann <tzimmermann@suse.de>

drm/kms-helper: Remove struct drm_simple_display_pipe and helpers

This commit removes struct drm_simple_display_pipe and its related helpers,
stating that they are no longer used by any drivers. It also updates the
TODO list to reflect this cleanup.

> There are no drivers using struct drm_simple_display_pipe. Remove
> the data type and all related helpers.

[Severity: Low]
Is this statement fully accurate? It appears the imx-lcdc driver still
relies on these structs and functions. Building with CONFIG_DRM_IMX_LCDC=y
currently fails due to incomplete types and implicit function declarations
caused by this removal.

For example, in drivers/gpu/drm/imx/lcdc/imx-lcdc.c, the struct is still
embedded:

	struct imx_lcdc {
		...
		struct drm_device *drm;
		struct drm_simple_display_pipe pipe;
		...

And initialized in imx_lcdc_probe():

	ret = drm_simple_display_pipe_init(drm, &lcdc->pipe,
					   &imx_lcdc_pipe_funcs,
					   imx_lcdc_formats,
					   ARRAY_SIZE(imx_lcdc_formats), NULL, NULL);

Does this driver need to be converted to regular atomic helpers before
removing the simple-pipe infrastructure?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261002124456.741011-1-tzimmermann@suse.de?part=2

  reply	other threads:[~2026-10-02 12:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-02 12:41 [PATCH v2 0/7] drm: Remove simple-display pipe Thomas Zimmermann
2026-10-02 12:41 ` [PATCH v2 1/7] drm/hyperv: Add missing include statements Thomas Zimmermann
2026-10-02 12:50   ` Javier Martinez Canillas
2026-10-02 12:41 ` [PATCH v2 2/7] drm/kms-helper: Remove struct drm_simple_display_pipe and helpers Thomas Zimmermann
2026-10-02 12:55   ` sashiko-bot [this message]
2026-10-02 12:41 ` [PATCH v2 3/7] drm/bridge: Do not include <drm/drm_simple_kms_helper.h> Thomas Zimmermann
2026-10-02 12:51   ` Javier Martinez Canillas
2026-10-02 12:41 ` [PATCH v2 4/7] drm/hisilicon/hibmc: " Thomas Zimmermann
2026-10-02 12:51   ` Javier Martinez Canillas
2026-10-02 12:41 ` [PATCH v2 5/7] drm/tegra: " Thomas Zimmermann
2026-10-02 12:51   ` Javier Martinez Canillas
2026-10-02 12:41 ` [PATCH v2 6/7] drm/verisilicon: " Thomas Zimmermann
2026-10-02 12:51   ` Javier Martinez Canillas
2026-10-02 12:41 ` [PATCH v2 7/7] drm/vc4: " Thomas Zimmermann
2026-10-02 12:52   ` Javier Martinez Canillas
2026-10-02 13:26 ` [PATCH v2 0/7] drm: Remove simple-display pipe Andy Shevchenko

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=20261002125557.D45D71F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.