summaryrefslogtreecommitdiff
path: root/drivers/gpu/drm/i915/display/intel_panel.h
diff options
context:
space:
mode:
authorVille Syrjälä <ville.syrjala@linux.intel.com>2020-09-10 00:38:23 +0300
committerVille Syrjälä <ville.syrjala@linux.intel.com>2020-09-15 14:57:13 +0300
commitda27bd41d0ebcc21bff308236bbf5595ce85b67a (patch)
tree51dc3bc174e8021b3655878370bc9254c79d2946 /drivers/gpu/drm/i915/display/intel_panel.h
parentac03de1f5e8380a8f16728407619d9e5a4a351b0 (diff)
drm/i915: Reduce INTEL_DISPLAY_ENABLED to just removing the outputs
Having a mode where the display hardware is present but we try to pretend it isn't just leads to massive headaches when trying to reason what the fallout might be from skipping some random bits of programming. Let's just neuter INTEL_DISPLAY_ENABLED so that we treat the hardware as fully present, except we just don't register any outputs. That's still rather sketchy if the outputs are already enabled when the driver is loaded. I think the simplest solution would be to probe everything as normal and just return disconnected" from all .detect() hooks. That would avoid anything automagically enabling those outputs, but the driver could then shut things down using the normal codepaths. Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20200909213824.12390-1-ville.syrjala@linux.intel.com Reviewed-by: Jani Nikula <jani.nikula@intel.com>
Diffstat (limited to 'drivers/gpu/drm/i915/display/intel_panel.h')
0 files changed, 0 insertions, 0 deletions