linux/drivers/gpu/drm/mgag200
Dave Airlie 6417195995 drm/mgag200: deal with bo reserve fail in dirty update path
On F19 testing, it was noticed we get a lot of errors in dmesg
about being unable to reserve the buffer when plymouth starts,
this is due to the buffer being in the process of migrating,
so it makes sense we can't reserve it.

In order to deal with it, this adds delayed updates for the dirty
updates, when the bo is unreservable, in the normal console case
this shouldn't ever happen, its just when plymouth or X is
pushing the console bo to system memory.

Cc: stable@vger.kernel.org
Signed-off-by: Dave Airlie <airlied@redhat.com>
2013-05-02 12:46:39 +10:00
..
Kconfig drivers/gpu/drm/mgag200: remove depends on CONFIG_EXPERIMENTAL 2013-01-21 14:52:43 -08:00
Makefile mgag200: initial g200se driver (v2) 2012-05-17 10:53:41 +01:00
mgag200_drv.c Drivers: gpu: remove __dev* attributes. 2013-01-03 15:57:15 -08:00
mgag200_drv.h drm/mgag200: deal with bo reserve fail in dirty update path 2013-05-02 12:46:39 +10:00
mgag200_fb.c drm/mgag200: deal with bo reserve fail in dirty update path 2013-05-02 12:46:39 +10:00
mgag200_i2c.c drm/mgag200: Bug fix: Renesas board now selects native resolution. 2013-03-08 08:31:49 +10:00
mgag200_main.c drm/mgag200: Remove extra variable assigns 2013-04-30 09:57:23 +10:00
mgag200_mode.c drm/mgag200: Pass driver specific mga_device in driver functions 2013-04-30 09:57:02 +10:00
mgag200_reg.h mgag200: initial g200se driver (v2) 2012-05-17 10:53:41 +01:00
mgag200_ttm.c drm/mgag200: deal with bo reserve fail in dirty update path 2013-05-02 12:46:39 +10:00