diff options
| author | Chris Wilson <chris@chris-wilson.co.uk> | 2014-04-09 09:19:42 +0100 |
|---|---|---|
| committer | Daniel Vetter <daniel.vetter@ffwll.ch> | 2014-05-05 09:08:38 +0200 |
| commit | 6099032045d4d83bf643b5fe33caaa8e56e7f5de (patch) | |
| tree | 6b5853a35e76e63127b8cbfed73c2e0e53dfb1c8 /drivers/gpu/drm/i915/intel_ringbuffer.c | |
| parent | e3efda49e736b8b0de3a5adb45e412cf90fdaf8d (diff) | |
drm/i915: Allow the module to load even if we fail to setup rings
Even without enabling the ringbuffers to allow command execution, we can
still control the display engines to enable modesetting. So make the
ringbuffer initialization failure soft, and mark the GPU as wedged
instead.
v2: Only treat an EIO from ring initialisation as a soft failure, and
abort module load for any other failure, such as allocation failures.
v3: Add an *ERROR* prior to declaring the GPU wedged so that it stands
out like a sore thumb in the logs
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Reviewed-by: Oscar Mateo <oscar.mateo@intel.com>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Diffstat (limited to 'drivers/gpu/drm/i915/intel_ringbuffer.c')
0 files changed, 0 insertions, 0 deletions