diff options
| author | Stefan Agner <stefan.agner@toradex.com> | 2015-06-11 09:25:04 +0200 |
|---|---|---|
| committer | Stefan Agner <stefan.agner@toradex.com> | 2015-07-01 15:04:34 +0200 |
| commit | 1668362effee27780c7eeace482681265cb1e3f3 (patch) | |
| tree | e34f427e8b0e8fe42b3f608e63a59f42e55004c9 /kernel/irq | |
| parent | 3d392402aea0db20ed99b1cc4fb51254ef0c4948 (diff) | |
video: fsl-dcu-fb: remove underrun interrupt handling
The current buffer underrun interrupt handling seems bogus in
multiple ways: Disabling and reenabling the controller seems a
questionable procedure and is also not documented. Furthermore,
to apply a DCU mode, a register transfer would be necessary
(UPDATE_MODE).
The current implementation probably even introduce races: If
a underrun happens just when enabling the controller (which has
been observed to happen quite often during initialization), the
register could still be in transfer mode. A write to a register
could still be transferred in this situation, which might lead
that the DCU off mode is transferred. Since the interrupt handler
does not initiate another register transfer, the controller would
stay off in this situation...
Rare conditions have been observed in which the controller ends
up in test mode. The race condition outlined above describes a
sequence in which the controller ends up beeing disabled. However,
before cd586e4cf9dc ("video: fsl-dcu-fb: fix operating mode off)
the DCU state off and test have been mixed up, hence this patch
could in fact fix that issue.
Diffstat (limited to 'kernel/irq')
0 files changed, 0 insertions, 0 deletions