[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20161020003221.2941-1-stefan@agner.ch>
Date: Wed, 19 Oct 2016 17:32:18 -0700
From: Stefan Agner <stefan@...er.ch>
To: daniel.vetter@...ll.ch, meng.yi@....com,
dri-devel@...ts.freedesktop.org
Cc: alison.wang@...escale.com, jianwei.wang.chn@...il.com,
linux-kernel@...r.kernel.org, Stefan Agner <stefan@...er.ch>
Subject: [PATCH 0/3] drm/fsl-dcu: fix driver remove/DRM unload
Hi All,
The first patch is a better alternative to the previously posted
patch ("drm/fsl-dcu: only init fbdev if required") as suggested
by Daniel.
The second and third are fix related issue uncovered during tests
with bind/unbind:
echo 40058000.dcu > /sys/bus/platform/drivers/fsl-dcu/unbind
echo 40058000.dcu > /sys/bus/platform/drivers/fsl-dcu/bind
Especially the third patch I am not sure if that is a reasonable
strategy to fix the issue. I did not saw another SoC DRM driver
which is making use of drm_crtc_force_disable_all...
Also, when the X Server is running (with modesetting driver) I
still get a warning:
WARNING: CPU: 0 PID: 452 at drivers/gpu/drm/drm_crtc.c:1154 drm_mode_config_cleanup+0x210/0x220
The comment says it is the drivers fault, but as far as I can
tell it is user space which does not free up this framebuffers.
Is there something missing in my driver?
Any ideas?
--
Stefan
Stefan Agner (3):
drm/fb_cma_helper: do not free fbdev if there is none
drm/fsl-dcu: unload driver before disabling clocks
drm/fsl-dcu: disable outputs before unloading driver
drivers/gpu/drm/drm_fb_cma_helper.c | 3 ++-
drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c | 3 ++-
2 files changed, 4 insertions(+), 2 deletions(-)
--
2.10.0
Powered by blists - more mailing lists