diff options
author | Ville Syrjälä <ville.syrjala@linux.intel.com> | 2014-12-02 14:10:46 +0200 |
---|---|---|
committer | Daniel Vetter <daniel.vetter@ffwll.ch> | 2014-12-03 09:31:53 +0100 |
commit | 00f0b3781028605910cb4662a0f8a4849b445fc2 (patch) | |
tree | 1e754a0524bda40b30a12cfdaf367ff43d815ee3 /mm/memory.c | |
parent | 9939fba226649c62630a74d36ee45c5d5402b460 (diff) | |
download | op-kernel-dev-00f0b3781028605910cb4662a0f8a4849b445fc2.zip op-kernel-dev-00f0b3781028605910cb4662a0f8a4849b445fc2.tar.gz |
drm/i915: Reject modeset when the same digital port is used more than once
On pre-HSW we have two encoders per digital port: one HDMI, one DP.
However they are the same physical port in hardware and we can't enable
both at the same time. Reject the modeset if the user attempts this.
So far we've been saved by the fact that we never see both HDMI and DP
connectors as connected. But if the user decides to force a mode anyway,
all kinds of funny stuff might happen.
Unfortunately we don't seem to have any way to inform userspace that
such configurations are invalid except by returning an error from
setcrtc. possible_clones only covers real cloning situations, and
looking at the connector names doesn't work either since we don't
always register both connectors for the same port. I suppose the
only way to fix that would be to expose only a single encoder per
digital port like we do on HSW+ but that would be a fairly large
undertaking for little gain.
kms_setmode hits this since it forces modes on non-connected VGA and
HDMI connectors. Previosuly it just resulted in weirdness such as
failed link training. With this patch it will now get an error back
from the kernel and will die with an assert since it thinks that the
configuration should be fine.
v2: Deal with INTEL_OUTPUT_UNKNOWN (Paulo)
Cc: Paulo Zanoni <przanoni@gmail.com>
Reviewed-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Diffstat (limited to 'mm/memory.c')
0 files changed, 0 insertions, 0 deletions