diff options
author | Mikulas Patocka <mpatocka@redhat.com> | 2014-05-15 06:58:24 -0400 |
---|---|---|
committer | Tomi Valkeinen <tomi.valkeinen@ti.com> | 2014-05-23 13:44:25 +0300 |
commit | 972754cfaee94d6e25acf94a497bc0a864d91b7e (patch) | |
tree | b6d0e5a15c896c2c47c6f3be6813cf8045b8aca3 /firmware | |
parent | 80c68c1e2e801a14d718f2ab9690398a864aa37c (diff) |
matroxfb: perform a dummy read of M_STATUS
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>
Cc: stable@vger.kernel.org
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Diffstat (limited to 'firmware')
0 files changed, 0 insertions, 0 deletions