From: Thomas Zimmermann <tzimmermann@suse.de>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: 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,
Russell King <linux@armlinux.org.uk>,
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: Tue, 16 May 2023 15:03:52 +0200 [thread overview]
Message-ID: <72d1535b-45ee-1556-d97f-6d3dfdcd7ed4@suse.de> (raw)
In-Reply-To: <20230515175544.GB1745913@ravnborg.org>
[-- Attachment #1.1: Type: text/plain, Size: 3076 bytes --]
Hi
Am 15.05.23 um 19:55 schrieb Sam Ravnborg:
> 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?
fb_io_read() and fb_io_write() are the default implementations. They are
called when no callback has been set. All the other fbdev drivers leave
them out, so I kept this pattern for the DRM side as well.
Best regards
Thomas
>
> 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.
>
> Sam
>
>> .fb_destroy = armada_fbdev_fb_destroy,
>> };
>>
>> --
>> 2.40.1
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstrasse 146, 90461 Nuernberg, Germany
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
HRB 36809 (AG Nuernberg)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2023-05-16 13:05 UTC|newest]
Thread overview: 23+ 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)
2023-05-16 13:13 ` Thomas Zimmermann
2023-05-16 13:03 ` Thomas Zimmermann [this message]
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
2023-05-17 1:58 ` [v2,11/12] " Sui Jingfeng
2023-05-17 7:07 ` Thomas Zimmermann
2023-05-18 12:46 ` Sui Jingfeng
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=72d1535b-45ee-1556-d97f-6d3dfdcd7ed4@suse.de \
--to=tzimmermann@suse.de \
--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=linux@armlinux.org.uk \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=sam@ravnborg.org \
/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