linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Thomas Zimmermann <tzimmermann@suse.de>,
	daniel@ffwll.ch, airlied@gmail.com,
	maarten.lankhorst@linux.intel.com, mripard@kernel.org,
	javierm@redhat.com, linux-samsung-soc@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, intel-gfx@lists.freedesktop.org,
	dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org,
	linux-tegra@vger.kernel.org, freedreno@lists.freedesktop.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 02/12] drm/armada: Use regular fbdev I/O helpers
Date: Mon, 15 May 2023 19:04:48 +0100	[thread overview]
Message-ID: <ZGJ0QIQrF/a0Wkri@shell.armlinux.org.uk> (raw)
In-Reply-To: <20230515175544.GB1745913@ravnborg.org>

On Mon, May 15, 2023 at 07:55:44PM +0200, Sam Ravnborg wrote:
> Hi Thomas,
> 
> On Mon, May 15, 2023 at 11:40:23AM +0200, Thomas Zimmermann wrote:
> > Use the regular fbdev helpers for framebuffer I/O instead of DRM's
> > helpers. Armada does not use damage handling, so DRM's fbdev helpers
> > are mere wrappers around the fbdev code.
> > 
> > By using fbdev helpers directly within each DRM fbdev emulation,
> > we can eventually remove DRM's wrapper functions entirely.
> > 
> > v2:
> > 	* use FB_IO_HELPERS option
> > 
> > Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
> > Cc: Russell King <linux@armlinux.org.uk>
> > ---
> >  drivers/gpu/drm/armada/Kconfig        | 1 +
> >  drivers/gpu/drm/armada/armada_fbdev.c | 9 ++++-----
> >  2 files changed, 5 insertions(+), 5 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/armada/Kconfig b/drivers/gpu/drm/armada/Kconfig
> > index f5c66d89ba99..5afade25e217 100644
> > --- a/drivers/gpu/drm/armada/Kconfig
> > +++ b/drivers/gpu/drm/armada/Kconfig
> > @@ -3,6 +3,7 @@ config DRM_ARMADA
> >  	tristate "DRM support for Marvell Armada SoCs"
> >  	depends on DRM && HAVE_CLK && ARM && MMU
> >  	select DRM_KMS_HELPER
> > +	select FB_IO_HELPERS if DRM_FBDEV_EMULATION
> >  	help
> >  	  Support the "LCD" controllers found on the Marvell Armada 510
> >  	  devices.  There are two controllers on the device, each controller
> > diff --git a/drivers/gpu/drm/armada/armada_fbdev.c b/drivers/gpu/drm/armada/armada_fbdev.c
> > index 0a5fd1aa86eb..6c3bbaf53569 100644
> > --- a/drivers/gpu/drm/armada/armada_fbdev.c
> > +++ b/drivers/gpu/drm/armada/armada_fbdev.c
> > @@ -5,6 +5,7 @@
> >   */
> >  
> >  #include <linux/errno.h>
> > +#include <linux/fb.h>
> >  #include <linux/kernel.h>
> >  #include <linux/module.h>
> >  
> > @@ -34,11 +35,9 @@ static void armada_fbdev_fb_destroy(struct fb_info *info)
> >  static const struct fb_ops armada_fb_ops = {
> >  	.owner		= THIS_MODULE,
> >  	DRM_FB_HELPER_DEFAULT_OPS,
> > -	.fb_read	= drm_fb_helper_cfb_read,
> > -	.fb_write	= drm_fb_helper_cfb_write,
> I had expected to see
> .fb_read = fb_io_read,
> 
> But maybe this only used when using damage handling?
> 
> Likewise for drm_fb_helper_cfb_write.
> 
> ??
> 
> > -	.fb_fillrect	= drm_fb_helper_cfb_fillrect,
> > -	.fb_copyarea	= drm_fb_helper_cfb_copyarea,
> > -	.fb_imageblit	= drm_fb_helper_cfb_imageblit,
> > +	.fb_fillrect	= cfb_fillrect,
> > +	.fb_copyarea	= cfb_copyarea,
> > +	.fb_imageblit	= cfb_imageblit,
> 
> This part is as expected.

Well, to me it looks like this has gone through an entire circular set
of revisions:

commit e8b70e4dd7b5dad7c2379de6e0851587bf86bfd6
Author: Archit Taneja <architt@codeaurora.org>
Date:   Wed Jul 22 14:58:04 2015 +0530

    drm/armada: Use new drm_fb_helper functions

-       .fb_fillrect    = cfb_fillrect,
-       .fb_copyarea    = cfb_copyarea,
-       .fb_imageblit   = cfb_imageblit,
+       .fb_fillrect    = drm_fb_helper_cfb_fillrect,
+       .fb_copyarea    = drm_fb_helper_cfb_copyarea,
+       .fb_imageblit   = drm_fb_helper_cfb_imageblit,

commit 983780918c759fdbbf0bf033e701bbff75d2af23
Author: Thomas Zimmermann <tzimmermann@suse.de>
Date:   Thu Nov 3 16:14:40 2022 +0100

    drm/fb-helper: Perform all fbdev I/O with the same implementation

+       .fb_read        = drm_fb_helper_cfb_read,
+       .fb_write       = drm_fb_helper_cfb_write,

and now effectively those two changes are being reverted, so we'd
now be back to the pre-July 2015 state of affairs. As I believe
the fbdev layer has been stable, this change merely reverts the
driver back to what it once was.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2023-05-15 18:05 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-15  9:40 [PATCH v2 00/12] drm/fbdev: Remove DRM's helpers for fbdev I/O Thomas Zimmermann
2023-05-15  9:40 ` [PATCH v2 01/12] fbdev: Add Kconfig options to select different fb_ops helpers Thomas Zimmermann
2023-05-15  9:40 ` [PATCH v2 02/12] drm/armada: Use regular fbdev I/O helpers Thomas Zimmermann
2023-05-15 17:55   ` Sam Ravnborg
2023-05-15 18:04     ` Russell King (Oracle) [this message]
2023-05-16 13:13       ` Thomas Zimmermann
2023-05-16 13:03     ` Thomas Zimmermann
2023-05-15  9:40 ` [PATCH v2 03/12] drm/exynos: " Thomas Zimmermann
2023-05-15 17:43   ` Sam Ravnborg
2023-05-16 13:14     ` Thomas Zimmermann
2023-05-15  9:40 ` [PATCH v2 04/12] drm/gma500: " Thomas Zimmermann
2023-05-15  9:40 ` [PATCH v2 05/12] drm/radeon: " Thomas Zimmermann
2023-05-15  9:40 ` [PATCH v2 06/12] drm/fbdev-dma: " Thomas Zimmermann
2023-05-15  9:40 ` [PATCH v2 07/12] drm/msm: " Thomas Zimmermann
2023-05-15  9:40 ` [PATCH v2 08/12] drm/omapdrm: " Thomas Zimmermann
2023-05-15  9:40 ` [PATCH v2 09/12] drm/tegra: " Thomas Zimmermann
2023-05-15  9:40 ` [PATCH v2 10/12] drm/fb-helper: Export helpers for marking damage areas Thomas Zimmermann
2023-05-15  9:40 ` [PATCH v2 11/12] drm/fbdev-generic: Implement dedicated fbdev I/O helpers Thomas Zimmermann
     [not found]   ` <80b4b615-0a71-89e8-3a58-fbeb8a9a06e8@189.cn>
2023-05-17  7:07     ` [v2,11/12] " Thomas Zimmermann
     [not found]       ` <f1688b87-0b8d-59b0-2fe8-88b2d40c513e@189.cn>
2023-05-18 13:30         ` Thomas Zimmermann
2023-05-15  9:40 ` [PATCH v2 12/12] drm/i915: " Thomas Zimmermann

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=ZGJ0QIQrF/a0Wkri@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=airlied@gmail.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=javierm@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=sam@ravnborg.org \
    --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;
as well as URLs for NNTP newsgroup(s).