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 2/2] drm/kms-helper: Remove struct drm_simple_display_pipe and helpers
Date: Thu, 01 Oct 2026 13:47:14 +0000	[thread overview]
Message-ID: <20261001134714.67EF61F00898@smtp.kernel.org> (raw)
In-Reply-To: <20261001133736.802604-3-tzimmermann@suse.de>

Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Low] drm/kms-helper: build breakage in imx-lcdc due to removed drm_simple_display_pipe
- [Low] doc: spelling mistake introduced in fbtft/TODO
--

commit d4d7a38057f45dc5b1cce9536154c93423caeae1
Author: Thomas Zimmermann <tzimmermann@suse.de>
Subject: drm/kms-helper: Remove struct drm_simple_display_pipe and helpers

This commit removes the struct drm_simple_display_pipe data type and its
associated helper functions from the DRM subsystem. It cleans up the
remaining TODO items related to simple-pipe, under the premise that all
drivers have been updated to use regular atomic helpers.

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

[Severity: Low]
Is this description accurate?

The imx-lcdc driver appears to still use struct drm_simple_display_pipe and
its helper functions. Compiling with CONFIG_DRM_IMX_LCDC enabled will result
in a build failure because the driver still relies on this structure in its
device setup:

drivers/gpu/drm/imx/lcdc/imx-lcdc.c:imx_lcdc() {
	...
	struct drm_simple_display_pipe pipe;
	...
}

As well as during initialization:

drivers/gpu/drm/imx/lcdc/imx-lcdc.c: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);
	...
}

> diff --git a/drivers/staging/fbtft/TODO b/drivers/staging/fbtft/TODO
> index e72a08bf221cf..72df3ea3a52ce 100644
> --- a/drivers/staging/fbtft/TODO
> +++ b/drivers/staging/fbtft/TODO
> @@ -1,3 +1,3 @@
> -* convert all these over to drm_simple_display_pipe and submit for inclusion
> -  into the DRM subsystem under drivers/gpu/drm - fbdev doesn't take any new
> -  drivers anymore.
> +* convert all these over to DRM and submit thme for inclusion into
                                              ^^^^

[Severity: Low]
This isn't a bug, but there is a typo here (thme instead of them).

> +  the DRM subsystem under drivers/gpu/drm - fbdev doesn't take any
> +  new drivers anymore.

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

  reply	other threads:[~2026-10-01 13:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-01 13:35 [PATCH 0/2] drm: Remove simple-display pipe Thomas Zimmermann
2026-10-01 13:35 ` [PATCH 1/2] drm/hyperv: Add missing include statements Thomas Zimmermann
2026-10-01 13:35 ` [PATCH 2/2] drm/kms-helper: Remove struct drm_simple_display_pipe and helpers Thomas Zimmermann
2026-10-01 13:47   ` sashiko-bot [this message]
2026-10-01 13:58     ` Thomas Zimmermann
2026-10-01 14:02   ` Andy Shevchenko
2026-10-01 14:38   ` Javier Martinez Canillas
2026-10-01 14:46   ` Javier Martinez Canillas
2026-10-01 15:57     ` Thomas Zimmermann
2026-10-01 14:03 ` [PATCH 0/2] 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=20261001134714.67EF61F00898@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.