DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
/*
|
|
|
|
* Copyright © 2006-2007 Intel Corporation
|
|
|
|
*
|
|
|
|
* Permission is hereby granted, free of charge, to any person obtaining a
|
|
|
|
* copy of this software and associated documentation files (the "Software"),
|
|
|
|
* to deal in the Software without restriction, including without limitation
|
|
|
|
* the rights to use, copy, modify, merge, publish, distribute, sublicense,
|
|
|
|
* and/or sell copies of the Software, and to permit persons to whom the
|
|
|
|
* Software is furnished to do so, subject to the following conditions:
|
|
|
|
*
|
|
|
|
* The above copyright notice and this permission notice (including the next
|
|
|
|
* paragraph) shall be included in all copies or substantial portions of the
|
|
|
|
* Software.
|
|
|
|
*
|
|
|
|
* THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
|
|
* IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
|
|
* FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
|
|
|
|
* THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
|
|
* LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
|
|
|
|
* FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
|
|
|
|
* DEALINGS IN THE SOFTWARE.
|
|
|
|
*
|
|
|
|
* Authors:
|
|
|
|
* Eric Anholt <eric@anholt.net>
|
|
|
|
*/
|
|
|
|
|
2011-10-26 05:42:21 +07:00
|
|
|
#include <linux/dmi.h>
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
#include <linux/i2c.h>
|
include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from percpu.h
percpu.h is included by sched.h and module.h and thus ends up being
included when building most .c files. percpu.h includes slab.h which
in turn includes gfp.h making everything defined by the two files
universally available and complicating inclusion dependencies.
percpu.h -> slab.h dependency is about to be removed. Prepare for
this change by updating users of gfp and slab facilities include those
headers directly instead of assuming availability. As this conversion
needs to touch large number of source files, the following script is
used as the basis of conversion.
http://userweb.kernel.org/~tj/misc/slabh-sweep.py
The script does the followings.
* Scan files for gfp and slab usages and update includes such that
only the necessary includes are there. ie. if only gfp is used,
gfp.h, if slab is used, slab.h.
* When the script inserts a new include, it looks at the include
blocks and try to put the new include such that its order conforms
to its surrounding. It's put in the include block which contains
core kernel includes, in the same order that the rest are ordered -
alphabetical, Christmas tree, rev-Xmas-tree or at the end if there
doesn't seem to be any matching order.
* If the script can't find a place to put a new include (mostly
because the file doesn't have fitting include block), it prints out
an error message indicating which .h file needs to be added to the
file.
The conversion was done in the following steps.
1. The initial automatic conversion of all .c files updated slightly
over 4000 files, deleting around 700 includes and adding ~480 gfp.h
and ~3000 slab.h inclusions. The script emitted errors for ~400
files.
2. Each error was manually checked. Some didn't need the inclusion,
some needed manual addition while adding it to implementation .h or
embedding .c file was more appropriate for others. This step added
inclusions to around 150 files.
3. The script was run again and the output was compared to the edits
from #2 to make sure no file was left behind.
4. Several build tests were done and a couple of problems were fixed.
e.g. lib/decompress_*.c used malloc/free() wrappers around slab
APIs requiring slab.h to be added manually.
5. The script was run on all .h files but without automatically
editing them as sprinkling gfp.h and slab.h inclusions around .h
files could easily lead to inclusion dependency hell. Most gfp.h
inclusion directives were ignored as stuff from gfp.h was usually
wildly available and often used in preprocessor macros. Each
slab.h inclusion directive was examined and added manually as
necessary.
6. percpu.h was updated not to include slab.h.
7. Build test were done on the following configurations and failures
were fixed. CONFIG_GCOV_KERNEL was turned off for all tests (as my
distributed build env didn't work with gcov compiles) and a few
more options had to be turned off depending on archs to make things
build (like ipr on powerpc/64 which failed due to missing writeq).
* x86 and x86_64 UP and SMP allmodconfig and a custom test config.
* powerpc and powerpc64 SMP allmodconfig
* sparc and sparc64 SMP allmodconfig
* ia64 SMP allmodconfig
* s390 SMP allmodconfig
* alpha SMP allmodconfig
* um on x86_64 SMP allmodconfig
8. percpu.h modifications were reverted so that it could be applied as
a separate patch and serve as bisection point.
Given the fact that I had only a couple of failures from tests on step
6, I'm fairly confident about the coverage of this conversion patch.
If there is a breakage, it's likely to be something in one of the arch
headers which should be easily discoverable easily on most builds of
the specific arch.
Signed-off-by: Tejun Heo <tj@kernel.org>
Guess-its-ok-by: Christoph Lameter <cl@linux-foundation.org>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
2010-03-24 15:04:11 +07:00
|
|
|
#include <linux/slab.h>
|
2012-10-03 00:01:07 +07:00
|
|
|
#include <drm/drmP.h>
|
2015-01-23 07:50:32 +07:00
|
|
|
#include <drm/drm_atomic_helper.h>
|
2012-10-03 00:01:07 +07:00
|
|
|
#include <drm/drm_crtc.h>
|
|
|
|
#include <drm/drm_crtc_helper.h>
|
|
|
|
#include <drm/drm_edid.h>
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
#include "intel_drv.h"
|
2012-10-03 00:01:07 +07:00
|
|
|
#include <drm/i915_drm.h>
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
#include "i915_drv.h"
|
|
|
|
|
2010-11-16 15:03:53 +07:00
|
|
|
/* Here's the desired hotplug mode */
|
|
|
|
#define ADPA_HOTPLUG_BITS (ADPA_CRT_HOTPLUG_PERIOD_128 | \
|
|
|
|
ADPA_CRT_HOTPLUG_WARMUP_10MS | \
|
|
|
|
ADPA_CRT_HOTPLUG_SAMPLE_4S | \
|
|
|
|
ADPA_CRT_HOTPLUG_VOLTAGE_50 | \
|
|
|
|
ADPA_CRT_HOTPLUG_VOLREF_325MV | \
|
|
|
|
ADPA_CRT_HOTPLUG_ENABLE)
|
|
|
|
|
2010-11-16 17:58:37 +07:00
|
|
|
struct intel_crt {
|
|
|
|
struct intel_encoder base;
|
2013-03-26 02:40:05 +07:00
|
|
|
/* DPMS state is stored in the connector, which we need in the
|
|
|
|
* encoder's enable/disable callbacks */
|
|
|
|
struct intel_connector *connector;
|
2010-11-16 15:03:53 +07:00
|
|
|
bool force_hotplug_required;
|
drm/i915: Type safe register read/write
Make I915_READ and I915_WRITE more type safe by wrapping the register
offset in a struct. This should eliminate most of the fumbles we've had
with misplaced parens.
This only takes care of normal mmio registers. We could extend the idea
to other register types and define each with its own struct. That way
you wouldn't be able to accidentally pass the wrong thing to a specific
register access function.
The gpio_reg setup is probably the ugliest thing left. But I figure I'd
just leave it for now, and wait for some divine inspiration to strike
before making it nice.
As for the generated code, it's actually a bit better sometimes. Eg.
looking at i915_irq_handler(), we can see the following change:
lea 0x70024(%rdx,%rax,1),%r9d
mov $0x1,%edx
- movslq %r9d,%r9
- mov %r9,%rsi
- mov %r9,-0x58(%rbp)
- callq *0xd8(%rbx)
+ mov %r9d,%esi
+ mov %r9d,-0x48(%rbp)
callq *0xd8(%rbx)
So previously gcc thought the register offset might be signed and
decided to sign extend it, just in case. The rest appears to be
mostly just minor shuffling of instructions.
v2: i915_mmio_reg_{offset,equal,valid}() helpers added
s/_REG/_MMIO/ in the register defines
mo more switch statements left to worry about
ring_emit stuff got sorted in a prep patch
cmd parser, lrc context and w/a batch buildup also in prep patch
vgpu stuff cleaned up and moved to a prep patch
all other unrelated changes split out
v3: Rebased due to BXT DSI/BLC, MOCS, etc.
v4: Rebased due to churn, s/i915_mmio_reg_t/i915_reg_t/
Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Link: http://patchwork.freedesktop.org/patch/msgid/1447853606-2751-1-git-send-email-ville.syrjala@linux.intel.com
2015-11-18 20:33:26 +07:00
|
|
|
i915_reg_t adpa_reg;
|
2010-11-16 17:58:37 +07:00
|
|
|
};
|
|
|
|
|
2013-07-22 02:37:03 +07:00
|
|
|
static struct intel_crt *intel_encoder_to_crt(struct intel_encoder *encoder)
|
2010-11-16 17:58:37 +07:00
|
|
|
{
|
2013-07-22 02:37:03 +07:00
|
|
|
return container_of(encoder, struct intel_crt, base);
|
2010-11-16 17:58:37 +07:00
|
|
|
}
|
|
|
|
|
2013-07-22 02:37:03 +07:00
|
|
|
static struct intel_crt *intel_attached_crt(struct drm_connector *connector)
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
{
|
2013-07-22 02:37:03 +07:00
|
|
|
return intel_encoder_to_crt(intel_attached_encoder(connector));
|
2012-07-11 21:27:57 +07:00
|
|
|
}
|
|
|
|
|
2018-05-15 00:24:19 +07:00
|
|
|
bool intel_crt_port_enabled(struct drm_i915_private *dev_priv,
|
|
|
|
i915_reg_t adpa_reg, enum pipe *pipe)
|
|
|
|
{
|
|
|
|
u32 val;
|
|
|
|
|
|
|
|
val = I915_READ(adpa_reg);
|
|
|
|
|
|
|
|
/* asserts want to know the pipe even if the port is disabled */
|
|
|
|
if (HAS_PCH_CPT(dev_priv))
|
|
|
|
*pipe = (val & ADPA_PIPE_SEL_MASK_CPT) >> ADPA_PIPE_SEL_SHIFT_CPT;
|
|
|
|
else
|
|
|
|
*pipe = (val & ADPA_PIPE_SEL_MASK) >> ADPA_PIPE_SEL_SHIFT;
|
|
|
|
|
|
|
|
return val & ADPA_DAC_ENABLE;
|
|
|
|
}
|
|
|
|
|
2012-07-02 18:41:21 +07:00
|
|
|
static bool intel_crt_get_hw_state(struct intel_encoder *encoder,
|
|
|
|
enum pipe *pipe)
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
{
|
2018-05-15 00:24:19 +07:00
|
|
|
struct drm_i915_private *dev_priv = to_i915(encoder->base.dev);
|
2012-07-02 18:41:21 +07:00
|
|
|
struct intel_crt *crt = intel_encoder_to_crt(encoder);
|
2016-02-12 23:55:15 +07:00
|
|
|
bool ret;
|
2012-07-02 18:41:21 +07:00
|
|
|
|
2017-02-22 13:34:27 +07:00
|
|
|
if (!intel_display_power_get_if_enabled(dev_priv,
|
|
|
|
encoder->power_domain))
|
2014-03-05 21:20:54 +07:00
|
|
|
return false;
|
|
|
|
|
2018-05-15 00:24:19 +07:00
|
|
|
ret = intel_crt_port_enabled(dev_priv, crt->adpa_reg, pipe);
|
2012-07-02 18:41:21 +07:00
|
|
|
|
2017-02-22 13:34:27 +07:00
|
|
|
intel_display_power_put(dev_priv, encoder->power_domain);
|
2016-02-12 23:55:15 +07:00
|
|
|
|
|
|
|
return ret;
|
2012-07-02 18:41:21 +07:00
|
|
|
}
|
|
|
|
|
2013-09-24 18:24:05 +07:00
|
|
|
static unsigned int intel_crt_get_flags(struct intel_encoder *encoder)
|
2013-05-15 07:08:26 +07:00
|
|
|
{
|
2016-07-04 17:34:36 +07:00
|
|
|
struct drm_i915_private *dev_priv = to_i915(encoder->base.dev);
|
2013-05-15 07:08:26 +07:00
|
|
|
struct intel_crt *crt = intel_encoder_to_crt(encoder);
|
|
|
|
u32 tmp, flags = 0;
|
|
|
|
|
|
|
|
tmp = I915_READ(crt->adpa_reg);
|
|
|
|
|
|
|
|
if (tmp & ADPA_HSYNC_ACTIVE_HIGH)
|
|
|
|
flags |= DRM_MODE_FLAG_PHSYNC;
|
|
|
|
else
|
|
|
|
flags |= DRM_MODE_FLAG_NHSYNC;
|
|
|
|
|
|
|
|
if (tmp & ADPA_VSYNC_ACTIVE_HIGH)
|
|
|
|
flags |= DRM_MODE_FLAG_PVSYNC;
|
|
|
|
else
|
|
|
|
flags |= DRM_MODE_FLAG_NVSYNC;
|
|
|
|
|
2013-09-24 18:24:05 +07:00
|
|
|
return flags;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void intel_crt_get_config(struct intel_encoder *encoder,
|
2015-01-15 19:55:21 +07:00
|
|
|
struct intel_crtc_state *pipe_config)
|
2013-09-24 18:24:05 +07:00
|
|
|
{
|
2017-10-28 02:31:23 +07:00
|
|
|
pipe_config->output_types |= BIT(INTEL_OUTPUT_ANALOG);
|
|
|
|
|
2015-01-15 19:55:22 +07:00
|
|
|
pipe_config->base.adjusted_mode.flags |= intel_crt_get_flags(encoder);
|
2013-09-13 20:00:08 +07:00
|
|
|
|
2016-02-18 02:41:09 +07:00
|
|
|
pipe_config->base.adjusted_mode.crtc_clock = pipe_config->port_clock;
|
2013-05-15 07:08:26 +07:00
|
|
|
}
|
|
|
|
|
2013-09-24 18:24:05 +07:00
|
|
|
static void hsw_crt_get_config(struct intel_encoder *encoder,
|
2015-01-15 19:55:21 +07:00
|
|
|
struct intel_crtc_state *pipe_config)
|
2013-09-24 18:24:05 +07:00
|
|
|
{
|
2016-02-18 02:41:12 +07:00
|
|
|
struct drm_i915_private *dev_priv = to_i915(encoder->base.dev);
|
|
|
|
|
2013-09-24 18:24:05 +07:00
|
|
|
intel_ddi_get_config(encoder, pipe_config);
|
|
|
|
|
2015-01-15 19:55:22 +07:00
|
|
|
pipe_config->base.adjusted_mode.flags &= ~(DRM_MODE_FLAG_PHSYNC |
|
2013-09-24 18:24:05 +07:00
|
|
|
DRM_MODE_FLAG_NHSYNC |
|
|
|
|
DRM_MODE_FLAG_PVSYNC |
|
|
|
|
DRM_MODE_FLAG_NVSYNC);
|
2015-01-15 19:55:22 +07:00
|
|
|
pipe_config->base.adjusted_mode.flags |= intel_crt_get_flags(encoder);
|
2016-02-18 02:41:12 +07:00
|
|
|
|
|
|
|
pipe_config->base.adjusted_mode.crtc_clock = lpt_get_iclkip(dev_priv);
|
2013-09-24 18:24:05 +07:00
|
|
|
}
|
|
|
|
|
drm/i915: convert dpms functions of dvo/sdvo/crt
Yeah, big patch but I couldn't come up with a neat idea of how to
split it up further, that wouldn't break dpms on cloned configs
somehow. But the changes in dvo/sdvo/crt are all pretty much
orthonogal, so it's not too bad a patch.
These are the only encoders that support cloning, which requires a few
special changes compared to the previous patches.
- Compute the desired state of the display pipe by walking all
connected encoders and checking whether any has active connectors.
To make this clearer, drop the old mode parameter to the crtc dpms
function and rename it to intel_crtc_update_dpms.
- There's the curious case of intel_crtc->dpms_mode. With the previous
patches to remove the overlay pipe A code and to rework the load
detect pipe code, the big users are gone. We still keep it to avoid
enabling the pipe twice, but we duplicate this logic with
crtc->active, too. Still, leave this for now and just push a fake
dpms mode into it that reflects the state of the display pipe.
Changes in the encoder dpms functions:
- We clamp the dpms state to the supported range right away. This is
escpecially important for the VGA outputs, where only older hw
supports the intermediate states. This (and the crt->adpa_reg patch)
allows us to unify the crt dpms code again between all variants
(gmch, vlv and pch).
- We only enable/disable the output for dvo/sdvo and leave the encoder
running. The encoder will be disabled/enabled when we switch the
state of the entire output pipeline (which will happen right away
for non-cloned setups). This way the duplication is reduced and
strange interaction when disabling output ports at the wrong time
avoided.
The dpms code for all three types of connectors contains a bit of
duplicated logic, but I think keeping these special cases separate is
simpler: CRT is the only one that hanldes intermediate dpms state
(which requires extra logic to enable/disable things in the right
order), and introducing some abstraction just to share the code
between dvo and sdvo smells like overkill. We can do that once someone
bothers to implement cloning for the more modern outputs. But I doubt
that this will ever happen.
v2: s/crtc/crt/_set_dpms, noticed by Paulo Zanoni.
Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-Off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
2012-07-02 03:42:24 +07:00
|
|
|
/* Note: The caller is required to filter out dpms modes not supported by the
|
|
|
|
* platform. */
|
2016-08-09 22:04:07 +07:00
|
|
|
static void intel_crt_set_dpms(struct intel_encoder *encoder,
|
2017-08-18 20:49:58 +07:00
|
|
|
const struct intel_crtc_state *crtc_state,
|
2016-08-09 22:04:07 +07:00
|
|
|
int mode)
|
2012-04-18 05:06:33 +07:00
|
|
|
{
|
2016-11-16 15:55:40 +07:00
|
|
|
struct drm_i915_private *dev_priv = to_i915(encoder->base.dev);
|
drm/i915: convert dpms functions of dvo/sdvo/crt
Yeah, big patch but I couldn't come up with a neat idea of how to
split it up further, that wouldn't break dpms on cloned configs
somehow. But the changes in dvo/sdvo/crt are all pretty much
orthonogal, so it's not too bad a patch.
These are the only encoders that support cloning, which requires a few
special changes compared to the previous patches.
- Compute the desired state of the display pipe by walking all
connected encoders and checking whether any has active connectors.
To make this clearer, drop the old mode parameter to the crtc dpms
function and rename it to intel_crtc_update_dpms.
- There's the curious case of intel_crtc->dpms_mode. With the previous
patches to remove the overlay pipe A code and to rework the load
detect pipe code, the big users are gone. We still keep it to avoid
enabling the pipe twice, but we duplicate this logic with
crtc->active, too. Still, leave this for now and just push a fake
dpms mode into it that reflects the state of the display pipe.
Changes in the encoder dpms functions:
- We clamp the dpms state to the supported range right away. This is
escpecially important for the VGA outputs, where only older hw
supports the intermediate states. This (and the crt->adpa_reg patch)
allows us to unify the crt dpms code again between all variants
(gmch, vlv and pch).
- We only enable/disable the output for dvo/sdvo and leave the encoder
running. The encoder will be disabled/enabled when we switch the
state of the entire output pipeline (which will happen right away
for non-cloned setups). This way the duplication is reduced and
strange interaction when disabling output ports at the wrong time
avoided.
The dpms code for all three types of connectors contains a bit of
duplicated logic, but I think keeping these special cases separate is
simpler: CRT is the only one that hanldes intermediate dpms state
(which requires extra logic to enable/disable things in the right
order), and introducing some abstraction just to share the code
between dvo and sdvo smells like overkill. We can do that once someone
bothers to implement cloning for the more modern outputs. But I doubt
that this will ever happen.
v2: s/crtc/crt/_set_dpms, noticed by Paulo Zanoni.
Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-Off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
2012-07-02 03:42:24 +07:00
|
|
|
struct intel_crt *crt = intel_encoder_to_crt(encoder);
|
2016-08-09 22:04:07 +07:00
|
|
|
struct intel_crtc *crtc = to_intel_crtc(crtc_state->base.crtc);
|
|
|
|
const struct drm_display_mode *adjusted_mode = &crtc_state->base.adjusted_mode;
|
2014-04-25 04:54:44 +07:00
|
|
|
u32 adpa;
|
|
|
|
|
2016-11-16 15:55:40 +07:00
|
|
|
if (INTEL_GEN(dev_priv) >= 5)
|
2014-04-25 04:54:44 +07:00
|
|
|
adpa = ADPA_HOTPLUG_BITS;
|
|
|
|
else
|
|
|
|
adpa = 0;
|
2012-04-18 05:06:33 +07:00
|
|
|
|
2014-04-25 04:54:44 +07:00
|
|
|
if (adjusted_mode->flags & DRM_MODE_FLAG_PHSYNC)
|
|
|
|
adpa |= ADPA_HSYNC_ACTIVE_HIGH;
|
|
|
|
if (adjusted_mode->flags & DRM_MODE_FLAG_PVSYNC)
|
|
|
|
adpa |= ADPA_VSYNC_ACTIVE_HIGH;
|
|
|
|
|
|
|
|
/* For CPT allow 3 pipe config, for others just use A or B */
|
2016-10-13 17:02:53 +07:00
|
|
|
if (HAS_PCH_LPT(dev_priv))
|
2014-04-25 04:54:44 +07:00
|
|
|
; /* Those bits don't exist here */
|
2016-10-13 17:02:53 +07:00
|
|
|
else if (HAS_PCH_CPT(dev_priv))
|
2018-05-15 00:24:19 +07:00
|
|
|
adpa |= ADPA_PIPE_SEL_CPT(crtc->pipe);
|
2014-04-25 04:54:44 +07:00
|
|
|
else
|
2018-05-15 00:24:19 +07:00
|
|
|
adpa |= ADPA_PIPE_SEL(crtc->pipe);
|
2014-04-25 04:54:44 +07:00
|
|
|
|
2016-10-13 17:02:53 +07:00
|
|
|
if (!HAS_PCH_SPLIT(dev_priv))
|
2014-04-25 04:54:44 +07:00
|
|
|
I915_WRITE(BCLRPAT(crtc->pipe), 0);
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
|
2011-08-17 02:34:10 +07:00
|
|
|
switch (mode) {
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
case DRM_MODE_DPMS_ON:
|
2014-04-25 04:54:44 +07:00
|
|
|
adpa |= ADPA_DAC_ENABLE;
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
break;
|
|
|
|
case DRM_MODE_DPMS_STANDBY:
|
2014-04-25 04:54:44 +07:00
|
|
|
adpa |= ADPA_DAC_ENABLE | ADPA_HSYNC_CNTL_DISABLE;
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
break;
|
|
|
|
case DRM_MODE_DPMS_SUSPEND:
|
2014-04-25 04:54:44 +07:00
|
|
|
adpa |= ADPA_DAC_ENABLE | ADPA_VSYNC_CNTL_DISABLE;
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
break;
|
|
|
|
case DRM_MODE_DPMS_OFF:
|
2014-04-25 04:54:44 +07:00
|
|
|
adpa |= ADPA_HSYNC_CNTL_DISABLE | ADPA_VSYNC_CNTL_DISABLE;
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
2014-04-25 04:54:44 +07:00
|
|
|
I915_WRITE(crt->adpa_reg, adpa);
|
2012-04-18 05:06:33 +07:00
|
|
|
}
|
2009-06-05 14:38:42 +07:00
|
|
|
|
2016-08-09 22:04:04 +07:00
|
|
|
static void intel_disable_crt(struct intel_encoder *encoder,
|
2017-08-18 20:49:58 +07:00
|
|
|
const struct intel_crtc_state *old_crtc_state,
|
|
|
|
const struct drm_connector_state *old_conn_state)
|
2013-03-26 02:40:05 +07:00
|
|
|
{
|
2016-08-09 22:04:07 +07:00
|
|
|
intel_crt_set_dpms(encoder, old_crtc_state, DRM_MODE_DPMS_OFF);
|
2013-03-26 02:40:05 +07:00
|
|
|
}
|
|
|
|
|
2016-08-09 22:04:04 +07:00
|
|
|
static void pch_disable_crt(struct intel_encoder *encoder,
|
2017-08-18 20:49:58 +07:00
|
|
|
const struct intel_crtc_state *old_crtc_state,
|
|
|
|
const struct drm_connector_state *old_conn_state)
|
2015-05-05 21:17:37 +07:00
|
|
|
{
|
|
|
|
}
|
|
|
|
|
2016-08-09 22:04:04 +07:00
|
|
|
static void pch_post_disable_crt(struct intel_encoder *encoder,
|
2017-08-18 20:49:58 +07:00
|
|
|
const struct intel_crtc_state *old_crtc_state,
|
|
|
|
const struct drm_connector_state *old_conn_state)
|
2015-05-05 21:17:37 +07:00
|
|
|
{
|
2016-08-09 22:04:04 +07:00
|
|
|
intel_disable_crt(encoder, old_crtc_state, old_conn_state);
|
2015-05-05 21:17:37 +07:00
|
|
|
}
|
2014-06-26 02:01:52 +07:00
|
|
|
|
2017-10-05 17:52:11 +07:00
|
|
|
static void hsw_disable_crt(struct intel_encoder *encoder,
|
|
|
|
const struct intel_crtc_state *old_crtc_state,
|
|
|
|
const struct drm_connector_state *old_conn_state)
|
|
|
|
{
|
2017-11-01 03:51:19 +07:00
|
|
|
struct drm_i915_private *dev_priv = to_i915(encoder->base.dev);
|
2017-10-05 17:52:11 +07:00
|
|
|
|
2017-11-01 03:51:19 +07:00
|
|
|
WARN_ON(!old_crtc_state->has_pch_encoder);
|
2017-10-05 17:52:11 +07:00
|
|
|
|
|
|
|
intel_set_pch_fifo_underrun_reporting(dev_priv, PIPE_A, false);
|
|
|
|
}
|
|
|
|
|
2016-08-23 21:18:08 +07:00
|
|
|
static void hsw_post_disable_crt(struct intel_encoder *encoder,
|
2017-08-18 20:49:58 +07:00
|
|
|
const struct intel_crtc_state *old_crtc_state,
|
|
|
|
const struct drm_connector_state *old_conn_state)
|
2016-08-23 21:18:08 +07:00
|
|
|
{
|
|
|
|
struct drm_i915_private *dev_priv = to_i915(encoder->base.dev);
|
|
|
|
|
2018-06-14 00:27:46 +07:00
|
|
|
intel_ddi_disable_pipe_clock(old_crtc_state);
|
|
|
|
|
2016-08-23 21:18:08 +07:00
|
|
|
pch_post_disable_crt(encoder, old_crtc_state, old_conn_state);
|
|
|
|
|
|
|
|
lpt_disable_pch_transcoder(dev_priv);
|
|
|
|
lpt_disable_iclkip(dev_priv);
|
|
|
|
|
|
|
|
intel_ddi_fdi_post_disable(encoder, old_crtc_state, old_conn_state);
|
2017-10-05 17:52:11 +07:00
|
|
|
|
|
|
|
WARN_ON(!old_crtc_state->has_pch_encoder);
|
|
|
|
|
|
|
|
intel_set_pch_fifo_underrun_reporting(dev_priv, PIPE_A, true);
|
2016-08-23 21:18:08 +07:00
|
|
|
}
|
|
|
|
|
2017-10-05 17:52:10 +07:00
|
|
|
static void hsw_pre_pll_enable_crt(struct intel_encoder *encoder,
|
2017-11-01 03:51:19 +07:00
|
|
|
const struct intel_crtc_state *crtc_state,
|
2017-10-05 17:52:10 +07:00
|
|
|
const struct drm_connector_state *conn_state)
|
|
|
|
{
|
2017-11-01 03:51:19 +07:00
|
|
|
struct drm_i915_private *dev_priv = to_i915(encoder->base.dev);
|
2017-10-05 17:52:10 +07:00
|
|
|
|
2017-11-01 03:51:19 +07:00
|
|
|
WARN_ON(!crtc_state->has_pch_encoder);
|
2017-10-05 17:52:10 +07:00
|
|
|
|
|
|
|
intel_set_pch_fifo_underrun_reporting(dev_priv, PIPE_A, false);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void hsw_pre_enable_crt(struct intel_encoder *encoder,
|
2017-11-01 03:51:19 +07:00
|
|
|
const struct intel_crtc_state *crtc_state,
|
2017-10-05 17:52:10 +07:00
|
|
|
const struct drm_connector_state *conn_state)
|
|
|
|
{
|
2017-11-01 03:51:19 +07:00
|
|
|
struct drm_i915_private *dev_priv = to_i915(encoder->base.dev);
|
|
|
|
struct intel_crtc *crtc = to_intel_crtc(crtc_state->base.crtc);
|
|
|
|
enum pipe pipe = crtc->pipe;
|
2017-10-05 17:52:10 +07:00
|
|
|
|
2017-11-01 03:51:19 +07:00
|
|
|
WARN_ON(!crtc_state->has_pch_encoder);
|
2017-10-05 17:52:10 +07:00
|
|
|
|
|
|
|
intel_set_cpu_fifo_underrun_reporting(dev_priv, pipe, false);
|
2017-10-05 17:52:13 +07:00
|
|
|
|
2017-11-01 03:51:19 +07:00
|
|
|
dev_priv->display.fdi_link_train(crtc, crtc_state);
|
2018-06-14 00:27:46 +07:00
|
|
|
|
|
|
|
intel_ddi_enable_pipe_clock(crtc_state);
|
2017-10-05 17:52:10 +07:00
|
|
|
}
|
|
|
|
|
|
|
|
static void hsw_enable_crt(struct intel_encoder *encoder,
|
2017-11-01 03:51:19 +07:00
|
|
|
const struct intel_crtc_state *crtc_state,
|
2017-10-05 17:52:10 +07:00
|
|
|
const struct drm_connector_state *conn_state)
|
|
|
|
{
|
2017-11-01 03:51:19 +07:00
|
|
|
struct drm_i915_private *dev_priv = to_i915(encoder->base.dev);
|
|
|
|
struct intel_crtc *crtc = to_intel_crtc(crtc_state->base.crtc);
|
|
|
|
enum pipe pipe = crtc->pipe;
|
2017-10-05 17:52:10 +07:00
|
|
|
|
2017-11-01 03:51:19 +07:00
|
|
|
WARN_ON(!crtc_state->has_pch_encoder);
|
2017-10-05 17:52:10 +07:00
|
|
|
|
2017-11-01 03:51:19 +07:00
|
|
|
intel_crt_set_dpms(encoder, crtc_state, DRM_MODE_DPMS_ON);
|
2017-10-05 17:52:10 +07:00
|
|
|
|
|
|
|
intel_wait_for_vblank(dev_priv, pipe);
|
|
|
|
intel_wait_for_vblank(dev_priv, pipe);
|
|
|
|
intel_set_cpu_fifo_underrun_reporting(dev_priv, pipe, true);
|
|
|
|
intel_set_pch_fifo_underrun_reporting(dev_priv, PIPE_A, true);
|
|
|
|
}
|
|
|
|
|
2016-08-09 22:04:04 +07:00
|
|
|
static void intel_enable_crt(struct intel_encoder *encoder,
|
2017-11-01 03:51:19 +07:00
|
|
|
const struct intel_crtc_state *crtc_state,
|
2017-08-18 20:49:58 +07:00
|
|
|
const struct drm_connector_state *conn_state)
|
2013-03-26 02:40:05 +07:00
|
|
|
{
|
2017-11-01 03:51:19 +07:00
|
|
|
intel_crt_set_dpms(encoder, crtc_state, DRM_MODE_DPMS_ON);
|
2013-03-26 02:40:05 +07:00
|
|
|
}
|
|
|
|
|
2013-11-28 22:29:18 +07:00
|
|
|
static enum drm_mode_status
|
|
|
|
intel_crt_mode_valid(struct drm_connector *connector,
|
|
|
|
struct drm_display_mode *mode)
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
{
|
2009-03-03 17:06:42 +07:00
|
|
|
struct drm_device *dev = connector->dev;
|
2016-10-13 17:02:53 +07:00
|
|
|
struct drm_i915_private *dev_priv = to_i915(dev);
|
|
|
|
int max_dotclk = dev_priv->max_dotclk_freq;
|
2016-02-18 02:41:13 +07:00
|
|
|
int max_clock;
|
2009-03-03 17:06:42 +07:00
|
|
|
|
2018-05-24 19:54:03 +07:00
|
|
|
if (mode->flags & DRM_MODE_FLAG_DBLSCAN)
|
|
|
|
return MODE_NO_DBLESCAN;
|
|
|
|
|
2009-03-03 17:06:42 +07:00
|
|
|
if (mode->clock < 25000)
|
|
|
|
return MODE_CLOCK_LOW;
|
|
|
|
|
2016-10-13 17:02:53 +07:00
|
|
|
if (HAS_PCH_LPT(dev_priv))
|
2016-02-18 02:41:13 +07:00
|
|
|
max_clock = 180000;
|
2016-10-13 17:03:08 +07:00
|
|
|
else if (IS_VALLEYVIEW(dev_priv))
|
2016-02-18 02:41:13 +07:00
|
|
|
/*
|
|
|
|
* 270 MHz due to current DPLL limits,
|
|
|
|
* DAC limit supposedly 355 MHz.
|
|
|
|
*/
|
|
|
|
max_clock = 270000;
|
2016-10-13 17:03:10 +07:00
|
|
|
else if (IS_GEN3(dev_priv) || IS_GEN4(dev_priv))
|
2009-03-03 17:06:42 +07:00
|
|
|
max_clock = 400000;
|
2016-02-18 02:41:13 +07:00
|
|
|
else
|
|
|
|
max_clock = 350000;
|
2009-03-03 17:06:42 +07:00
|
|
|
if (mode->clock > max_clock)
|
|
|
|
return MODE_CLOCK_HIGH;
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
|
2016-02-02 20:16:42 +07:00
|
|
|
if (mode->clock > max_dotclk)
|
|
|
|
return MODE_CLOCK_HIGH;
|
|
|
|
|
2012-11-29 20:29:32 +07:00
|
|
|
/* The FDI receiver on LPT only supports 8bpc and only has 2 lanes. */
|
2016-10-13 17:02:53 +07:00
|
|
|
if (HAS_PCH_LPT(dev_priv) &&
|
2012-11-29 20:29:32 +07:00
|
|
|
(ironlake_get_lanes_required(mode->clock, 270000, 24) > 2))
|
|
|
|
return MODE_CLOCK_HIGH;
|
|
|
|
|
2018-06-16 00:44:06 +07:00
|
|
|
/* HSW/BDW FDI limited to 4k */
|
|
|
|
if (mode->hdisplay > 4096)
|
|
|
|
return MODE_H_ILLEGAL;
|
|
|
|
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
return MODE_OK;
|
|
|
|
}
|
|
|
|
|
2013-03-27 06:44:55 +07:00
|
|
|
static bool intel_crt_compute_config(struct intel_encoder *encoder,
|
2016-08-09 22:04:05 +07:00
|
|
|
struct intel_crtc_state *pipe_config,
|
|
|
|
struct drm_connector_state *conn_state)
|
2017-10-17 21:03:13 +07:00
|
|
|
{
|
2018-05-24 19:54:03 +07:00
|
|
|
struct drm_display_mode *adjusted_mode =
|
|
|
|
&pipe_config->base.adjusted_mode;
|
|
|
|
|
|
|
|
if (adjusted_mode->flags & DRM_MODE_FLAG_DBLSCAN)
|
|
|
|
return false;
|
|
|
|
|
2017-10-17 21:03:13 +07:00
|
|
|
return true;
|
|
|
|
}
|
|
|
|
|
|
|
|
static bool pch_crt_compute_config(struct intel_encoder *encoder,
|
|
|
|
struct intel_crtc_state *pipe_config,
|
|
|
|
struct drm_connector_state *conn_state)
|
|
|
|
{
|
2018-05-24 19:54:03 +07:00
|
|
|
struct drm_display_mode *adjusted_mode =
|
|
|
|
&pipe_config->base.adjusted_mode;
|
|
|
|
|
|
|
|
if (adjusted_mode->flags & DRM_MODE_FLAG_DBLSCAN)
|
|
|
|
return false;
|
|
|
|
|
2017-10-17 21:03:13 +07:00
|
|
|
pipe_config->has_pch_encoder = true;
|
|
|
|
|
|
|
|
return true;
|
|
|
|
}
|
|
|
|
|
|
|
|
static bool hsw_crt_compute_config(struct intel_encoder *encoder,
|
|
|
|
struct intel_crtc_state *pipe_config,
|
|
|
|
struct drm_connector_state *conn_state)
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
{
|
2016-10-13 17:02:52 +07:00
|
|
|
struct drm_i915_private *dev_priv = to_i915(encoder->base.dev);
|
2018-05-24 19:54:03 +07:00
|
|
|
struct drm_display_mode *adjusted_mode =
|
|
|
|
&pipe_config->base.adjusted_mode;
|
|
|
|
|
|
|
|
if (adjusted_mode->flags & DRM_MODE_FLAG_DBLSCAN)
|
|
|
|
return false;
|
2013-03-27 06:44:55 +07:00
|
|
|
|
2018-06-16 00:44:06 +07:00
|
|
|
/* HSW/BDW FDI limited to 4k */
|
|
|
|
if (adjusted_mode->crtc_hdisplay > 4096 ||
|
|
|
|
adjusted_mode->crtc_hblank_start > 4096)
|
|
|
|
return false;
|
|
|
|
|
2017-10-17 21:03:13 +07:00
|
|
|
pipe_config->has_pch_encoder = true;
|
2013-03-27 06:44:55 +07:00
|
|
|
|
2013-04-19 16:24:39 +07:00
|
|
|
/* LPT FDI RX only supports 8bpc. */
|
2016-10-13 17:02:52 +07:00
|
|
|
if (HAS_PCH_LPT(dev_priv)) {
|
2016-05-03 15:33:01 +07:00
|
|
|
if (pipe_config->bw_constrained && pipe_config->pipe_bpp < 24) {
|
|
|
|
DRM_DEBUG_KMS("LPT only supports 24bpp\n");
|
|
|
|
return false;
|
|
|
|
}
|
|
|
|
|
2013-04-19 16:24:39 +07:00
|
|
|
pipe_config->pipe_bpp = 24;
|
2016-05-03 15:33:01 +07:00
|
|
|
}
|
2013-04-19 16:24:39 +07:00
|
|
|
|
2014-02-27 19:23:12 +07:00
|
|
|
/* FDI must always be 2.7 GHz */
|
2017-10-17 21:03:13 +07:00
|
|
|
pipe_config->port_clock = 135000 * 2;
|
2015-11-16 20:42:12 +07:00
|
|
|
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
return true;
|
|
|
|
}
|
|
|
|
|
2009-12-04 05:14:42 +07:00
|
|
|
static bool intel_ironlake_crt_detect_hotplug(struct drm_connector *connector)
|
2009-06-05 14:38:42 +07:00
|
|
|
{
|
|
|
|
struct drm_device *dev = connector->dev;
|
2010-11-16 15:03:53 +07:00
|
|
|
struct intel_crt *crt = intel_attached_crt(connector);
|
2016-07-04 17:34:36 +07:00
|
|
|
struct drm_i915_private *dev_priv = to_i915(dev);
|
2010-11-16 15:03:53 +07:00
|
|
|
u32 adpa;
|
2009-06-05 14:38:42 +07:00
|
|
|
bool ret;
|
|
|
|
|
2010-11-16 15:03:53 +07:00
|
|
|
/* The first time through, trigger an explicit detection cycle */
|
|
|
|
if (crt->force_hotplug_required) {
|
2016-10-13 17:02:53 +07:00
|
|
|
bool turn_off_dac = HAS_PCH_SPLIT(dev_priv);
|
2010-11-16 15:03:53 +07:00
|
|
|
u32 save_adpa;
|
2009-07-24 00:00:33 +07:00
|
|
|
|
2010-11-16 15:03:53 +07:00
|
|
|
crt->force_hotplug_required = 0;
|
|
|
|
|
2013-01-26 02:44:42 +07:00
|
|
|
save_adpa = adpa = I915_READ(crt->adpa_reg);
|
2010-11-16 15:03:53 +07:00
|
|
|
DRM_DEBUG_KMS("trigger hotplug detect cycle: adpa=0x%x\n", adpa);
|
|
|
|
|
|
|
|
adpa |= ADPA_CRT_HOTPLUG_FORCE_TRIGGER;
|
|
|
|
if (turn_off_dac)
|
|
|
|
adpa &= ~ADPA_DAC_ENABLE;
|
|
|
|
|
2013-01-26 02:44:42 +07:00
|
|
|
I915_WRITE(crt->adpa_reg, adpa);
|
2010-11-16 15:03:53 +07:00
|
|
|
|
2016-06-30 21:32:49 +07:00
|
|
|
if (intel_wait_for_register(dev_priv,
|
|
|
|
crt->adpa_reg,
|
|
|
|
ADPA_CRT_HOTPLUG_FORCE_TRIGGER, 0,
|
|
|
|
1000))
|
2010-11-16 15:03:53 +07:00
|
|
|
DRM_DEBUG_KMS("timed out waiting for FORCE_TRIGGER");
|
|
|
|
|
|
|
|
if (turn_off_dac) {
|
2013-01-26 02:44:42 +07:00
|
|
|
I915_WRITE(crt->adpa_reg, save_adpa);
|
|
|
|
POSTING_READ(crt->adpa_reg);
|
2010-11-16 15:03:53 +07:00
|
|
|
}
|
2010-04-07 15:15:55 +07:00
|
|
|
}
|
|
|
|
|
2009-06-05 14:38:42 +07:00
|
|
|
/* Check the status to see if both blue and green are on now */
|
2013-01-26 02:44:42 +07:00
|
|
|
adpa = I915_READ(crt->adpa_reg);
|
2010-11-16 15:03:53 +07:00
|
|
|
if ((adpa & ADPA_CRT_HOTPLUG_MONITOR_MASK) != 0)
|
2009-06-05 14:38:42 +07:00
|
|
|
ret = true;
|
|
|
|
else
|
|
|
|
ret = false;
|
2010-11-16 15:03:53 +07:00
|
|
|
DRM_DEBUG_KMS("ironlake hotplug adpa=0x%x, result %d\n", adpa, ret);
|
2009-06-05 14:38:42 +07:00
|
|
|
|
|
|
|
return ret;
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
}
|
|
|
|
|
2012-06-16 01:55:15 +07:00
|
|
|
static bool valleyview_crt_detect_hotplug(struct drm_connector *connector)
|
|
|
|
{
|
|
|
|
struct drm_device *dev = connector->dev;
|
2013-01-26 02:44:42 +07:00
|
|
|
struct intel_crt *crt = intel_attached_crt(connector);
|
2016-07-04 17:34:36 +07:00
|
|
|
struct drm_i915_private *dev_priv = to_i915(dev);
|
2016-06-22 04:03:43 +07:00
|
|
|
bool reenable_hpd;
|
2012-06-16 01:55:15 +07:00
|
|
|
u32 adpa;
|
|
|
|
bool ret;
|
|
|
|
u32 save_adpa;
|
|
|
|
|
2016-06-22 04:03:43 +07:00
|
|
|
/*
|
|
|
|
* Doing a force trigger causes a hpd interrupt to get sent, which can
|
|
|
|
* get us stuck in a loop if we're polling:
|
|
|
|
* - We enable power wells and reset the ADPA
|
|
|
|
* - output_poll_exec does force probe on VGA, triggering a hpd
|
|
|
|
* - HPD handler waits for poll to unlock dev->mode_config.mutex
|
|
|
|
* - output_poll_exec shuts off the ADPA, unlocks
|
|
|
|
* dev->mode_config.mutex
|
|
|
|
* - HPD handler runs, resets ADPA and brings us back to the start
|
|
|
|
*
|
|
|
|
* Just disable HPD interrupts here to prevent this
|
|
|
|
*/
|
|
|
|
reenable_hpd = intel_hpd_disable(dev_priv, crt->base.hpd_pin);
|
|
|
|
|
2013-01-26 02:44:42 +07:00
|
|
|
save_adpa = adpa = I915_READ(crt->adpa_reg);
|
2012-06-16 01:55:15 +07:00
|
|
|
DRM_DEBUG_KMS("trigger hotplug detect cycle: adpa=0x%x\n", adpa);
|
|
|
|
|
|
|
|
adpa |= ADPA_CRT_HOTPLUG_FORCE_TRIGGER;
|
|
|
|
|
2013-01-26 02:44:42 +07:00
|
|
|
I915_WRITE(crt->adpa_reg, adpa);
|
2012-06-16 01:55:15 +07:00
|
|
|
|
2016-06-30 21:32:50 +07:00
|
|
|
if (intel_wait_for_register(dev_priv,
|
|
|
|
crt->adpa_reg,
|
|
|
|
ADPA_CRT_HOTPLUG_FORCE_TRIGGER, 0,
|
|
|
|
1000)) {
|
2012-06-16 01:55:15 +07:00
|
|
|
DRM_DEBUG_KMS("timed out waiting for FORCE_TRIGGER");
|
2013-01-26 02:44:42 +07:00
|
|
|
I915_WRITE(crt->adpa_reg, save_adpa);
|
2012-06-16 01:55:15 +07:00
|
|
|
}
|
|
|
|
|
|
|
|
/* Check the status to see if both blue and green are on now */
|
2013-01-26 02:44:42 +07:00
|
|
|
adpa = I915_READ(crt->adpa_reg);
|
2012-06-16 01:55:15 +07:00
|
|
|
if ((adpa & ADPA_CRT_HOTPLUG_MONITOR_MASK) != 0)
|
|
|
|
ret = true;
|
|
|
|
else
|
|
|
|
ret = false;
|
|
|
|
|
|
|
|
DRM_DEBUG_KMS("valleyview hotplug adpa=0x%x, result %d\n", adpa, ret);
|
|
|
|
|
2016-06-22 04:03:43 +07:00
|
|
|
if (reenable_hpd)
|
|
|
|
intel_hpd_enable(dev_priv, crt->base.hpd_pin);
|
|
|
|
|
2012-06-16 01:55:15 +07:00
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
static bool intel_crt_detect_hotplug(struct drm_connector *connector)
|
|
|
|
{
|
|
|
|
struct drm_device *dev = connector->dev;
|
2016-07-04 17:34:36 +07:00
|
|
|
struct drm_i915_private *dev_priv = to_i915(dev);
|
2015-09-23 21:15:27 +07:00
|
|
|
u32 stat;
|
2010-05-25 03:46:29 +07:00
|
|
|
bool ret = false;
|
2009-03-03 17:07:52 +07:00
|
|
|
int i, tries = 0;
|
2009-06-05 14:38:42 +07:00
|
|
|
|
2016-10-13 17:02:53 +07:00
|
|
|
if (HAS_PCH_SPLIT(dev_priv))
|
2009-12-04 05:14:42 +07:00
|
|
|
return intel_ironlake_crt_detect_hotplug(connector);
|
2009-06-05 14:38:42 +07:00
|
|
|
|
2016-10-13 17:03:08 +07:00
|
|
|
if (IS_VALLEYVIEW(dev_priv))
|
2012-06-16 01:55:15 +07:00
|
|
|
return valleyview_crt_detect_hotplug(connector);
|
|
|
|
|
2009-03-03 17:07:52 +07:00
|
|
|
/*
|
|
|
|
* On 4 series desktop, CRT detect sequence need to be done twice
|
|
|
|
* to get a reliable result.
|
|
|
|
*/
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
|
2018-06-15 01:05:00 +07:00
|
|
|
if (IS_G45(dev_priv))
|
2009-03-03 17:07:52 +07:00
|
|
|
tries = 2;
|
|
|
|
else
|
|
|
|
tries = 1;
|
|
|
|
|
|
|
|
for (i = 0; i < tries ; i++) {
|
|
|
|
/* turn on the FORCE_DETECT */
|
2015-09-23 21:15:27 +07:00
|
|
|
i915_hotplug_interrupt_update(dev_priv,
|
|
|
|
CRT_HOTPLUG_FORCE_DETECT,
|
|
|
|
CRT_HOTPLUG_FORCE_DETECT);
|
2009-03-03 17:07:52 +07:00
|
|
|
/* wait for FORCE_DETECT to go off */
|
2016-06-30 21:32:51 +07:00
|
|
|
if (intel_wait_for_register(dev_priv, PORT_HOTPLUG_EN,
|
|
|
|
CRT_HOTPLUG_FORCE_DETECT, 0,
|
|
|
|
1000))
|
2010-09-13 01:58:04 +07:00
|
|
|
DRM_DEBUG_KMS("timed out waiting for FORCE_DETECT to go off");
|
2009-03-03 17:07:52 +07:00
|
|
|
}
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
|
2010-05-25 03:46:29 +07:00
|
|
|
stat = I915_READ(PORT_HOTPLUG_STAT);
|
|
|
|
if ((stat & CRT_HOTPLUG_MONITOR_MASK) != CRT_HOTPLUG_MONITOR_NONE)
|
|
|
|
ret = true;
|
|
|
|
|
|
|
|
/* clear the interrupt we just generated, if any */
|
|
|
|
I915_WRITE(PORT_HOTPLUG_STAT, CRT_HOTPLUG_INT_STATUS);
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
|
2015-09-23 21:15:27 +07:00
|
|
|
i915_hotplug_interrupt_update(dev_priv, CRT_HOTPLUG_FORCE_DETECT, 0);
|
2010-05-25 03:46:29 +07:00
|
|
|
|
|
|
|
return ret;
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
}
|
|
|
|
|
2012-08-13 17:22:35 +07:00
|
|
|
static struct edid *intel_crt_get_edid(struct drm_connector *connector,
|
|
|
|
struct i2c_adapter *i2c)
|
|
|
|
{
|
|
|
|
struct edid *edid;
|
|
|
|
|
|
|
|
edid = drm_get_edid(connector, i2c);
|
|
|
|
|
|
|
|
if (!edid && !intel_gmbus_is_forced_bit(i2c)) {
|
|
|
|
DRM_DEBUG_KMS("CRT GMBUS EDID read failed, retry using GPIO bit-banging\n");
|
|
|
|
intel_gmbus_force_bit(i2c, true);
|
|
|
|
edid = drm_get_edid(connector, i2c);
|
|
|
|
intel_gmbus_force_bit(i2c, false);
|
|
|
|
}
|
|
|
|
|
|
|
|
return edid;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* local version of intel_ddc_get_modes() to use intel_crt_get_edid() */
|
|
|
|
static int intel_crt_ddc_get_modes(struct drm_connector *connector,
|
|
|
|
struct i2c_adapter *adapter)
|
|
|
|
{
|
|
|
|
struct edid *edid;
|
2012-10-19 18:51:51 +07:00
|
|
|
int ret;
|
2012-08-13 17:22:35 +07:00
|
|
|
|
|
|
|
edid = intel_crt_get_edid(connector, adapter);
|
|
|
|
if (!edid)
|
|
|
|
return 0;
|
|
|
|
|
2012-10-19 18:51:51 +07:00
|
|
|
ret = intel_connector_update_modes(connector, edid);
|
|
|
|
kfree(edid);
|
|
|
|
|
|
|
|
return ret;
|
2012-08-13 17:22:35 +07:00
|
|
|
}
|
|
|
|
|
2011-01-06 19:29:32 +07:00
|
|
|
static bool intel_crt_detect_ddc(struct drm_connector *connector)
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
{
|
2011-01-06 19:29:32 +07:00
|
|
|
struct intel_crt *crt = intel_attached_crt(connector);
|
2016-07-04 17:34:36 +07:00
|
|
|
struct drm_i915_private *dev_priv = to_i915(crt->base.base.dev);
|
2012-07-11 17:31:52 +07:00
|
|
|
struct edid *edid;
|
|
|
|
struct i2c_adapter *i2c;
|
2017-01-20 21:28:42 +07:00
|
|
|
bool ret = false;
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
|
2012-07-11 17:31:52 +07:00
|
|
|
BUG_ON(crt->base.type != INTEL_OUTPUT_ANALOG);
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
|
2013-05-10 06:03:18 +07:00
|
|
|
i2c = intel_gmbus_get_adapter(dev_priv, dev_priv->vbt.crt_ddc_pin);
|
2012-08-13 17:22:35 +07:00
|
|
|
edid = intel_crt_get_edid(connector, i2c);
|
2012-07-11 17:31:52 +07:00
|
|
|
|
|
|
|
if (edid) {
|
|
|
|
bool is_digital = edid->input & DRM_EDID_INPUT_DIGITAL;
|
2011-01-06 19:29:32 +07:00
|
|
|
|
|
|
|
/*
|
|
|
|
* This may be a DVI-I connector with a shared DDC
|
|
|
|
* link between analog and digital outputs, so we
|
|
|
|
* have to check the EDID input spec of the attached device.
|
|
|
|
*/
|
|
|
|
if (!is_digital) {
|
|
|
|
DRM_DEBUG_KMS("CRT detected via DDC:0x50 [EDID]\n");
|
2017-01-20 21:28:42 +07:00
|
|
|
ret = true;
|
|
|
|
} else {
|
|
|
|
DRM_DEBUG_KMS("CRT not detected via DDC:0x50 [EDID reports a digital panel]\n");
|
2011-01-06 19:29:32 +07:00
|
|
|
}
|
2012-07-11 17:31:52 +07:00
|
|
|
} else {
|
|
|
|
DRM_DEBUG_KMS("CRT not detected via DDC:0x50 [no valid EDID found]\n");
|
2010-09-23 00:17:01 +07:00
|
|
|
}
|
|
|
|
|
2012-07-11 17:31:52 +07:00
|
|
|
kfree(edid);
|
|
|
|
|
2017-01-20 21:28:42 +07:00
|
|
|
return ret;
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
}
|
|
|
|
|
2009-05-26 10:31:00 +07:00
|
|
|
static enum drm_connector_status
|
2016-02-17 15:18:36 +07:00
|
|
|
intel_crt_load_detect(struct intel_crt *crt, uint32_t pipe)
|
2009-05-26 10:31:00 +07:00
|
|
|
{
|
2011-04-20 05:10:58 +07:00
|
|
|
struct drm_device *dev = crt->base.base.dev;
|
2016-07-04 17:34:36 +07:00
|
|
|
struct drm_i915_private *dev_priv = to_i915(dev);
|
2009-05-26 10:31:00 +07:00
|
|
|
uint32_t save_bclrpat;
|
|
|
|
uint32_t save_vtotal;
|
|
|
|
uint32_t vtotal, vactive;
|
|
|
|
uint32_t vsample;
|
|
|
|
uint32_t vblank, vblank_start, vblank_end;
|
|
|
|
uint32_t dsl;
|
drm/i915: Type safe register read/write
Make I915_READ and I915_WRITE more type safe by wrapping the register
offset in a struct. This should eliminate most of the fumbles we've had
with misplaced parens.
This only takes care of normal mmio registers. We could extend the idea
to other register types and define each with its own struct. That way
you wouldn't be able to accidentally pass the wrong thing to a specific
register access function.
The gpio_reg setup is probably the ugliest thing left. But I figure I'd
just leave it for now, and wait for some divine inspiration to strike
before making it nice.
As for the generated code, it's actually a bit better sometimes. Eg.
looking at i915_irq_handler(), we can see the following change:
lea 0x70024(%rdx,%rax,1),%r9d
mov $0x1,%edx
- movslq %r9d,%r9
- mov %r9,%rsi
- mov %r9,-0x58(%rbp)
- callq *0xd8(%rbx)
+ mov %r9d,%esi
+ mov %r9d,-0x48(%rbp)
callq *0xd8(%rbx)
So previously gcc thought the register offset might be signed and
decided to sign extend it, just in case. The rest appears to be
mostly just minor shuffling of instructions.
v2: i915_mmio_reg_{offset,equal,valid}() helpers added
s/_REG/_MMIO/ in the register defines
mo more switch statements left to worry about
ring_emit stuff got sorted in a prep patch
cmd parser, lrc context and w/a batch buildup also in prep patch
vgpu stuff cleaned up and moved to a prep patch
all other unrelated changes split out
v3: Rebased due to BXT DSI/BLC, MOCS, etc.
v4: Rebased due to churn, s/i915_mmio_reg_t/i915_reg_t/
Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Link: http://patchwork.freedesktop.org/patch/msgid/1447853606-2751-1-git-send-email-ville.syrjala@linux.intel.com
2015-11-18 20:33:26 +07:00
|
|
|
i915_reg_t bclrpat_reg, vtotal_reg,
|
|
|
|
vblank_reg, vsync_reg, pipeconf_reg, pipe_dsl_reg;
|
2009-05-26 10:31:00 +07:00
|
|
|
uint8_t st00;
|
|
|
|
enum drm_connector_status status;
|
|
|
|
|
2010-09-23 00:17:01 +07:00
|
|
|
DRM_DEBUG_KMS("starting load-detect on CRT\n");
|
|
|
|
|
2011-02-08 03:26:52 +07:00
|
|
|
bclrpat_reg = BCLRPAT(pipe);
|
|
|
|
vtotal_reg = VTOTAL(pipe);
|
|
|
|
vblank_reg = VBLANK(pipe);
|
|
|
|
vsync_reg = VSYNC(pipe);
|
|
|
|
pipeconf_reg = PIPECONF(pipe);
|
|
|
|
pipe_dsl_reg = PIPEDSL(pipe);
|
2009-05-26 10:31:00 +07:00
|
|
|
|
|
|
|
save_bclrpat = I915_READ(bclrpat_reg);
|
|
|
|
save_vtotal = I915_READ(vtotal_reg);
|
|
|
|
vblank = I915_READ(vblank_reg);
|
|
|
|
|
|
|
|
vtotal = ((save_vtotal >> 16) & 0xfff) + 1;
|
|
|
|
vactive = (save_vtotal & 0x7ff) + 1;
|
|
|
|
|
|
|
|
vblank_start = (vblank & 0xfff) + 1;
|
|
|
|
vblank_end = ((vblank >> 16) & 0xfff) + 1;
|
|
|
|
|
|
|
|
/* Set the border color to purple. */
|
|
|
|
I915_WRITE(bclrpat_reg, 0x500050);
|
|
|
|
|
2016-10-13 17:03:10 +07:00
|
|
|
if (!IS_GEN2(dev_priv)) {
|
2009-05-26 10:31:00 +07:00
|
|
|
uint32_t pipeconf = I915_READ(pipeconf_reg);
|
|
|
|
I915_WRITE(pipeconf_reg, pipeconf | PIPECONF_FORCE_BORDER);
|
2010-08-09 20:50:53 +07:00
|
|
|
POSTING_READ(pipeconf_reg);
|
2009-05-26 10:31:00 +07:00
|
|
|
/* Wait for next Vblank to substitue
|
|
|
|
* border color for Color info */
|
2016-11-01 03:37:06 +07:00
|
|
|
intel_wait_for_vblank(dev_priv, pipe);
|
drm/i915: Type safe register read/write
Make I915_READ and I915_WRITE more type safe by wrapping the register
offset in a struct. This should eliminate most of the fumbles we've had
with misplaced parens.
This only takes care of normal mmio registers. We could extend the idea
to other register types and define each with its own struct. That way
you wouldn't be able to accidentally pass the wrong thing to a specific
register access function.
The gpio_reg setup is probably the ugliest thing left. But I figure I'd
just leave it for now, and wait for some divine inspiration to strike
before making it nice.
As for the generated code, it's actually a bit better sometimes. Eg.
looking at i915_irq_handler(), we can see the following change:
lea 0x70024(%rdx,%rax,1),%r9d
mov $0x1,%edx
- movslq %r9d,%r9
- mov %r9,%rsi
- mov %r9,-0x58(%rbp)
- callq *0xd8(%rbx)
+ mov %r9d,%esi
+ mov %r9d,-0x48(%rbp)
callq *0xd8(%rbx)
So previously gcc thought the register offset might be signed and
decided to sign extend it, just in case. The rest appears to be
mostly just minor shuffling of instructions.
v2: i915_mmio_reg_{offset,equal,valid}() helpers added
s/_REG/_MMIO/ in the register defines
mo more switch statements left to worry about
ring_emit stuff got sorted in a prep patch
cmd parser, lrc context and w/a batch buildup also in prep patch
vgpu stuff cleaned up and moved to a prep patch
all other unrelated changes split out
v3: Rebased due to BXT DSI/BLC, MOCS, etc.
v4: Rebased due to churn, s/i915_mmio_reg_t/i915_reg_t/
Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Link: http://patchwork.freedesktop.org/patch/msgid/1447853606-2751-1-git-send-email-ville.syrjala@linux.intel.com
2015-11-18 20:33:26 +07:00
|
|
|
st00 = I915_READ8(_VGA_MSR_WRITE);
|
2009-05-26 10:31:00 +07:00
|
|
|
status = ((st00 & (1 << 4)) != 0) ?
|
|
|
|
connector_status_connected :
|
|
|
|
connector_status_disconnected;
|
|
|
|
|
|
|
|
I915_WRITE(pipeconf_reg, pipeconf);
|
|
|
|
} else {
|
|
|
|
bool restore_vblank = false;
|
|
|
|
int count, detect;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* If there isn't any border, add some.
|
|
|
|
* Yes, this will flicker
|
|
|
|
*/
|
|
|
|
if (vblank_start <= vactive && vblank_end >= vtotal) {
|
|
|
|
uint32_t vsync = I915_READ(vsync_reg);
|
|
|
|
uint32_t vsync_start = (vsync & 0xffff) + 1;
|
|
|
|
|
|
|
|
vblank_start = vsync_start;
|
|
|
|
I915_WRITE(vblank_reg,
|
|
|
|
(vblank_start - 1) |
|
|
|
|
((vblank_end - 1) << 16));
|
|
|
|
restore_vblank = true;
|
|
|
|
}
|
|
|
|
/* sample in the vertical border, selecting the larger one */
|
|
|
|
if (vblank_start - vactive >= vtotal - vblank_end)
|
|
|
|
vsample = (vblank_start + vactive) >> 1;
|
|
|
|
else
|
|
|
|
vsample = (vtotal + vblank_end) >> 1;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Wait for the border to be displayed
|
|
|
|
*/
|
|
|
|
while (I915_READ(pipe_dsl_reg) >= vactive)
|
|
|
|
;
|
|
|
|
while ((dsl = I915_READ(pipe_dsl_reg)) <= vsample)
|
|
|
|
;
|
|
|
|
/*
|
|
|
|
* Watch ST00 for an entire scanline
|
|
|
|
*/
|
|
|
|
detect = 0;
|
|
|
|
count = 0;
|
|
|
|
do {
|
|
|
|
count++;
|
|
|
|
/* Read the ST00 VGA status register */
|
drm/i915: Type safe register read/write
Make I915_READ and I915_WRITE more type safe by wrapping the register
offset in a struct. This should eliminate most of the fumbles we've had
with misplaced parens.
This only takes care of normal mmio registers. We could extend the idea
to other register types and define each with its own struct. That way
you wouldn't be able to accidentally pass the wrong thing to a specific
register access function.
The gpio_reg setup is probably the ugliest thing left. But I figure I'd
just leave it for now, and wait for some divine inspiration to strike
before making it nice.
As for the generated code, it's actually a bit better sometimes. Eg.
looking at i915_irq_handler(), we can see the following change:
lea 0x70024(%rdx,%rax,1),%r9d
mov $0x1,%edx
- movslq %r9d,%r9
- mov %r9,%rsi
- mov %r9,-0x58(%rbp)
- callq *0xd8(%rbx)
+ mov %r9d,%esi
+ mov %r9d,-0x48(%rbp)
callq *0xd8(%rbx)
So previously gcc thought the register offset might be signed and
decided to sign extend it, just in case. The rest appears to be
mostly just minor shuffling of instructions.
v2: i915_mmio_reg_{offset,equal,valid}() helpers added
s/_REG/_MMIO/ in the register defines
mo more switch statements left to worry about
ring_emit stuff got sorted in a prep patch
cmd parser, lrc context and w/a batch buildup also in prep patch
vgpu stuff cleaned up and moved to a prep patch
all other unrelated changes split out
v3: Rebased due to BXT DSI/BLC, MOCS, etc.
v4: Rebased due to churn, s/i915_mmio_reg_t/i915_reg_t/
Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Link: http://patchwork.freedesktop.org/patch/msgid/1447853606-2751-1-git-send-email-ville.syrjala@linux.intel.com
2015-11-18 20:33:26 +07:00
|
|
|
st00 = I915_READ8(_VGA_MSR_WRITE);
|
2009-05-26 10:31:00 +07:00
|
|
|
if (st00 & (1 << 4))
|
|
|
|
detect++;
|
|
|
|
} while ((I915_READ(pipe_dsl_reg) == dsl));
|
|
|
|
|
|
|
|
/* restore vblank if necessary */
|
|
|
|
if (restore_vblank)
|
|
|
|
I915_WRITE(vblank_reg, vblank);
|
|
|
|
/*
|
|
|
|
* If more than 3/4 of the scanline detected a monitor,
|
|
|
|
* then it is assumed to be present. This works even on i830,
|
|
|
|
* where there isn't any way to force the border color across
|
|
|
|
* the screen
|
|
|
|
*/
|
|
|
|
status = detect * 4 > count * 3 ?
|
|
|
|
connector_status_connected :
|
|
|
|
connector_status_disconnected;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Restore previous settings */
|
|
|
|
I915_WRITE(bclrpat_reg, save_bclrpat);
|
|
|
|
|
|
|
|
return status;
|
|
|
|
}
|
|
|
|
|
2016-09-26 16:20:45 +07:00
|
|
|
static int intel_spurious_crt_detect_dmi_callback(const struct dmi_system_id *id)
|
|
|
|
{
|
|
|
|
DRM_DEBUG_DRIVER("Skipping CRT detection for %s\n", id->ident);
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
static const struct dmi_system_id intel_spurious_crt_detect[] = {
|
|
|
|
{
|
|
|
|
.callback = intel_spurious_crt_detect_dmi_callback,
|
|
|
|
.ident = "ACER ZGB",
|
|
|
|
.matches = {
|
|
|
|
DMI_MATCH(DMI_SYS_VENDOR, "ACER"),
|
|
|
|
DMI_MATCH(DMI_PRODUCT_NAME, "ZGB"),
|
|
|
|
},
|
|
|
|
},
|
2016-09-26 16:20:46 +07:00
|
|
|
{
|
|
|
|
.callback = intel_spurious_crt_detect_dmi_callback,
|
|
|
|
.ident = "Intel DZ77BH-55K",
|
|
|
|
.matches = {
|
|
|
|
DMI_MATCH(DMI_BOARD_VENDOR, "Intel Corporation"),
|
|
|
|
DMI_MATCH(DMI_BOARD_NAME, "DZ77BH-55K"),
|
|
|
|
},
|
|
|
|
},
|
2016-09-26 16:20:45 +07:00
|
|
|
{ }
|
|
|
|
};
|
|
|
|
|
2017-04-07 01:55:20 +07:00
|
|
|
static int
|
|
|
|
intel_crt_detect(struct drm_connector *connector,
|
|
|
|
struct drm_modeset_acquire_ctx *ctx,
|
|
|
|
bool force)
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
{
|
2016-11-16 15:55:40 +07:00
|
|
|
struct drm_i915_private *dev_priv = to_i915(connector->dev);
|
2010-11-16 17:58:37 +07:00
|
|
|
struct intel_crt *crt = intel_attached_crt(connector);
|
2014-03-05 21:20:53 +07:00
|
|
|
struct intel_encoder *intel_encoder = &crt->base;
|
2017-04-07 01:55:20 +07:00
|
|
|
int status, ret;
|
2012-04-21 02:03:36 +07:00
|
|
|
struct intel_load_detect_pipe tmp;
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
|
2013-07-21 02:27:08 +07:00
|
|
|
DRM_DEBUG_KMS("[CONNECTOR:%d:%s] force=%d\n",
|
2014-06-03 18:56:17 +07:00
|
|
|
connector->base.id, connector->name,
|
2013-07-21 02:27:08 +07:00
|
|
|
force);
|
|
|
|
|
2018-03-23 00:41:35 +07:00
|
|
|
if (i915_modparams.load_detect_test) {
|
|
|
|
intel_display_power_get(dev_priv, intel_encoder->power_domain);
|
|
|
|
goto load_detect;
|
|
|
|
}
|
|
|
|
|
2016-09-26 16:20:45 +07:00
|
|
|
/* Skip machines without VGA that falsely report hotplug events */
|
|
|
|
if (dmi_check_system(intel_spurious_crt_detect))
|
|
|
|
return connector_status_disconnected;
|
|
|
|
|
2017-02-22 13:34:27 +07:00
|
|
|
intel_display_power_get(dev_priv, intel_encoder->power_domain);
|
2014-03-05 21:20:53 +07:00
|
|
|
|
2016-11-07 16:29:20 +07:00
|
|
|
if (I915_HAS_HOTPLUG(dev_priv)) {
|
2012-06-16 20:30:32 +07:00
|
|
|
/* We can not rely on the HPD pin always being correctly wired
|
|
|
|
* up, for example many KVM do not pass it through, and so
|
|
|
|
* only trust an assertion that the monitor is connected.
|
|
|
|
*/
|
2010-09-23 00:17:01 +07:00
|
|
|
if (intel_crt_detect_hotplug(connector)) {
|
|
|
|
DRM_DEBUG_KMS("CRT detected via hotplug\n");
|
2014-02-21 23:52:22 +07:00
|
|
|
status = connector_status_connected;
|
|
|
|
goto out;
|
2012-06-16 20:30:32 +07:00
|
|
|
} else
|
2010-11-16 15:03:53 +07:00
|
|
|
DRM_DEBUG_KMS("CRT not detected via hotplug\n");
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
}
|
|
|
|
|
2014-02-21 23:52:22 +07:00
|
|
|
if (intel_crt_detect_ddc(connector)) {
|
|
|
|
status = connector_status_connected;
|
|
|
|
goto out;
|
|
|
|
}
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
|
2012-06-16 20:30:32 +07:00
|
|
|
/* Load detection is broken on HPD capable machines. Whoever wants a
|
|
|
|
* broken monitor (without edid) to work behind a broken kvm (that fails
|
|
|
|
* to have the right resistors for HP detection) needs to fix this up.
|
|
|
|
* For now just bail out. */
|
2018-03-23 00:41:35 +07:00
|
|
|
if (I915_HAS_HOTPLUG(dev_priv)) {
|
2014-02-21 23:52:22 +07:00
|
|
|
status = connector_status_disconnected;
|
|
|
|
goto out;
|
|
|
|
}
|
2012-06-16 20:30:32 +07:00
|
|
|
|
2018-03-23 00:41:35 +07:00
|
|
|
load_detect:
|
2014-02-21 23:52:22 +07:00
|
|
|
if (!force) {
|
|
|
|
status = connector->status;
|
|
|
|
goto out;
|
|
|
|
}
|
2010-09-10 05:51:02 +07:00
|
|
|
|
2009-05-26 10:31:00 +07:00
|
|
|
/* for pre-945g platforms use load detect */
|
2017-04-07 01:55:20 +07:00
|
|
|
ret = intel_get_load_detect_pipe(connector, NULL, &tmp, ctx);
|
|
|
|
if (ret > 0) {
|
2012-04-21 02:03:36 +07:00
|
|
|
if (intel_crt_detect_ddc(connector))
|
|
|
|
status = connector_status_connected;
|
2016-11-16 15:55:40 +07:00
|
|
|
else if (INTEL_GEN(dev_priv) < 4)
|
2016-02-17 15:18:36 +07:00
|
|
|
status = intel_crt_load_detect(crt,
|
|
|
|
to_intel_crtc(connector->state->crtc)->pipe);
|
2017-09-20 02:38:44 +07:00
|
|
|
else if (i915_modparams.load_detect_test)
|
2016-03-01 23:04:01 +07:00
|
|
|
status = connector_status_disconnected;
|
2015-03-04 00:03:47 +07:00
|
|
|
else
|
|
|
|
status = connector_status_unknown;
|
2017-04-07 01:55:20 +07:00
|
|
|
intel_release_load_detect_pipe(connector, &tmp, ctx);
|
2018-02-08 23:39:39 +07:00
|
|
|
} else if (ret == 0) {
|
2012-04-21 02:03:36 +07:00
|
|
|
status = connector_status_unknown;
|
2018-02-08 23:39:39 +07:00
|
|
|
} else {
|
2017-04-07 01:55:20 +07:00
|
|
|
status = ret;
|
2018-02-08 23:39:39 +07:00
|
|
|
}
|
2014-08-11 17:15:35 +07:00
|
|
|
|
2014-02-21 23:52:22 +07:00
|
|
|
out:
|
2017-02-22 13:34:27 +07:00
|
|
|
intel_display_power_put(dev_priv, intel_encoder->power_domain);
|
2009-05-26 10:31:00 +07:00
|
|
|
return status;
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
}
|
|
|
|
|
|
|
|
static void intel_crt_destroy(struct drm_connector *connector)
|
|
|
|
{
|
|
|
|
drm_connector_cleanup(connector);
|
|
|
|
kfree(connector);
|
|
|
|
}
|
|
|
|
|
|
|
|
static int intel_crt_get_modes(struct drm_connector *connector)
|
|
|
|
{
|
2009-06-30 10:35:34 +07:00
|
|
|
struct drm_device *dev = connector->dev;
|
2016-07-04 17:34:36 +07:00
|
|
|
struct drm_i915_private *dev_priv = to_i915(dev);
|
2014-03-05 21:20:53 +07:00
|
|
|
struct intel_crt *crt = intel_attached_crt(connector);
|
|
|
|
struct intel_encoder *intel_encoder = &crt->base;
|
2010-09-14 22:46:59 +07:00
|
|
|
int ret;
|
2012-03-28 01:36:14 +07:00
|
|
|
struct i2c_adapter *i2c;
|
2009-06-30 10:35:34 +07:00
|
|
|
|
2017-02-22 13:34:27 +07:00
|
|
|
intel_display_power_get(dev_priv, intel_encoder->power_domain);
|
2014-03-05 21:20:53 +07:00
|
|
|
|
2013-05-10 06:03:18 +07:00
|
|
|
i2c = intel_gmbus_get_adapter(dev_priv, dev_priv->vbt.crt_ddc_pin);
|
2012-08-13 17:22:35 +07:00
|
|
|
ret = intel_crt_ddc_get_modes(connector, i2c);
|
2016-10-13 17:03:06 +07:00
|
|
|
if (ret || !IS_G4X(dev_priv))
|
2014-03-05 21:20:53 +07:00
|
|
|
goto out;
|
2009-06-30 10:35:34 +07:00
|
|
|
|
|
|
|
/* Try to probe digital port for output in DVI-I -> VGA mode. */
|
2015-03-27 05:20:19 +07:00
|
|
|
i2c = intel_gmbus_get_adapter(dev_priv, GMBUS_PIN_DPB);
|
2014-03-05 21:20:53 +07:00
|
|
|
ret = intel_crt_ddc_get_modes(connector, i2c);
|
|
|
|
|
|
|
|
out:
|
2017-02-22 13:34:27 +07:00
|
|
|
intel_display_power_put(dev_priv, intel_encoder->power_domain);
|
2014-03-05 21:20:53 +07:00
|
|
|
|
|
|
|
return ret;
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
}
|
|
|
|
|
2016-06-22 04:03:42 +07:00
|
|
|
void intel_crt_reset(struct drm_encoder *encoder)
|
2011-01-24 22:17:08 +07:00
|
|
|
{
|
2016-11-16 15:55:40 +07:00
|
|
|
struct drm_i915_private *dev_priv = to_i915(encoder->dev);
|
2016-06-22 04:03:41 +07:00
|
|
|
struct intel_crt *crt = intel_encoder_to_crt(to_intel_encoder(encoder));
|
2011-01-24 22:17:08 +07:00
|
|
|
|
2016-11-16 15:55:40 +07:00
|
|
|
if (INTEL_GEN(dev_priv) >= 5) {
|
2012-10-12 01:08:24 +07:00
|
|
|
u32 adpa;
|
|
|
|
|
2013-01-26 02:44:42 +07:00
|
|
|
adpa = I915_READ(crt->adpa_reg);
|
2012-10-12 01:08:24 +07:00
|
|
|
adpa &= ~ADPA_CRT_HOTPLUG_MASK;
|
|
|
|
adpa |= ADPA_HOTPLUG_BITS;
|
2013-01-26 02:44:42 +07:00
|
|
|
I915_WRITE(crt->adpa_reg, adpa);
|
|
|
|
POSTING_READ(crt->adpa_reg);
|
2012-10-12 01:08:24 +07:00
|
|
|
|
2014-10-17 00:52:30 +07:00
|
|
|
DRM_DEBUG_KMS("crt adpa set to 0x%x\n", adpa);
|
2011-01-24 22:17:08 +07:00
|
|
|
crt->force_hotplug_required = 1;
|
2012-10-12 01:08:24 +07:00
|
|
|
}
|
|
|
|
|
2011-01-24 22:17:08 +07:00
|
|
|
}
|
|
|
|
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
/*
|
|
|
|
* Routines for controlling stuff on the analog port
|
|
|
|
*/
|
|
|
|
|
|
|
|
static const struct drm_connector_funcs intel_crt_connector_funcs = {
|
|
|
|
.fill_modes = drm_helper_probe_single_connector_modes,
|
2016-06-24 20:00:15 +07:00
|
|
|
.late_register = intel_connector_register,
|
2016-06-17 17:40:33 +07:00
|
|
|
.early_unregister = intel_connector_unregister,
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
.destroy = intel_crt_destroy,
|
2015-01-23 07:50:32 +07:00
|
|
|
.atomic_destroy_state = drm_atomic_helper_connector_destroy_state,
|
2015-03-20 21:18:06 +07:00
|
|
|
.atomic_duplicate_state = drm_atomic_helper_connector_duplicate_state,
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
};
|
|
|
|
|
|
|
|
static const struct drm_connector_helper_funcs intel_crt_connector_helper_funcs = {
|
2017-04-07 01:55:20 +07:00
|
|
|
.detect_ctx = intel_crt_detect,
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
.mode_valid = intel_crt_mode_valid,
|
|
|
|
.get_modes = intel_crt_get_modes,
|
|
|
|
};
|
|
|
|
|
|
|
|
static const struct drm_encoder_funcs intel_crt_enc_funcs = {
|
2016-06-22 04:03:41 +07:00
|
|
|
.reset = intel_crt_reset,
|
2010-08-04 19:50:23 +07:00
|
|
|
.destroy = intel_encoder_destroy,
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
};
|
|
|
|
|
2016-11-23 21:21:44 +07:00
|
|
|
void intel_crt_init(struct drm_i915_private *dev_priv)
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
{
|
|
|
|
struct drm_connector *connector;
|
2010-11-16 17:58:37 +07:00
|
|
|
struct intel_crt *crt;
|
2010-03-29 14:53:23 +07:00
|
|
|
struct intel_connector *intel_connector;
|
2015-11-21 03:35:41 +07:00
|
|
|
i915_reg_t adpa_reg;
|
|
|
|
u32 adpa;
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
|
2016-10-13 17:02:53 +07:00
|
|
|
if (HAS_PCH_SPLIT(dev_priv))
|
2015-11-21 03:35:41 +07:00
|
|
|
adpa_reg = PCH_ADPA;
|
2016-10-13 17:03:08 +07:00
|
|
|
else if (IS_VALLEYVIEW(dev_priv))
|
2015-11-21 03:35:41 +07:00
|
|
|
adpa_reg = VLV_ADPA;
|
|
|
|
else
|
|
|
|
adpa_reg = ADPA;
|
|
|
|
|
|
|
|
adpa = I915_READ(adpa_reg);
|
|
|
|
if ((adpa & ADPA_DAC_ENABLE) == 0) {
|
|
|
|
/*
|
|
|
|
* On some machines (some IVB at least) CRT can be
|
|
|
|
* fused off, but there's no known fuse bit to
|
|
|
|
* indicate that. On these machine the ADPA register
|
|
|
|
* works normally, except the DAC enable bit won't
|
|
|
|
* take. So the only way to tell is attempt to enable
|
|
|
|
* it and see what happens.
|
|
|
|
*/
|
|
|
|
I915_WRITE(adpa_reg, adpa | ADPA_DAC_ENABLE |
|
|
|
|
ADPA_HSYNC_CNTL_DISABLE | ADPA_VSYNC_CNTL_DISABLE);
|
|
|
|
if ((I915_READ(adpa_reg) & ADPA_DAC_ENABLE) == 0)
|
|
|
|
return;
|
|
|
|
I915_WRITE(adpa_reg, adpa);
|
|
|
|
}
|
|
|
|
|
2010-11-16 17:58:37 +07:00
|
|
|
crt = kzalloc(sizeof(struct intel_crt), GFP_KERNEL);
|
|
|
|
if (!crt)
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
return;
|
|
|
|
|
2015-04-10 14:59:10 +07:00
|
|
|
intel_connector = intel_connector_alloc();
|
2010-03-29 14:53:23 +07:00
|
|
|
if (!intel_connector) {
|
2010-11-16 17:58:37 +07:00
|
|
|
kfree(crt);
|
2010-03-29 14:53:23 +07:00
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
connector = &intel_connector->base;
|
2013-03-26 02:40:05 +07:00
|
|
|
crt->connector = intel_connector;
|
2016-11-23 21:21:44 +07:00
|
|
|
drm_connector_init(&dev_priv->drm, &intel_connector->base,
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
&intel_crt_connector_funcs, DRM_MODE_CONNECTOR_VGA);
|
|
|
|
|
2016-11-23 21:21:44 +07:00
|
|
|
drm_encoder_init(&dev_priv->drm, &crt->base.base, &intel_crt_enc_funcs,
|
2016-05-28 00:59:24 +07:00
|
|
|
DRM_MODE_ENCODER_DAC, "CRT");
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
|
2010-11-16 17:58:37 +07:00
|
|
|
intel_connector_attach_encoder(intel_connector, &crt->base);
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
|
2010-11-16 17:58:37 +07:00
|
|
|
crt->base.type = INTEL_OUTPUT_ANALOG;
|
2014-03-03 21:15:30 +07:00
|
|
|
crt->base.cloneable = (1 << INTEL_OUTPUT_DVO) | (1 << INTEL_OUTPUT_HDMI);
|
2016-10-13 17:02:58 +07:00
|
|
|
if (IS_I830(dev_priv))
|
2012-05-10 01:37:19 +07:00
|
|
|
crt->base.crtc_mask = (1 << 0);
|
|
|
|
else
|
2012-08-14 11:34:45 +07:00
|
|
|
crt->base.crtc_mask = (1 << 0) | (1 << 1) | (1 << 2);
|
2012-05-10 01:37:19 +07:00
|
|
|
|
2016-10-13 17:03:10 +07:00
|
|
|
if (IS_GEN2(dev_priv))
|
2012-01-28 20:49:23 +07:00
|
|
|
connector->interlace_allowed = 0;
|
|
|
|
else
|
|
|
|
connector->interlace_allowed = 1;
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
connector->doublescan_allowed = 0;
|
|
|
|
|
2015-11-21 03:35:41 +07:00
|
|
|
crt->adpa_reg = adpa_reg;
|
2012-07-11 21:27:57 +07:00
|
|
|
|
2017-02-22 13:34:27 +07:00
|
|
|
crt->base.power_domain = POWER_DOMAIN_PORT_CRT;
|
|
|
|
|
2016-11-07 16:29:20 +07:00
|
|
|
if (I915_HAS_HOTPLUG(dev_priv) &&
|
2018-01-18 02:21:46 +07:00
|
|
|
!dmi_check_system(intel_spurious_crt_detect)) {
|
2013-02-26 00:06:49 +07:00
|
|
|
crt->base.hpd_pin = HPD_CRT;
|
2018-01-18 02:21:46 +07:00
|
|
|
crt->base.hotplug = intel_encoder_hotplug;
|
|
|
|
}
|
2017-10-05 17:52:14 +07:00
|
|
|
|
2016-10-13 17:02:52 +07:00
|
|
|
if (HAS_DDI(dev_priv)) {
|
2016-09-20 08:24:38 +07:00
|
|
|
crt->base.port = PORT_E;
|
2013-11-08 00:25:59 +07:00
|
|
|
crt->base.get_config = hsw_crt_get_config;
|
2012-11-01 03:12:21 +07:00
|
|
|
crt->base.get_hw_state = intel_ddi_get_hw_state;
|
2017-10-17 21:03:13 +07:00
|
|
|
crt->base.compute_config = hsw_crt_compute_config;
|
2017-10-05 17:52:10 +07:00
|
|
|
crt->base.pre_pll_enable = hsw_pre_pll_enable_crt;
|
|
|
|
crt->base.pre_enable = hsw_pre_enable_crt;
|
|
|
|
crt->base.enable = hsw_enable_crt;
|
2017-10-05 17:52:11 +07:00
|
|
|
crt->base.disable = hsw_disable_crt;
|
2016-08-23 21:18:08 +07:00
|
|
|
crt->base.post_disable = hsw_post_disable_crt;
|
2013-11-08 00:25:59 +07:00
|
|
|
} else {
|
2017-10-05 17:52:14 +07:00
|
|
|
if (HAS_PCH_SPLIT(dev_priv)) {
|
2017-10-17 21:03:13 +07:00
|
|
|
crt->base.compute_config = pch_crt_compute_config;
|
2017-10-05 17:52:14 +07:00
|
|
|
crt->base.disable = pch_disable_crt;
|
|
|
|
crt->base.post_disable = pch_post_disable_crt;
|
|
|
|
} else {
|
2017-10-17 21:03:13 +07:00
|
|
|
crt->base.compute_config = intel_crt_compute_config;
|
2017-10-05 17:52:14 +07:00
|
|
|
crt->base.disable = intel_disable_crt;
|
|
|
|
}
|
2016-09-20 08:24:38 +07:00
|
|
|
crt->base.port = PORT_NONE;
|
2013-11-08 00:25:59 +07:00
|
|
|
crt->base.get_config = intel_crt_get_config;
|
2012-11-01 03:12:21 +07:00
|
|
|
crt->base.get_hw_state = intel_crt_get_hw_state;
|
2017-10-05 17:52:10 +07:00
|
|
|
crt->base.enable = intel_enable_crt;
|
2013-11-08 00:25:59 +07:00
|
|
|
}
|
2012-07-02 18:41:21 +07:00
|
|
|
intel_connector->get_hw_state = intel_connector_get_hw_state;
|
2012-04-18 05:06:33 +07:00
|
|
|
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
drm_connector_helper_add(connector, &intel_crt_connector_helper_funcs);
|
|
|
|
|
2016-11-07 16:29:20 +07:00
|
|
|
if (!I915_HAS_HOTPLUG(dev_priv))
|
2013-04-16 18:36:55 +07:00
|
|
|
intel_connector->polled = DRM_CONNECTOR_POLL_CONNECT;
|
2010-05-07 13:42:51 +07:00
|
|
|
|
2010-11-16 15:03:53 +07:00
|
|
|
/*
|
|
|
|
* Configure the automatic hotplug detection stuff
|
|
|
|
*/
|
|
|
|
crt->force_hotplug_required = 0;
|
|
|
|
|
2012-12-01 21:04:26 +07:00
|
|
|
/*
|
2012-12-12 01:48:29 +07:00
|
|
|
* TODO: find a proper way to discover whether we need to set the the
|
|
|
|
* polarity and link reversal bits or not, instead of relying on the
|
|
|
|
* BIOS.
|
2012-12-01 21:04:26 +07:00
|
|
|
*/
|
2016-10-13 17:02:53 +07:00
|
|
|
if (HAS_PCH_LPT(dev_priv)) {
|
2012-12-12 01:48:29 +07:00
|
|
|
u32 fdi_config = FDI_RX_POLARITY_REVERSED_LPT |
|
|
|
|
FDI_RX_LINK_REVERSAL_OVERRIDE;
|
|
|
|
|
2015-09-19 00:03:30 +07:00
|
|
|
dev_priv->fdi_rx_config = I915_READ(FDI_RX_CTL(PIPE_A)) & fdi_config;
|
2012-12-12 01:48:29 +07:00
|
|
|
}
|
2014-01-17 04:28:44 +07:00
|
|
|
|
2016-06-22 04:03:41 +07:00
|
|
|
intel_crt_reset(&crt->base.base);
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 05:24:08 +07:00
|
|
|
}
|