diff options
author | Mikulas Patocka <mpatocka@redhat.com> | 2014-05-15 06:58:24 -0400 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2014-06-30 20:09:42 -0700 |
commit | 031767d310d44ec8e1e244ad8e8d0f5564f4a49a (patch) | |
tree | 1607a52954c183d634866367a141c4af66c6fef3 /drivers/md/dm-thin-metadata.c | |
parent | dc10f332a7fce531cd44fc5984286369a6bb71f0 (diff) | |
download | linux-3.10-031767d310d44ec8e1e244ad8e8d0f5564f4a49a.tar.gz linux-3.10-031767d310d44ec8e1e244ad8e8d0f5564f4a49a.tar.bz2 linux-3.10-031767d310d44ec8e1e244ad8e8d0f5564f4a49a.zip |
matroxfb: perform a dummy read of M_STATUS
commit 972754cfaee94d6e25acf94a497bc0a864d91b7e upstream.
I had occasional screen corruption with the matrox framebuffer driver and
I found out that the reason for the corruption is that the hardware
blitter accesses the videoram while it is being written to.
The matrox driver has a macro WaitTillIdle() that should wait until the
blitter is idle, but it sometimes doesn't work. I added a dummy read
mga_inl(M_STATUS) to WaitTillIdle() to fix the problem. The dummy read
will flush the write buffer in the PCI chipset, and the next read of
M_STATUS will return the hardware status.
Since applying this patch, I had no screen corruption at all.
Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/md/dm-thin-metadata.c')
0 files changed, 0 insertions, 0 deletions