From: John Keeping <john@metanate.com>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: dri-devel@lists.freedesktop.org,
"Sandy Huang" <hjc@rock-chips.com>,
"Heiko Stübner" <heiko@sntech.de>,
"David Airlie" <airlied@linux.ie>,
"Daniel Vetter" <daniel@ffwll.ch>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org
Subject: Re: [PATCH] drm/rockchip: use generic fbdev setup
Date: Sat, 30 Oct 2021 13:05:31 +0100 [thread overview]
Message-ID: <YX01C6l93I2YPgku@donbot> (raw)
In-Reply-To: <ab7ace79-0148-1efa-ec17-6994bb35fd2f@suse.de>
Hi Thomas,
On Fri, Oct 29, 2021 at 09:00:08PM +0200, Thomas Zimmermann wrote:
> Am 29.10.21 um 13:50 schrieb John Keeping:
> > The Rockchip fbdev code does not add anything compared to
> > drm_fbdev_generic_setup(); the one custom function for .fb_mmap does the
> > same thing as gem_prime_mmap which is called by the helper.
> >
> > Signed-off-by: John Keeping <john@metanate.com>
> > ---
> > drivers/gpu/drm/rockchip/Makefile | 1 -
> > drivers/gpu/drm/rockchip/rockchip_drm_drv.c | 10 +-
> > drivers/gpu/drm/rockchip/rockchip_drm_drv.h | 2 -
> > drivers/gpu/drm/rockchip/rockchip_drm_fbdev.c | 164 ------------------
> > drivers/gpu/drm/rockchip/rockchip_drm_fbdev.h | 24 ---
> > 5 files changed, 2 insertions(+), 199 deletions(-)
> > delete mode 100644 drivers/gpu/drm/rockchip/rockchip_drm_fbdev.c
> > delete mode 100644 drivers/gpu/drm/rockchip/rockchip_drm_fbdev.h
> >
> > diff --git a/drivers/gpu/drm/rockchip/Makefile b/drivers/gpu/drm/rockchip/Makefile
> > index 17a9e7eb2130..1a56f696558c 100644
> > --- a/drivers/gpu/drm/rockchip/Makefile
> > +++ b/drivers/gpu/drm/rockchip/Makefile
> > @@ -5,7 +5,6 @@
> > rockchipdrm-y := rockchip_drm_drv.o rockchip_drm_fb.o \
> > rockchip_drm_gem.o rockchip_drm_vop.o rockchip_vop_reg.o
> > -rockchipdrm-$(CONFIG_DRM_FBDEV_EMULATION) += rockchip_drm_fbdev.o
> > rockchipdrm-$(CONFIG_ROCKCHIP_ANALOGIX_DP) += analogix_dp-rockchip.o
> > rockchipdrm-$(CONFIG_ROCKCHIP_CDN_DP) += cdn-dp-core.o cdn-dp-reg.o
> > diff --git a/drivers/gpu/drm/rockchip/rockchip_drm_drv.c b/drivers/gpu/drm/rockchip/rockchip_drm_drv.c
> > index 69c699459dce..20d81ae69828 100644
> > --- a/drivers/gpu/drm/rockchip/rockchip_drm_drv.c
> > +++ b/drivers/gpu/drm/rockchip/rockchip_drm_drv.c
> > @@ -26,7 +26,6 @@
> > #include "rockchip_drm_drv.h"
> > #include "rockchip_drm_fb.h"
> > -#include "rockchip_drm_fbdev.h"
> > #include "rockchip_drm_gem.h"
> > #define DRIVER_NAME "rockchip"
> > @@ -159,10 +158,6 @@ static int rockchip_drm_bind(struct device *dev)
> > drm_mode_config_reset(drm_dev);
> > - ret = rockchip_drm_fbdev_init(drm_dev);
> > - if (ret)
> > - goto err_unbind_all;
> > -
> > /* init kms poll for handling hpd */
> > drm_kms_helper_poll_init(drm_dev);
> > @@ -170,10 +165,11 @@ static int rockchip_drm_bind(struct device *dev)
> > if (ret)
> > goto err_kms_helper_poll_fini;
> > + drm_fbdev_generic_setup(drm_dev, 32);
>
> Please pass 0 for the final argument. The fbdev helpers pick 32 by default.
> Maybe leave a comment if you require 32 here.
I wanted to minimise the changes introduced here - passing 32 matches
the value passed to drm_fb_helper_initial_config() in the deleted code
from rockchip_drm_fbdev.c.
What do you think about changing this to 0 in a follow-up patch?
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-10-30 12:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 11:50 [PATCH] drm/rockchip: use generic fbdev setup John Keeping
2021-10-29 19:00 ` Thomas Zimmermann
2021-10-30 12:05 ` John Keeping [this message]
2021-10-31 18:09 ` Thomas Zimmermann
2021-11-01 11:34 ` John Keeping
2021-12-07 11:54 ` John Keeping
2021-12-07 13:00 ` Thomas Zimmermann
2022-10-17 8:11 ` [BUG] " Johan Jonker
2022-10-17 10:05 ` John Keeping
2022-10-17 11:29 ` Heiko Stuebner
2022-10-17 18:30 ` Johan Jonker
2022-10-17 19:00 ` John Keeping
2022-10-17 19:16 ` Johan Jonker
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=YX01C6l93I2YPgku@donbot \
--to=john@metanate.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=hjc@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.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).