From: CK Hu <ck.hu@mediatek.com>
To: Frank Wunderlich <frank-w@public-files.de>
Cc: "Daniel Vetter" <daniel@ffwll.ch>,
srv_heupstream@mediatek.com, "David Airlie" <airlied@linux.ie>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
"\"Noralf Tr�nnes\"" <noralf@tronnes.org>,
linux-mediatek@lists.infradead.org,
"Philipp Zabel" <p.zabel@pengutronix.de>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: Aw: [PATCH 2/2] drm/mediatek: Add Mediatek framebuffer device
Date: Fri, 18 Jan 2019 09:46:15 +0800 [thread overview]
Message-ID: <1547775975.4221.11.camel@mtksdaap41> (raw)
In-Reply-To: <trinity-1adab8be-573a-4816-9e9f-feddf07bdcd3-1547734452313@3c-app-gmx-bs28>
Hi, Frank:
On Thu, 2019-01-17 at 15:14 +0100, Frank Wunderlich wrote:
> Hi,
>
> this Patchset does not hang on Bananapi R2, but does not show anything on FB-Console...seems anything is missing
>
> https://github.com/frank-w/BPI-R2-4.14/tree/4.20-fbdev
>
> dmesg | grep 'fb\|framebuffer'
> [ 0.000000] Linux version 4.20.0-rc7-bpi-r2-fbdev (frank@frank-N56VZ) (gcc version 7.3.0 (Ubuntu/Linaro 7.3.0-27ubuntu1~18.04)) 9
> [ 0.000000] cma: Reserved 64 MiB at 0xfb800000
> [ 0.000000] Kernel command line: board=bpi-r2 console=earlyprintk console=tty1 fbcon=map:0 console=ttyS0,115200 root=/dev/mmcblk7
> [ 5.733185] [drm:drm_fb_helper_generic_probe] surface width(1280), height(1024) and bpp(32)
> [ 5.754452] [drm:drm_mode_addfb2] [FB:44]
> [ 5.792878] mediatek-drm 14000000.dispsys: fb0: DRM emulated frame buffer device
> [ 5.814067] [drm:drm_fb_helper_hotplug_event.part.11]
> [ 6.203083] mediatek-drm 14000000.dispsys: [drm:drm_client_dev_hotplug] fbdev: ret=0
> [ 24.930347] mediatek-drm 14000000.dispsys: [drm:drm_client_dev_restore] fbdev: ret=0
> [ 25.196872] mediatek-drm 14000000.dispsys: [drm:drm_client_dev_restore] fbdev: ret=0
> [ 25.281184] [drm:drm_mode_addfb2] [FB:49]
> [ 27.947962] [drm:drm_mode_addfb2] [FB:49]
The log does not show any information of error, but it close fbdev at
the time 24.930347.
I just test vmap() by writing white color into framebuffer after vmap()
and use user space program to control fbdev to show this framebuffer and
the panel shows white screen. So I believe that vmap() and fbdev works
fine, but I'm not sure what happen to fbcon. I would try to setup fbcon
to find out the bug. If you could try to debug parallelly, it would be
much help.
Regards,
CK
>
> regards Frank
>
>
> > Gesendet: Mittwoch, 16. Januar 2019 um 02:39 Uhr
> > Von: "CK Hu" <ck.hu@mediatek.com>
> > An: "Philipp Zabel" <p.zabel@pengutronix.de>, "David Airlie" <airlied@linux.ie>, "Daniel Vetter" <daniel@ffwll.ch>, "Matthias Brugger" <matthias.bgg@gmail.com>, "Noralf Tr�nnes" <noralf@tronnes.org>, "Frank Wunderlich" <frank-w@public-files.de>
> > Cc: dri-devel@lists.freedesktop.org, linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org, srv_heupstream@mediatek.com, "CK Hu" <ck.hu@mediatek.com>
> > Betreff: [PATCH 2/2] drm/mediatek: Add Mediatek framebuffer device
> >
> > For Mediatek drm driver, use fbdev emulation to create a framebuffer
> > device.
> >
> > Signed-off-by: CK Hu <ck.hu@mediatek.com>
> > ---
> > drivers/gpu/drm/mediatek/mtk_drm_drv.c | 5 +++++
> > 1 file changed, 5 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/mediatek/mtk_drm_drv.c b/drivers/gpu/drm/mediatek/mtk_drm_drv.c
> > index 6ec4ca070382..5fcc0e294696 100644
> > --- a/drivers/gpu/drm/mediatek/mtk_drm_drv.c
> > +++ b/drivers/gpu/drm/mediatek/mtk_drm_drv.c
> > @@ -16,6 +16,7 @@
> > #include <drm/drm_atomic.h>
> > #include <drm/drm_atomic_helper.h>
> > #include <drm/drm_crtc_helper.h>
> > +#include <drm/drm_fb_helper.h>
> > #include <drm/drm_gem.h>
> > #include <drm/drm_gem_cma_helper.h>
> > #include <drm/drm_of.h>
> > @@ -378,6 +379,10 @@ static int mtk_drm_bind(struct device *dev)
> > if (ret < 0)
> > goto err_deinit;
> >
> > + ret = drm_fbdev_generic_setup(drm, 32);
> > + if (ret)
> > + DRM_ERROR("Failed to initialize fbdev: %d\n", ret);
> > +
> > return 0;
> >
> > err_deinit:
> > --
> > 2.18.1
> >
> >
>
> _______________________________________________
> Linux-mediatek mailing list
> Linux-mediatek@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-mediatek
_______________________________________________
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:[~2019-01-18 1:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 1:39 [PATCH 1/2] drm/mediatek: Implement gem prime vmap/vunmap function CK Hu
2019-01-16 1:39 ` [PATCH 2/2] drm/mediatek: Add Mediatek framebuffer device CK Hu
2019-01-17 14:14 ` Aw: " Frank Wunderlich
2019-01-18 1:46 ` CK Hu [this message]
2019-01-18 8:39 ` Matthias Brugger
2019-01-18 12:33 ` Aw: " Frank Wunderlich
2019-01-20 13:36 ` Frank Wunderlich
2019-03-19 3:12 ` CK Hu
2019-03-19 16:52 ` Aw: " Frank Wunderlich
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=1547775975.4221.11.camel@mtksdaap41 \
--to=ck.hu@mediatek.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=frank-w@public-files.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=noralf@tronnes.org \
--cc=p.zabel@pengutronix.de \
--cc=srv_heupstream@mediatek.com \
/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