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 06:24:08 +08:00
|
|
|
/*
|
|
|
|
* Copyright © 2006-2007 Intel Corporation
|
|
|
|
* Copyright (c) 2006 Dave Airlie <airlied@linux.ie>
|
|
|
|
*
|
|
|
|
* 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>
|
|
|
|
* Dave Airlie <airlied@linux.ie>
|
|
|
|
* Jesse Barnes <jesse.barnes@intel.com>
|
|
|
|
*/
|
|
|
|
|
2009-09-11 06:28:03 +08:00
|
|
|
#include <acpi/button.h>
|
2009-02-04 18:05:41 +08: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 06:24:08 +08: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 16:04:11 +08:00
|
|
|
#include <linux/slab.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 06:24:08 +08:00
|
|
|
#include "drmP.h"
|
|
|
|
#include "drm.h"
|
|
|
|
#include "drm_crtc.h"
|
|
|
|
#include "drm_edid.h"
|
|
|
|
#include "intel_drv.h"
|
|
|
|
#include "i915_drm.h"
|
|
|
|
#include "i915_drv.h"
|
2009-06-26 09:46:18 +08:00
|
|
|
#include <linux/acpi.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 06:24:08 +08:00
|
|
|
|
2009-06-22 15:31:25 +08:00
|
|
|
/* Private structure for the integrated LVDS support */
|
2010-08-04 20:50:23 +08:00
|
|
|
struct intel_lvds {
|
|
|
|
struct intel_encoder base;
|
2010-09-13 00:34:41 +08:00
|
|
|
|
2010-09-17 06:05:10 +08:00
|
|
|
struct edid *edid;
|
2010-09-13 00:34:41 +08:00
|
|
|
|
2009-06-22 15:31:25 +08:00
|
|
|
int fitting_mode;
|
|
|
|
u32 pfit_control;
|
|
|
|
u32 pfit_pgm_ratios;
|
2010-09-13 08:16:10 +08:00
|
|
|
bool pfit_dirty;
|
2010-09-13 00:34:41 +08:00
|
|
|
|
|
|
|
struct drm_display_mode *fixed_mode;
|
2009-06-22 15:31:25 +08:00
|
|
|
};
|
|
|
|
|
2010-09-13 00:34:41 +08:00
|
|
|
static struct intel_lvds *to_intel_lvds(struct drm_encoder *encoder)
|
2010-08-04 20:50:23 +08:00
|
|
|
{
|
2010-09-09 22:14:28 +08:00
|
|
|
return container_of(encoder, struct intel_lvds, base.base);
|
2010-08-04 20:50:23 +08:00
|
|
|
}
|
|
|
|
|
2010-09-13 00:34:41 +08:00
|
|
|
static struct intel_lvds *intel_attached_lvds(struct drm_connector *connector)
|
|
|
|
{
|
|
|
|
return container_of(intel_attached_encoder(connector),
|
|
|
|
struct intel_lvds, 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 06:24:08 +08:00
|
|
|
/**
|
|
|
|
* Sets the power state for the panel.
|
|
|
|
*/
|
2010-12-06 03:21:18 +08:00
|
|
|
static void intel_lvds_enable(struct intel_lvds *intel_lvds)
|
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 06:24:08 +08:00
|
|
|
{
|
2010-09-13 08:16:10 +08:00
|
|
|
struct drm_device *dev = intel_lvds->base.base.dev;
|
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 06:24:08 +08:00
|
|
|
struct drm_i915_private *dev_priv = dev->dev_private;
|
2010-09-13 08:16:10 +08:00
|
|
|
u32 ctl_reg, lvds_reg;
|
2009-06-05 15:38:44 +08:00
|
|
|
|
2010-01-29 08:45:52 +08:00
|
|
|
if (HAS_PCH_SPLIT(dev)) {
|
2009-06-05 15:38:44 +08:00
|
|
|
ctl_reg = PCH_PP_CONTROL;
|
2010-02-12 04:41:05 +08:00
|
|
|
lvds_reg = PCH_LVDS;
|
2009-06-05 15:38:44 +08:00
|
|
|
} else {
|
|
|
|
ctl_reg = PP_CONTROL;
|
2010-02-12 04:41:05 +08:00
|
|
|
lvds_reg = LVDS;
|
2009-06-05 15:38:44 +08: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 06:24:08 +08:00
|
|
|
|
2010-12-06 03:21:18 +08:00
|
|
|
I915_WRITE(lvds_reg, I915_READ(lvds_reg) | LVDS_PORT_EN);
|
2010-09-13 08:16:10 +08:00
|
|
|
|
2010-12-06 03:21:18 +08:00
|
|
|
if (intel_lvds->pfit_dirty) {
|
|
|
|
/*
|
|
|
|
* Enable automatic panel scaling so that non-native modes
|
|
|
|
* fill the screen. The panel fitter should only be
|
|
|
|
* adjusted whilst the pipe is disabled, according to
|
|
|
|
* register description and PRM.
|
|
|
|
*/
|
|
|
|
DRM_DEBUG_KMS("applying panel-fitter: %x, %x\n",
|
|
|
|
intel_lvds->pfit_control,
|
|
|
|
intel_lvds->pfit_pgm_ratios);
|
|
|
|
if (wait_for((I915_READ(PP_STATUS) & PP_ON) == 0, 1000)) {
|
|
|
|
DRM_ERROR("timed out waiting for panel to power off\n");
|
|
|
|
} else {
|
|
|
|
I915_WRITE(PFIT_PGM_RATIOS, intel_lvds->pfit_pgm_ratios);
|
|
|
|
I915_WRITE(PFIT_CONTROL, intel_lvds->pfit_control);
|
2010-09-21 21:06:12 +08:00
|
|
|
intel_lvds->pfit_dirty = false;
|
2010-09-13 08:16:10 +08:00
|
|
|
}
|
2010-12-06 03:21:18 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
I915_WRITE(ctl_reg, I915_READ(ctl_reg) | POWER_TARGET_ON);
|
|
|
|
POSTING_READ(lvds_reg);
|
|
|
|
|
2011-01-12 01:06:04 +08:00
|
|
|
intel_panel_enable_backlight(dev);
|
2010-12-06 03:21:18 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
static void intel_lvds_disable(struct intel_lvds *intel_lvds)
|
|
|
|
{
|
|
|
|
struct drm_device *dev = intel_lvds->base.base.dev;
|
|
|
|
struct drm_i915_private *dev_priv = dev->dev_private;
|
|
|
|
u32 ctl_reg, lvds_reg;
|
|
|
|
|
|
|
|
if (HAS_PCH_SPLIT(dev)) {
|
|
|
|
ctl_reg = PCH_PP_CONTROL;
|
|
|
|
lvds_reg = PCH_LVDS;
|
|
|
|
} else {
|
|
|
|
ctl_reg = PP_CONTROL;
|
|
|
|
lvds_reg = LVDS;
|
|
|
|
}
|
|
|
|
|
2011-01-12 01:06:04 +08:00
|
|
|
intel_panel_disable_backlight(dev);
|
2010-12-06 03:21:18 +08:00
|
|
|
|
|
|
|
I915_WRITE(ctl_reg, I915_READ(ctl_reg) & ~POWER_TARGET_ON);
|
|
|
|
|
|
|
|
if (intel_lvds->pfit_control) {
|
|
|
|
if (wait_for((I915_READ(PP_STATUS) & PP_ON) == 0, 1000))
|
|
|
|
DRM_ERROR("timed out waiting for panel to power off\n");
|
2010-09-13 08:16:10 +08:00
|
|
|
|
2010-12-06 03:21:18 +08:00
|
|
|
I915_WRITE(PFIT_CONTROL, 0);
|
|
|
|
intel_lvds->pfit_dirty = true;
|
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 06:24:08 +08:00
|
|
|
}
|
2010-12-06 03:21:18 +08:00
|
|
|
|
|
|
|
I915_WRITE(lvds_reg, I915_READ(lvds_reg) & ~LVDS_PORT_EN);
|
2010-09-12 20:07:25 +08:00
|
|
|
POSTING_READ(lvds_reg);
|
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 06:24:08 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
static void intel_lvds_dpms(struct drm_encoder *encoder, int mode)
|
|
|
|
{
|
2010-09-13 00:34:41 +08:00
|
|
|
struct intel_lvds *intel_lvds = to_intel_lvds(encoder);
|
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 06:24:08 +08:00
|
|
|
|
|
|
|
if (mode == DRM_MODE_DPMS_ON)
|
2010-12-06 03:21:18 +08:00
|
|
|
intel_lvds_enable(intel_lvds);
|
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 06:24:08 +08:00
|
|
|
else
|
2010-12-06 03:21:18 +08:00
|
|
|
intel_lvds_disable(intel_lvds);
|
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 06:24:08 +08:00
|
|
|
|
|
|
|
/* XXX: We never power down the LVDS pairs. */
|
|
|
|
}
|
|
|
|
|
|
|
|
static int intel_lvds_mode_valid(struct drm_connector *connector,
|
|
|
|
struct drm_display_mode *mode)
|
|
|
|
{
|
2010-09-13 00:34:41 +08:00
|
|
|
struct intel_lvds *intel_lvds = intel_attached_lvds(connector);
|
|
|
|
struct drm_display_mode *fixed_mode = intel_lvds->fixed_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 06:24:08 +08:00
|
|
|
|
2010-09-13 00:34:41 +08:00
|
|
|
if (mode->hdisplay > fixed_mode->hdisplay)
|
|
|
|
return MODE_PANEL;
|
|
|
|
if (mode->vdisplay > fixed_mode->vdisplay)
|
|
|
|
return MODE_PANEL;
|
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 06:24:08 +08:00
|
|
|
|
|
|
|
return MODE_OK;
|
|
|
|
}
|
|
|
|
|
2010-07-18 19:05:54 +08:00
|
|
|
static void
|
|
|
|
centre_horizontally(struct drm_display_mode *mode,
|
|
|
|
int width)
|
|
|
|
{
|
|
|
|
u32 border, sync_pos, blank_width, sync_width;
|
|
|
|
|
|
|
|
/* keep the hsync and hblank widths constant */
|
|
|
|
sync_width = mode->crtc_hsync_end - mode->crtc_hsync_start;
|
|
|
|
blank_width = mode->crtc_hblank_end - mode->crtc_hblank_start;
|
|
|
|
sync_pos = (blank_width - sync_width + 1) / 2;
|
|
|
|
|
|
|
|
border = (mode->hdisplay - width + 1) / 2;
|
|
|
|
border += border & 1; /* make the border even */
|
|
|
|
|
|
|
|
mode->crtc_hdisplay = width;
|
|
|
|
mode->crtc_hblank_start = width + border;
|
|
|
|
mode->crtc_hblank_end = mode->crtc_hblank_start + blank_width;
|
|
|
|
|
|
|
|
mode->crtc_hsync_start = mode->crtc_hblank_start + sync_pos;
|
|
|
|
mode->crtc_hsync_end = mode->crtc_hsync_start + sync_width;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
|
|
|
centre_vertically(struct drm_display_mode *mode,
|
|
|
|
int height)
|
|
|
|
{
|
|
|
|
u32 border, sync_pos, blank_width, sync_width;
|
|
|
|
|
|
|
|
/* keep the vsync and vblank widths constant */
|
|
|
|
sync_width = mode->crtc_vsync_end - mode->crtc_vsync_start;
|
|
|
|
blank_width = mode->crtc_vblank_end - mode->crtc_vblank_start;
|
|
|
|
sync_pos = (blank_width - sync_width + 1) / 2;
|
|
|
|
|
|
|
|
border = (mode->vdisplay - height + 1) / 2;
|
|
|
|
|
|
|
|
mode->crtc_vdisplay = height;
|
|
|
|
mode->crtc_vblank_start = height + border;
|
|
|
|
mode->crtc_vblank_end = mode->crtc_vblank_start + blank_width;
|
|
|
|
|
|
|
|
mode->crtc_vsync_start = mode->crtc_vblank_start + sync_pos;
|
|
|
|
mode->crtc_vsync_end = mode->crtc_vsync_start + sync_width;
|
|
|
|
}
|
|
|
|
|
|
|
|
static inline u32 panel_fitter_scaling(u32 source, u32 target)
|
|
|
|
{
|
|
|
|
/*
|
|
|
|
* Floating point operation is not supported. So the FACTOR
|
|
|
|
* is defined, which can avoid the floating point computation
|
|
|
|
* when calculating the panel ratio.
|
|
|
|
*/
|
|
|
|
#define ACCURACY 12
|
|
|
|
#define FACTOR (1 << ACCURACY)
|
|
|
|
u32 ratio = source * FACTOR / target;
|
|
|
|
return (FACTOR * ratio + FACTOR/2) / FACTOR;
|
|
|
|
}
|
|
|
|
|
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 06:24:08 +08:00
|
|
|
static bool intel_lvds_mode_fixup(struct drm_encoder *encoder,
|
|
|
|
struct drm_display_mode *mode,
|
|
|
|
struct drm_display_mode *adjusted_mode)
|
|
|
|
{
|
|
|
|
struct drm_device *dev = encoder->dev;
|
|
|
|
struct drm_i915_private *dev_priv = dev->dev_private;
|
|
|
|
struct intel_crtc *intel_crtc = to_intel_crtc(encoder->crtc);
|
2010-09-13 00:34:41 +08:00
|
|
|
struct intel_lvds *intel_lvds = to_intel_lvds(encoder);
|
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 06:24:08 +08:00
|
|
|
struct drm_encoder *tmp_encoder;
|
2010-07-18 19:05:54 +08:00
|
|
|
u32 pfit_control = 0, pfit_pgm_ratios = 0, border = 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 06:24:08 +08:00
|
|
|
|
|
|
|
/* Should never happen!! */
|
2010-09-17 07:32:17 +08:00
|
|
|
if (INTEL_INFO(dev)->gen < 4 && intel_crtc->pipe == 0) {
|
2009-06-29 06:42:17 +08:00
|
|
|
DRM_ERROR("Can't support LVDS on pipe A\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 06:24:08 +08:00
|
|
|
return false;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Should never happen!! */
|
|
|
|
list_for_each_entry(tmp_encoder, &dev->mode_config.encoder_list, head) {
|
|
|
|
if (tmp_encoder != encoder && tmp_encoder->crtc == encoder->crtc) {
|
2009-06-29 06:42:17 +08:00
|
|
|
DRM_ERROR("Can't enable LVDS and another "
|
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 06:24:08 +08:00
|
|
|
"encoder on the same pipe\n");
|
|
|
|
return false;
|
|
|
|
}
|
|
|
|
}
|
2010-08-07 18:01:28 +08: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 06:24:08 +08:00
|
|
|
/*
|
2010-07-17 20:38:43 +08:00
|
|
|
* We have timings from the BIOS for the panel, put them in
|
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 06:24:08 +08:00
|
|
|
* to the adjusted mode. The CRTC will be set up for this mode,
|
|
|
|
* with the panel scaling set up to source from the H/VDisplay
|
|
|
|
* of the original mode.
|
|
|
|
*/
|
2010-09-13 00:34:41 +08:00
|
|
|
intel_fixed_panel_mode(intel_lvds->fixed_mode, adjusted_mode);
|
2010-08-07 18:01:28 +08:00
|
|
|
|
|
|
|
if (HAS_PCH_SPLIT(dev)) {
|
|
|
|
intel_pch_panel_fitting(dev, intel_lvds->fitting_mode,
|
|
|
|
mode, adjusted_mode);
|
|
|
|
return true;
|
|
|
|
}
|
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 06:24:08 +08:00
|
|
|
|
2009-06-22 15:31:25 +08:00
|
|
|
/* Native modes don't need fitting */
|
|
|
|
if (adjusted_mode->hdisplay == mode->hdisplay &&
|
2010-07-18 19:05:54 +08:00
|
|
|
adjusted_mode->vdisplay == mode->vdisplay)
|
2009-06-22 15:31:25 +08:00
|
|
|
goto out;
|
|
|
|
|
|
|
|
/* 965+ wants fuzzy fitting */
|
2010-09-17 07:32:17 +08:00
|
|
|
if (INTEL_INFO(dev)->gen >= 4)
|
2010-07-18 19:05:54 +08:00
|
|
|
pfit_control |= ((intel_crtc->pipe << PFIT_PIPE_SHIFT) |
|
|
|
|
PFIT_FILTER_FUZZY);
|
|
|
|
|
2009-06-22 15:31:25 +08:00
|
|
|
/*
|
|
|
|
* Enable automatic panel scaling for non-native modes so that they fill
|
|
|
|
* the screen. Should be enabled before the pipe is enabled, according
|
|
|
|
* to register description and PRM.
|
|
|
|
* Change the value here to see the borders for debugging
|
|
|
|
*/
|
2010-08-07 18:01:28 +08:00
|
|
|
I915_WRITE(BCLRPAT_A, 0);
|
|
|
|
I915_WRITE(BCLRPAT_B, 0);
|
2009-06-22 15:31:25 +08:00
|
|
|
|
2010-08-04 20:50:23 +08:00
|
|
|
switch (intel_lvds->fitting_mode) {
|
2009-07-02 01:04:40 +08:00
|
|
|
case DRM_MODE_SCALE_CENTER:
|
2009-06-22 15:31:25 +08:00
|
|
|
/*
|
|
|
|
* For centered modes, we have to calculate border widths &
|
|
|
|
* heights and modify the values programmed into the CRTC.
|
|
|
|
*/
|
2010-07-18 19:05:54 +08:00
|
|
|
centre_horizontally(adjusted_mode, mode->hdisplay);
|
|
|
|
centre_vertically(adjusted_mode, mode->vdisplay);
|
|
|
|
border = LVDS_BORDER_ENABLE;
|
2009-06-22 15:31:25 +08:00
|
|
|
break;
|
2010-07-18 19:05:54 +08:00
|
|
|
|
2009-06-22 15:31:25 +08:00
|
|
|
case DRM_MODE_SCALE_ASPECT:
|
2010-07-18 19:05:54 +08:00
|
|
|
/* Scale but preserve the aspect ratio */
|
2010-09-17 07:32:17 +08:00
|
|
|
if (INTEL_INFO(dev)->gen >= 4) {
|
2010-07-18 19:05:54 +08:00
|
|
|
u32 scaled_width = adjusted_mode->hdisplay * mode->vdisplay;
|
|
|
|
u32 scaled_height = mode->hdisplay * adjusted_mode->vdisplay;
|
|
|
|
|
2009-06-22 15:31:25 +08:00
|
|
|
/* 965+ is easy, it does everything in hw */
|
2010-07-18 19:05:54 +08:00
|
|
|
if (scaled_width > scaled_height)
|
2010-11-30 00:19:24 +08:00
|
|
|
pfit_control |= PFIT_ENABLE | PFIT_SCALING_PILLAR;
|
2010-07-18 19:05:54 +08:00
|
|
|
else if (scaled_width < scaled_height)
|
2010-11-30 00:19:24 +08:00
|
|
|
pfit_control |= PFIT_ENABLE | PFIT_SCALING_LETTER;
|
|
|
|
else if (adjusted_mode->hdisplay != mode->hdisplay)
|
|
|
|
pfit_control |= PFIT_ENABLE | PFIT_SCALING_AUTO;
|
2009-06-22 15:31:25 +08:00
|
|
|
} else {
|
2010-07-18 19:05:54 +08:00
|
|
|
u32 scaled_width = adjusted_mode->hdisplay * mode->vdisplay;
|
|
|
|
u32 scaled_height = mode->hdisplay * adjusted_mode->vdisplay;
|
2009-06-22 15:31:25 +08:00
|
|
|
/*
|
|
|
|
* For earlier chips we have to calculate the scaling
|
|
|
|
* ratio by hand and program it into the
|
|
|
|
* PFIT_PGM_RATIO register
|
|
|
|
*/
|
2010-07-18 19:05:54 +08:00
|
|
|
if (scaled_width > scaled_height) { /* pillar */
|
|
|
|
centre_horizontally(adjusted_mode, scaled_height / mode->vdisplay);
|
|
|
|
|
|
|
|
border = LVDS_BORDER_ENABLE;
|
|
|
|
if (mode->vdisplay != adjusted_mode->vdisplay) {
|
|
|
|
u32 bits = panel_fitter_scaling(mode->vdisplay, adjusted_mode->vdisplay);
|
|
|
|
pfit_pgm_ratios |= (bits << PFIT_HORIZ_SCALE_SHIFT |
|
|
|
|
bits << PFIT_VERT_SCALE_SHIFT);
|
|
|
|
pfit_control |= (PFIT_ENABLE |
|
|
|
|
VERT_INTERP_BILINEAR |
|
|
|
|
HORIZ_INTERP_BILINEAR);
|
|
|
|
}
|
|
|
|
} else if (scaled_width < scaled_height) { /* letter */
|
|
|
|
centre_vertically(adjusted_mode, scaled_width / mode->hdisplay);
|
|
|
|
|
|
|
|
border = LVDS_BORDER_ENABLE;
|
|
|
|
if (mode->hdisplay != adjusted_mode->hdisplay) {
|
|
|
|
u32 bits = panel_fitter_scaling(mode->hdisplay, adjusted_mode->hdisplay);
|
|
|
|
pfit_pgm_ratios |= (bits << PFIT_HORIZ_SCALE_SHIFT |
|
|
|
|
bits << PFIT_VERT_SCALE_SHIFT);
|
|
|
|
pfit_control |= (PFIT_ENABLE |
|
|
|
|
VERT_INTERP_BILINEAR |
|
|
|
|
HORIZ_INTERP_BILINEAR);
|
|
|
|
}
|
|
|
|
} else
|
|
|
|
/* Aspects match, Let hw scale both directions */
|
|
|
|
pfit_control |= (PFIT_ENABLE |
|
|
|
|
VERT_AUTO_SCALE | HORIZ_AUTO_SCALE |
|
2009-06-22 15:31:25 +08:00
|
|
|
VERT_INTERP_BILINEAR |
|
|
|
|
HORIZ_INTERP_BILINEAR);
|
|
|
|
}
|
|
|
|
break;
|
|
|
|
|
|
|
|
case DRM_MODE_SCALE_FULLSCREEN:
|
|
|
|
/*
|
|
|
|
* Full scaling, even if it changes the aspect ratio.
|
|
|
|
* Fortunately this is all done for us in hw.
|
|
|
|
*/
|
2010-11-30 00:19:24 +08:00
|
|
|
if (mode->vdisplay != adjusted_mode->vdisplay ||
|
|
|
|
mode->hdisplay != adjusted_mode->hdisplay) {
|
|
|
|
pfit_control |= PFIT_ENABLE;
|
|
|
|
if (INTEL_INFO(dev)->gen >= 4)
|
|
|
|
pfit_control |= PFIT_SCALING_AUTO;
|
|
|
|
else
|
|
|
|
pfit_control |= (VERT_AUTO_SCALE |
|
|
|
|
VERT_INTERP_BILINEAR |
|
|
|
|
HORIZ_AUTO_SCALE |
|
|
|
|
HORIZ_INTERP_BILINEAR);
|
|
|
|
}
|
2009-06-22 15:31:25 +08:00
|
|
|
break;
|
2010-07-18 19:05:54 +08:00
|
|
|
|
2009-06-22 15:31:25 +08:00
|
|
|
default:
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
|
|
|
out:
|
2011-02-06 23:50:52 +08:00
|
|
|
/* If not enabling scaling, be consistent and always use 0. */
|
2011-01-12 02:09:58 +08:00
|
|
|
if ((pfit_control & PFIT_ENABLE) == 0) {
|
|
|
|
pfit_control = 0;
|
|
|
|
pfit_pgm_ratios = 0;
|
|
|
|
}
|
2011-02-06 23:50:52 +08:00
|
|
|
|
|
|
|
/* Make sure pre-965 set dither correctly */
|
|
|
|
if (INTEL_INFO(dev)->gen < 4 && dev_priv->lvds_dither)
|
|
|
|
pfit_control |= PANEL_8TO6_DITHER_ENABLE;
|
|
|
|
|
2010-09-13 08:16:10 +08:00
|
|
|
if (pfit_control != intel_lvds->pfit_control ||
|
|
|
|
pfit_pgm_ratios != intel_lvds->pfit_pgm_ratios) {
|
|
|
|
intel_lvds->pfit_control = pfit_control;
|
|
|
|
intel_lvds->pfit_pgm_ratios = pfit_pgm_ratios;
|
|
|
|
intel_lvds->pfit_dirty = true;
|
|
|
|
}
|
2010-07-18 19:05:54 +08:00
|
|
|
dev_priv->lvds_border_bits = border;
|
|
|
|
|
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 06:24:08 +08:00
|
|
|
/*
|
|
|
|
* XXX: It would be nice to support lower refresh rates on the
|
|
|
|
* panels to reduce power consumption, and perhaps match the
|
|
|
|
* user's requested refresh rate.
|
|
|
|
*/
|
|
|
|
|
|
|
|
return true;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void intel_lvds_prepare(struct drm_encoder *encoder)
|
|
|
|
{
|
|
|
|
struct drm_device *dev = encoder->dev;
|
|
|
|
struct drm_i915_private *dev_priv = dev->dev_private;
|
2010-09-13 00:34:41 +08:00
|
|
|
struct intel_lvds *intel_lvds = to_intel_lvds(encoder);
|
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 06:24:08 +08:00
|
|
|
|
2010-09-13 08:16:10 +08:00
|
|
|
/* We try to do the minimum that is necessary in order to unlock
|
|
|
|
* the registers for mode setting.
|
|
|
|
*
|
|
|
|
* On Ironlake, this is quite simple as we just set the unlock key
|
|
|
|
* and ignore all subtleties. (This may cause some issues...)
|
|
|
|
*
|
|
|
|
* Prior to Ironlake, we must disable the pipe if we want to adjust
|
|
|
|
* the panel fitter. However at all other times we can just reset
|
|
|
|
* the registers regardless.
|
|
|
|
*/
|
|
|
|
|
|
|
|
if (HAS_PCH_SPLIT(dev)) {
|
|
|
|
I915_WRITE(PCH_PP_CONTROL,
|
|
|
|
I915_READ(PCH_PP_CONTROL) | PANEL_UNLOCK_REGS);
|
|
|
|
} else if (intel_lvds->pfit_dirty) {
|
|
|
|
I915_WRITE(PP_CONTROL,
|
2010-09-21 21:06:12 +08:00
|
|
|
(I915_READ(PP_CONTROL) | PANEL_UNLOCK_REGS)
|
|
|
|
& ~POWER_TARGET_ON);
|
2010-09-13 08:16:10 +08:00
|
|
|
} else {
|
|
|
|
I915_WRITE(PP_CONTROL,
|
|
|
|
I915_READ(PP_CONTROL) | PANEL_UNLOCK_REGS);
|
|
|
|
}
|
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 06:24:08 +08:00
|
|
|
}
|
|
|
|
|
2010-09-13 08:16:10 +08:00
|
|
|
static void intel_lvds_commit(struct drm_encoder *encoder)
|
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 06:24:08 +08:00
|
|
|
{
|
|
|
|
struct drm_device *dev = encoder->dev;
|
|
|
|
struct drm_i915_private *dev_priv = dev->dev_private;
|
2010-09-13 00:34:41 +08:00
|
|
|
struct intel_lvds *intel_lvds = to_intel_lvds(encoder);
|
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 06:24:08 +08:00
|
|
|
|
2010-09-13 08:16:10 +08:00
|
|
|
/* Undo any unlocking done in prepare to prevent accidental
|
|
|
|
* adjustment of the registers.
|
|
|
|
*/
|
|
|
|
if (HAS_PCH_SPLIT(dev)) {
|
|
|
|
u32 val = I915_READ(PCH_PP_CONTROL);
|
|
|
|
if ((val & PANEL_UNLOCK_REGS) == PANEL_UNLOCK_REGS)
|
|
|
|
I915_WRITE(PCH_PP_CONTROL, val & 0x3);
|
|
|
|
} else {
|
|
|
|
u32 val = I915_READ(PP_CONTROL);
|
|
|
|
if ((val & PANEL_UNLOCK_REGS) == PANEL_UNLOCK_REGS)
|
|
|
|
I915_WRITE(PP_CONTROL, val & 0x3);
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Always do a full power on as we do not know what state
|
|
|
|
* we were left in.
|
|
|
|
*/
|
2010-12-06 03:21:18 +08:00
|
|
|
intel_lvds_enable(intel_lvds);
|
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 06:24:08 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
static void intel_lvds_mode_set(struct drm_encoder *encoder,
|
|
|
|
struct drm_display_mode *mode,
|
|
|
|
struct drm_display_mode *adjusted_mode)
|
|
|
|
{
|
|
|
|
/*
|
|
|
|
* The LVDS pin pair will already have been turned on in the
|
|
|
|
* intel_crtc_mode_set since it has a large impact on the DPLL
|
|
|
|
* settings.
|
|
|
|
*/
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* Detect the LVDS connection.
|
|
|
|
*
|
2009-09-11 06:28:04 +08:00
|
|
|
* Since LVDS doesn't have hotlug, we use the lid as a proxy. Open means
|
|
|
|
* connected and closed means disconnected. We also send hotplug events as
|
|
|
|
* needed, using lid status notification from the input layer.
|
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 06:24:08 +08:00
|
|
|
*/
|
2010-09-10 06:51:02 +08:00
|
|
|
static enum drm_connector_status
|
2010-09-14 18:07:23 +08:00
|
|
|
intel_lvds_detect(struct drm_connector *connector, 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 06:24:08 +08:00
|
|
|
{
|
2010-02-13 01:30:00 +08:00
|
|
|
struct drm_device *dev = connector->dev;
|
2009-09-11 06:28:04 +08:00
|
|
|
enum drm_connector_status status = connector_status_connected;
|
|
|
|
|
2010-02-13 01:30:00 +08:00
|
|
|
/* ACPI lid methods were generally unreliable in this generation, so
|
|
|
|
* don't even bother.
|
|
|
|
*/
|
2010-03-18 04:48:06 +08:00
|
|
|
if (IS_GEN2(dev) || IS_GEN3(dev))
|
2010-02-13 01:30:00 +08:00
|
|
|
return connector_status_connected;
|
|
|
|
|
2009-09-11 06:28:04 +08: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 06:24:08 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* Return the list of DDC modes if available, or the BIOS fixed mode otherwise.
|
|
|
|
*/
|
|
|
|
static int intel_lvds_get_modes(struct drm_connector *connector)
|
|
|
|
{
|
2010-09-13 00:34:41 +08:00
|
|
|
struct intel_lvds *intel_lvds = intel_attached_lvds(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 06:24:08 +08:00
|
|
|
struct drm_device *dev = connector->dev;
|
2010-09-13 00:34:41 +08:00
|
|
|
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 06:24:08 +08:00
|
|
|
|
2010-11-09 07:20:52 +08:00
|
|
|
if (intel_lvds->edid)
|
2010-09-17 06:05:10 +08:00
|
|
|
return drm_add_edid_modes(connector, intel_lvds->edid);
|
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 06:24:08 +08:00
|
|
|
|
2010-09-13 00:34:41 +08:00
|
|
|
mode = drm_mode_duplicate(dev, intel_lvds->fixed_mode);
|
|
|
|
if (mode == 0)
|
|
|
|
return 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 06:24:08 +08:00
|
|
|
|
2010-09-13 00:34:41 +08:00
|
|
|
drm_mode_probed_add(connector, mode);
|
|
|
|
return 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 06:24:08 +08:00
|
|
|
}
|
|
|
|
|
2010-07-02 16:44:23 +08:00
|
|
|
static int intel_no_modeset_on_lid_dmi_callback(const struct dmi_system_id *id)
|
|
|
|
{
|
|
|
|
DRM_DEBUG_KMS("Skipping forced modeset for %s\n", id->ident);
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* The GPU hangs up on these systems if modeset is performed on LID open */
|
|
|
|
static const struct dmi_system_id intel_no_modeset_on_lid[] = {
|
|
|
|
{
|
|
|
|
.callback = intel_no_modeset_on_lid_dmi_callback,
|
|
|
|
.ident = "Toshiba Tecra A11",
|
|
|
|
.matches = {
|
|
|
|
DMI_MATCH(DMI_SYS_VENDOR, "TOSHIBA"),
|
|
|
|
DMI_MATCH(DMI_PRODUCT_NAME, "TECRA A11"),
|
|
|
|
},
|
|
|
|
},
|
|
|
|
|
|
|
|
{ } /* terminating entry */
|
|
|
|
};
|
|
|
|
|
2009-11-03 01:29:55 +08:00
|
|
|
/*
|
|
|
|
* Lid events. Note the use of 'modeset_on_lid':
|
|
|
|
* - we set it on lid close, and reset it on open
|
|
|
|
* - we use it as a "only once" bit (ie we ignore
|
|
|
|
* duplicate events where it was already properly
|
|
|
|
* set/reset)
|
|
|
|
* - the suspend/resume paths will also set it to
|
|
|
|
* zero, since they restore the mode ("lid open").
|
|
|
|
*/
|
2009-09-11 06:28:03 +08:00
|
|
|
static int intel_lid_notify(struct notifier_block *nb, unsigned long val,
|
|
|
|
void *unused)
|
|
|
|
{
|
|
|
|
struct drm_i915_private *dev_priv =
|
|
|
|
container_of(nb, struct drm_i915_private, lid_notifier);
|
|
|
|
struct drm_device *dev = dev_priv->dev;
|
drm/i915: Update LVDS connector status when receiving ACPI LID event
Dirk reports that nothing is displayed on LVDS when using ubuntu 9.1 after
close/reopen the LID. And I also reproduce this issue on another laptop.
After some tests and debug, it seems that it is related with that the
LVDS status is not updated in time in course of suspend/resume.
Now the LID state is used to check whether the LVDS is connected or
disconnected. And when the LID is closed, it means that the LVDS is
disconnected. When it is reopened, it means that the LVDS is connected.
At the same time on some distributions the LID event is also used to put
the system into suspend state. When the LID is closed, the system will enter
the suspend state. When the LID is reopened, the system will be resumed.
In such case when the LID is closed, user-space script will receive the LID
notification event and detect the LVDS as disconnected. Then the system will
enter the suspended state. When the LID is reopened, the system will be
resumed. As the LVDS status is not updated in course of resume, it will cause
that the LVDS connector is marked as unused and disabled. After the resume is
finished,user-space script will try to configure the display mode for LVDS.
But unfortunately as the LVDS status is not updated in time and it is still
marked as disconnected, the LVDS and its corresponding CRTC will be disabled
again in the function of drm_helper_disable_unused_functions after changing
mode for LVDS.
So we had better check and update the status of LVDS connector after receiving
the LID notication event. Then after the system is resumed from suspended
state, we can set the display mode for LVDS correctly.
Signed-off-by: Zhao Yakui <yakui.zhao@intel.com>
Reported-by: Dirk Hohndel <hohndel@infradead.org>
Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>
CC: stable@kernel.org
Signed-off-by: Eric Anholt <eric@anholt.net>
2009-12-11 09:26:11 +08:00
|
|
|
struct drm_connector *connector = dev_priv->int_lvds_connector;
|
2009-09-11 06:28:03 +08:00
|
|
|
|
drm/i915: Update LVDS connector status when receiving ACPI LID event
Dirk reports that nothing is displayed on LVDS when using ubuntu 9.1 after
close/reopen the LID. And I also reproduce this issue on another laptop.
After some tests and debug, it seems that it is related with that the
LVDS status is not updated in time in course of suspend/resume.
Now the LID state is used to check whether the LVDS is connected or
disconnected. And when the LID is closed, it means that the LVDS is
disconnected. When it is reopened, it means that the LVDS is connected.
At the same time on some distributions the LID event is also used to put
the system into suspend state. When the LID is closed, the system will enter
the suspend state. When the LID is reopened, the system will be resumed.
In such case when the LID is closed, user-space script will receive the LID
notification event and detect the LVDS as disconnected. Then the system will
enter the suspended state. When the LID is reopened, the system will be
resumed. As the LVDS status is not updated in course of resume, it will cause
that the LVDS connector is marked as unused and disabled. After the resume is
finished,user-space script will try to configure the display mode for LVDS.
But unfortunately as the LVDS status is not updated in time and it is still
marked as disconnected, the LVDS and its corresponding CRTC will be disabled
again in the function of drm_helper_disable_unused_functions after changing
mode for LVDS.
So we had better check and update the status of LVDS connector after receiving
the LID notication event. Then after the system is resumed from suspended
state, we can set the display mode for LVDS correctly.
Signed-off-by: Zhao Yakui <yakui.zhao@intel.com>
Reported-by: Dirk Hohndel <hohndel@infradead.org>
Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>
CC: stable@kernel.org
Signed-off-by: Eric Anholt <eric@anholt.net>
2009-12-11 09:26:11 +08:00
|
|
|
/*
|
|
|
|
* check and update the status of LVDS connector after receiving
|
|
|
|
* the LID nofication event.
|
|
|
|
*/
|
|
|
|
if (connector)
|
2010-09-10 06:51:02 +08:00
|
|
|
connector->status = connector->funcs->detect(connector,
|
2010-09-14 18:07:23 +08:00
|
|
|
false);
|
2010-09-10 06:51:02 +08:00
|
|
|
|
2010-07-02 16:44:23 +08:00
|
|
|
/* Don't force modeset on machines where it causes a GPU lockup */
|
|
|
|
if (dmi_check_system(intel_no_modeset_on_lid))
|
|
|
|
return NOTIFY_OK;
|
2009-11-03 01:29:55 +08:00
|
|
|
if (!acpi_lid_open()) {
|
|
|
|
dev_priv->modeset_on_lid = 1;
|
|
|
|
return NOTIFY_OK;
|
2009-09-15 01:58:48 +08:00
|
|
|
}
|
2009-09-11 06:28:03 +08:00
|
|
|
|
2009-11-03 01:29:55 +08:00
|
|
|
if (!dev_priv->modeset_on_lid)
|
|
|
|
return NOTIFY_OK;
|
|
|
|
|
|
|
|
dev_priv->modeset_on_lid = 0;
|
|
|
|
|
|
|
|
mutex_lock(&dev->mode_config.mutex);
|
|
|
|
drm_helper_resume_force_mode(dev);
|
|
|
|
mutex_unlock(&dev->mode_config.mutex);
|
2009-09-11 06:28:05 +08:00
|
|
|
|
2009-09-11 06:28:03 +08:00
|
|
|
return NOTIFY_OK;
|
|
|
|
}
|
|
|
|
|
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 06:24:08 +08:00
|
|
|
/**
|
|
|
|
* intel_lvds_destroy - unregister and free LVDS structures
|
|
|
|
* @connector: connector to free
|
|
|
|
*
|
|
|
|
* Unregister the DDC bus for this connector then free the driver private
|
|
|
|
* structure.
|
|
|
|
*/
|
|
|
|
static void intel_lvds_destroy(struct drm_connector *connector)
|
|
|
|
{
|
2009-09-11 06:28:03 +08:00
|
|
|
struct drm_device *dev = connector->dev;
|
|
|
|
struct drm_i915_private *dev_priv = dev->dev_private;
|
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 06:24:08 +08:00
|
|
|
|
2009-09-11 06:28:03 +08:00
|
|
|
if (dev_priv->lid_notifier.notifier_call)
|
|
|
|
acpi_lid_notifier_unregister(&dev_priv->lid_notifier);
|
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 06:24:08 +08:00
|
|
|
drm_sysfs_connector_remove(connector);
|
|
|
|
drm_connector_cleanup(connector);
|
|
|
|
kfree(connector);
|
|
|
|
}
|
|
|
|
|
2009-01-22 20:22:06 +08:00
|
|
|
static int intel_lvds_set_property(struct drm_connector *connector,
|
|
|
|
struct drm_property *property,
|
|
|
|
uint64_t value)
|
|
|
|
{
|
2010-09-13 00:34:41 +08:00
|
|
|
struct intel_lvds *intel_lvds = intel_attached_lvds(connector);
|
2009-06-22 15:31:25 +08:00
|
|
|
struct drm_device *dev = connector->dev;
|
|
|
|
|
2010-09-13 00:34:41 +08:00
|
|
|
if (property == dev->mode_config.scaling_mode_property) {
|
|
|
|
struct drm_crtc *crtc = intel_lvds->base.base.crtc;
|
2010-03-29 16:40:50 +08:00
|
|
|
|
2009-07-02 01:04:40 +08:00
|
|
|
if (value == DRM_MODE_SCALE_NONE) {
|
|
|
|
DRM_DEBUG_KMS("no scaling not supported\n");
|
2010-09-13 00:34:41 +08:00
|
|
|
return -EINVAL;
|
2009-06-22 15:31:25 +08:00
|
|
|
}
|
2010-09-13 00:34:41 +08:00
|
|
|
|
2010-08-04 20:50:23 +08:00
|
|
|
if (intel_lvds->fitting_mode == value) {
|
2009-06-22 15:31:25 +08:00
|
|
|
/* the LVDS scaling property is not changed */
|
|
|
|
return 0;
|
|
|
|
}
|
2010-08-04 20:50:23 +08:00
|
|
|
intel_lvds->fitting_mode = value;
|
2009-06-22 15:31:25 +08:00
|
|
|
if (crtc && crtc->enabled) {
|
|
|
|
/*
|
|
|
|
* If the CRTC is enabled, the display will be changed
|
|
|
|
* according to the new panel fitting mode.
|
|
|
|
*/
|
|
|
|
drm_crtc_helper_set_mode(crtc, &crtc->mode,
|
|
|
|
crtc->x, crtc->y, crtc->fb);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2009-01-22 20:22:06 +08:00
|
|
|
return 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 06:24:08 +08:00
|
|
|
static const struct drm_encoder_helper_funcs intel_lvds_helper_funcs = {
|
|
|
|
.dpms = intel_lvds_dpms,
|
|
|
|
.mode_fixup = intel_lvds_mode_fixup,
|
|
|
|
.prepare = intel_lvds_prepare,
|
|
|
|
.mode_set = intel_lvds_mode_set,
|
|
|
|
.commit = intel_lvds_commit,
|
|
|
|
};
|
|
|
|
|
|
|
|
static const struct drm_connector_helper_funcs intel_lvds_connector_helper_funcs = {
|
|
|
|
.get_modes = intel_lvds_get_modes,
|
|
|
|
.mode_valid = intel_lvds_mode_valid,
|
2010-09-09 23:20:55 +08:00
|
|
|
.best_encoder = intel_best_encoder,
|
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 06:24:08 +08:00
|
|
|
};
|
|
|
|
|
|
|
|
static const struct drm_connector_funcs intel_lvds_connector_funcs = {
|
2009-05-31 11:42:28 +08:00
|
|
|
.dpms = drm_helper_connector_dpms,
|
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 06:24:08 +08:00
|
|
|
.detect = intel_lvds_detect,
|
|
|
|
.fill_modes = drm_helper_probe_single_connector_modes,
|
2009-01-22 20:22:06 +08:00
|
|
|
.set_property = intel_lvds_set_property,
|
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 06:24:08 +08:00
|
|
|
.destroy = intel_lvds_destroy,
|
|
|
|
};
|
|
|
|
|
|
|
|
static const struct drm_encoder_funcs intel_lvds_enc_funcs = {
|
2010-08-04 20:50:23 +08: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 06:24:08 +08:00
|
|
|
};
|
|
|
|
|
2009-05-05 22:00:25 +08:00
|
|
|
static int __init intel_no_lvds_dmi_callback(const struct dmi_system_id *id)
|
|
|
|
{
|
2009-07-20 13:48:04 +08:00
|
|
|
DRM_DEBUG_KMS("Skipping LVDS initialization for %s\n", id->ident);
|
2009-05-05 22:00:25 +08:00
|
|
|
return 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 06:24:08 +08:00
|
|
|
|
2009-05-05 22:00:25 +08:00
|
|
|
/* These systems claim to have LVDS, but really don't */
|
2009-06-04 07:41:19 +08:00
|
|
|
static const struct dmi_system_id intel_no_lvds[] = {
|
2009-05-05 22:00:25 +08:00
|
|
|
{
|
|
|
|
.callback = intel_no_lvds_dmi_callback,
|
|
|
|
.ident = "Apple Mac Mini (Core series)",
|
|
|
|
.matches = {
|
2009-06-15 03:31:58 +08:00
|
|
|
DMI_MATCH(DMI_SYS_VENDOR, "Apple"),
|
2009-05-05 22:00:25 +08:00
|
|
|
DMI_MATCH(DMI_PRODUCT_NAME, "Macmini1,1"),
|
|
|
|
},
|
|
|
|
},
|
|
|
|
{
|
|
|
|
.callback = intel_no_lvds_dmi_callback,
|
|
|
|
.ident = "Apple Mac Mini (Core 2 series)",
|
|
|
|
.matches = {
|
2009-06-15 03:31:58 +08:00
|
|
|
DMI_MATCH(DMI_SYS_VENDOR, "Apple"),
|
2009-05-05 22:00:25 +08:00
|
|
|
DMI_MATCH(DMI_PRODUCT_NAME, "Macmini2,1"),
|
|
|
|
},
|
|
|
|
},
|
|
|
|
{
|
|
|
|
.callback = intel_no_lvds_dmi_callback,
|
|
|
|
.ident = "MSI IM-945GSE-A",
|
|
|
|
.matches = {
|
|
|
|
DMI_MATCH(DMI_SYS_VENDOR, "MSI"),
|
|
|
|
DMI_MATCH(DMI_PRODUCT_NAME, "A9830IMS"),
|
|
|
|
},
|
|
|
|
},
|
|
|
|
{
|
|
|
|
.callback = intel_no_lvds_dmi_callback,
|
|
|
|
.ident = "Dell Studio Hybrid",
|
|
|
|
.matches = {
|
|
|
|
DMI_MATCH(DMI_SYS_VENDOR, "Dell Inc."),
|
|
|
|
DMI_MATCH(DMI_PRODUCT_NAME, "Studio Hybrid 140g"),
|
|
|
|
},
|
|
|
|
},
|
2009-05-28 05:20:39 +08:00
|
|
|
{
|
|
|
|
.callback = intel_no_lvds_dmi_callback,
|
|
|
|
.ident = "AOpen Mini PC",
|
|
|
|
.matches = {
|
|
|
|
DMI_MATCH(DMI_SYS_VENDOR, "AOpen"),
|
|
|
|
DMI_MATCH(DMI_PRODUCT_NAME, "i965GMx-IF"),
|
|
|
|
},
|
|
|
|
},
|
2009-07-14 04:26:48 +08:00
|
|
|
{
|
|
|
|
.callback = intel_no_lvds_dmi_callback,
|
|
|
|
.ident = "AOpen Mini PC MP915",
|
|
|
|
.matches = {
|
|
|
|
DMI_MATCH(DMI_BOARD_VENDOR, "AOpen"),
|
|
|
|
DMI_MATCH(DMI_BOARD_NAME, "i915GMx-F"),
|
|
|
|
},
|
|
|
|
},
|
2011-01-14 23:38:10 +08:00
|
|
|
{
|
|
|
|
.callback = intel_no_lvds_dmi_callback,
|
|
|
|
.ident = "AOpen i915GMm-HFS",
|
|
|
|
.matches = {
|
|
|
|
DMI_MATCH(DMI_BOARD_VENDOR, "AOpen"),
|
|
|
|
DMI_MATCH(DMI_BOARD_NAME, "i915GMm-HFS"),
|
|
|
|
},
|
|
|
|
},
|
2009-06-06 03:16:22 +08:00
|
|
|
{
|
|
|
|
.callback = intel_no_lvds_dmi_callback,
|
|
|
|
.ident = "Aopen i945GTt-VFA",
|
|
|
|
.matches = {
|
|
|
|
DMI_MATCH(DMI_PRODUCT_VERSION, "AO00001JW"),
|
|
|
|
},
|
|
|
|
},
|
2010-03-29 23:53:12 +08:00
|
|
|
{
|
|
|
|
.callback = intel_no_lvds_dmi_callback,
|
|
|
|
.ident = "Clientron U800",
|
|
|
|
.matches = {
|
|
|
|
DMI_MATCH(DMI_SYS_VENDOR, "Clientron"),
|
|
|
|
DMI_MATCH(DMI_PRODUCT_NAME, "U800"),
|
|
|
|
},
|
|
|
|
},
|
2009-05-05 22:00:25 +08:00
|
|
|
|
|
|
|
{ } /* terminating entry */
|
|
|
|
};
|
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 06:24:08 +08:00
|
|
|
|
2009-11-20 11:24:16 +08:00
|
|
|
/**
|
|
|
|
* intel_find_lvds_downclock - find the reduced downclock for LVDS in EDID
|
|
|
|
* @dev: drm device
|
|
|
|
* @connector: LVDS connector
|
|
|
|
*
|
|
|
|
* Find the reduced downclock for LVDS in EDID.
|
|
|
|
*/
|
|
|
|
static void intel_find_lvds_downclock(struct drm_device *dev,
|
2010-09-13 00:34:41 +08:00
|
|
|
struct drm_display_mode *fixed_mode,
|
|
|
|
struct drm_connector *connector)
|
2009-11-20 11:24:16 +08:00
|
|
|
{
|
|
|
|
struct drm_i915_private *dev_priv = dev->dev_private;
|
2010-09-13 00:34:41 +08:00
|
|
|
struct drm_display_mode *scan;
|
2009-11-20 11:24:16 +08:00
|
|
|
int temp_downclock;
|
|
|
|
|
2010-09-13 00:34:41 +08:00
|
|
|
temp_downclock = fixed_mode->clock;
|
2009-11-20 11:24:16 +08:00
|
|
|
list_for_each_entry(scan, &connector->probed_modes, head) {
|
|
|
|
/*
|
|
|
|
* If one mode has the same resolution with the fixed_panel
|
|
|
|
* mode while they have the different refresh rate, it means
|
|
|
|
* that the reduced downclock is found for the LVDS. In such
|
|
|
|
* case we can set the different FPx0/1 to dynamically select
|
|
|
|
* between low and high frequency.
|
|
|
|
*/
|
2010-09-13 00:34:41 +08:00
|
|
|
if (scan->hdisplay == fixed_mode->hdisplay &&
|
|
|
|
scan->hsync_start == fixed_mode->hsync_start &&
|
|
|
|
scan->hsync_end == fixed_mode->hsync_end &&
|
|
|
|
scan->htotal == fixed_mode->htotal &&
|
|
|
|
scan->vdisplay == fixed_mode->vdisplay &&
|
|
|
|
scan->vsync_start == fixed_mode->vsync_start &&
|
|
|
|
scan->vsync_end == fixed_mode->vsync_end &&
|
|
|
|
scan->vtotal == fixed_mode->vtotal) {
|
2009-11-20 11:24:16 +08:00
|
|
|
if (scan->clock < temp_downclock) {
|
|
|
|
/*
|
|
|
|
* The downclock is already found. But we
|
|
|
|
* expect to find the lower downclock.
|
|
|
|
*/
|
|
|
|
temp_downclock = scan->clock;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
2010-09-13 00:34:41 +08:00
|
|
|
if (temp_downclock < fixed_mode->clock && i915_lvds_downclock) {
|
2009-11-20 11:24:16 +08:00
|
|
|
/* We found the downclock for LVDS. */
|
|
|
|
dev_priv->lvds_downclock_avail = 1;
|
|
|
|
dev_priv->lvds_downclock = temp_downclock;
|
|
|
|
DRM_DEBUG_KMS("LVDS downclock is found in EDID. "
|
2010-09-13 00:34:41 +08:00
|
|
|
"Normal clock %dKhz, downclock %dKhz\n",
|
|
|
|
fixed_mode->clock, temp_downclock);
|
2009-11-20 11:24:16 +08:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2009-11-24 09:48:47 +08:00
|
|
|
/*
|
|
|
|
* Enumerate the child dev array parsed from VBT to check whether
|
|
|
|
* the LVDS is present.
|
|
|
|
* If it is present, return 1.
|
|
|
|
* If it is not present, return false.
|
|
|
|
* If no child dev is parsed from VBT, it assumes that the LVDS is present.
|
|
|
|
*/
|
2010-09-24 08:15:02 +08:00
|
|
|
static bool lvds_is_present_in_vbt(struct drm_device *dev,
|
|
|
|
u8 *i2c_pin)
|
2009-11-24 09:48:47 +08:00
|
|
|
{
|
|
|
|
struct drm_i915_private *dev_priv = dev->dev_private;
|
2010-08-23 01:21:42 +08:00
|
|
|
int i;
|
2009-11-24 09:48:47 +08:00
|
|
|
|
|
|
|
if (!dev_priv->child_dev_num)
|
2010-08-23 01:21:42 +08:00
|
|
|
return true;
|
2009-11-24 09:48:47 +08:00
|
|
|
|
|
|
|
for (i = 0; i < dev_priv->child_dev_num; i++) {
|
2010-08-23 01:21:42 +08:00
|
|
|
struct child_device_config *child = dev_priv->child_dev + i;
|
|
|
|
|
|
|
|
/* If the device type is not LFP, continue.
|
|
|
|
* We have to check both the new identifiers as well as the
|
|
|
|
* old for compatibility with some BIOSes.
|
2009-11-24 09:48:47 +08:00
|
|
|
*/
|
2010-08-23 01:21:42 +08:00
|
|
|
if (child->device_type != DEVICE_TYPE_INT_LFP &&
|
|
|
|
child->device_type != DEVICE_TYPE_LFP)
|
2009-11-24 09:48:47 +08:00
|
|
|
continue;
|
|
|
|
|
2010-09-24 08:15:02 +08:00
|
|
|
if (child->i2c_pin)
|
|
|
|
*i2c_pin = child->i2c_pin;
|
|
|
|
|
2010-08-23 01:21:42 +08:00
|
|
|
/* However, we cannot trust the BIOS writers to populate
|
|
|
|
* the VBT correctly. Since LVDS requires additional
|
|
|
|
* information from AIM blocks, a non-zero addin offset is
|
|
|
|
* a good indicator that the LVDS is actually present.
|
2009-11-24 09:48:47 +08:00
|
|
|
*/
|
2010-08-23 01:21:42 +08:00
|
|
|
if (child->addin_offset)
|
|
|
|
return true;
|
|
|
|
|
|
|
|
/* But even then some BIOS writers perform some black magic
|
|
|
|
* and instantiate the device without reference to any
|
|
|
|
* additional data. Trust that if the VBT was written into
|
|
|
|
* the OpRegion then they have validated the LVDS's existence.
|
|
|
|
*/
|
|
|
|
if (dev_priv->opregion.vbt)
|
|
|
|
return true;
|
2009-11-24 09:48:47 +08:00
|
|
|
}
|
2010-08-23 01:21:42 +08:00
|
|
|
|
|
|
|
return false;
|
2009-11-24 09:48:47 +08:00
|
|
|
}
|
|
|
|
|
2010-09-24 08:15:02 +08:00
|
|
|
static bool intel_lvds_ddc_probe(struct drm_device *dev, u8 pin)
|
2010-09-23 18:16:49 +08:00
|
|
|
{
|
|
|
|
struct drm_i915_private *dev_priv = dev->dev_private;
|
|
|
|
u8 buf = 0;
|
|
|
|
struct i2c_msg msgs[] = {
|
|
|
|
{
|
|
|
|
.addr = 0xA0,
|
|
|
|
.flags = 0,
|
|
|
|
.len = 1,
|
|
|
|
.buf = &buf,
|
|
|
|
},
|
|
|
|
};
|
2010-09-24 08:15:02 +08:00
|
|
|
struct i2c_adapter *i2c = &dev_priv->gmbus[pin].adapter;
|
2010-09-28 23:41:32 +08:00
|
|
|
/* XXX this only appears to work when using GMBUS */
|
|
|
|
if (intel_gmbus_is_forced_bit(i2c))
|
|
|
|
return true;
|
2010-09-23 18:16:49 +08:00
|
|
|
return i2c_transfer(i2c, msgs, 1) == 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 06:24:08 +08:00
|
|
|
/**
|
|
|
|
* intel_lvds_init - setup LVDS connectors on this device
|
|
|
|
* @dev: drm device
|
|
|
|
*
|
|
|
|
* Create the connector, register the LVDS DDC bus, and try to figure out what
|
|
|
|
* modes we can display on the LVDS panel (if present).
|
|
|
|
*/
|
2010-11-30 02:00:23 +08:00
|
|
|
bool intel_lvds_init(struct drm_device *dev)
|
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 06:24:08 +08:00
|
|
|
{
|
|
|
|
struct drm_i915_private *dev_priv = dev->dev_private;
|
2010-08-04 20:50:23 +08:00
|
|
|
struct intel_lvds *intel_lvds;
|
2010-03-26 02:11:14 +08:00
|
|
|
struct intel_encoder *intel_encoder;
|
2010-03-29 16:40:50 +08:00
|
|
|
struct intel_connector *intel_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 06:24:08 +08:00
|
|
|
struct drm_connector *connector;
|
|
|
|
struct drm_encoder *encoder;
|
|
|
|
struct drm_display_mode *scan; /* *modes, *bios_mode; */
|
|
|
|
struct drm_crtc *crtc;
|
|
|
|
u32 lvds;
|
2010-09-24 08:15:02 +08:00
|
|
|
int pipe;
|
|
|
|
u8 pin;
|
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 06:24:08 +08:00
|
|
|
|
2009-05-05 22:00:25 +08:00
|
|
|
/* Skip init on machines we know falsely report LVDS */
|
|
|
|
if (dmi_check_system(intel_no_lvds))
|
2010-11-30 02:00:23 +08:00
|
|
|
return false;
|
2009-02-04 18:05:41 +08:00
|
|
|
|
2010-09-24 08:15:02 +08:00
|
|
|
pin = GMBUS_PORT_PANEL;
|
|
|
|
if (!lvds_is_present_in_vbt(dev, &pin)) {
|
2009-12-16 02:55:24 +08:00
|
|
|
DRM_DEBUG_KMS("LVDS is not present in VBT\n");
|
2010-11-30 02:00:23 +08:00
|
|
|
return false;
|
2009-11-24 23:07:00 +08:00
|
|
|
}
|
2009-06-26 09:46:18 +08:00
|
|
|
|
2010-01-29 08:45:52 +08:00
|
|
|
if (HAS_PCH_SPLIT(dev)) {
|
2009-06-05 15:38:44 +08:00
|
|
|
if ((I915_READ(PCH_LVDS) & LVDS_DETECTED) == 0)
|
2010-11-30 02:00:23 +08:00
|
|
|
return false;
|
2010-09-24 17:24:28 +08:00
|
|
|
if (dev_priv->edp.support) {
|
2009-10-09 11:39:41 +08:00
|
|
|
DRM_DEBUG_KMS("disable LVDS for eDP support\n");
|
2010-11-30 02:00:23 +08:00
|
|
|
return false;
|
2009-07-24 01:00:32 +08:00
|
|
|
}
|
2009-06-05 15:38:44 +08:00
|
|
|
}
|
|
|
|
|
2010-09-24 08:15:02 +08:00
|
|
|
if (!intel_lvds_ddc_probe(dev, pin)) {
|
2010-09-23 18:16:49 +08:00
|
|
|
DRM_DEBUG_KMS("LVDS did not respond to DDC probe\n");
|
2010-11-30 02:00:23 +08:00
|
|
|
return false;
|
2010-09-23 18:16:49 +08:00
|
|
|
}
|
|
|
|
|
2010-08-04 20:50:23 +08:00
|
|
|
intel_lvds = kzalloc(sizeof(struct intel_lvds), GFP_KERNEL);
|
|
|
|
if (!intel_lvds) {
|
2010-11-30 02:00:23 +08:00
|
|
|
return 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 06:24:08 +08:00
|
|
|
}
|
|
|
|
|
2010-03-29 16:40:50 +08:00
|
|
|
intel_connector = kzalloc(sizeof(struct intel_connector), GFP_KERNEL);
|
|
|
|
if (!intel_connector) {
|
2010-08-04 20:50:23 +08:00
|
|
|
kfree(intel_lvds);
|
2010-11-30 02:00:23 +08:00
|
|
|
return false;
|
2010-03-29 16:40:50 +08:00
|
|
|
}
|
|
|
|
|
2010-09-13 08:16:10 +08:00
|
|
|
if (!HAS_PCH_SPLIT(dev)) {
|
|
|
|
intel_lvds->pfit_control = I915_READ(PFIT_CONTROL);
|
|
|
|
}
|
|
|
|
|
2010-08-04 20:50:23 +08:00
|
|
|
intel_encoder = &intel_lvds->base;
|
2010-09-09 22:14:28 +08:00
|
|
|
encoder = &intel_encoder->base;
|
2010-08-04 20:50:23 +08:00
|
|
|
connector = &intel_connector->base;
|
2010-03-29 16:40:50 +08:00
|
|
|
drm_connector_init(dev, &intel_connector->base, &intel_lvds_connector_funcs,
|
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 06:24:08 +08:00
|
|
|
DRM_MODE_CONNECTOR_LVDS);
|
|
|
|
|
2010-09-09 22:14:28 +08:00
|
|
|
drm_encoder_init(dev, &intel_encoder->base, &intel_lvds_enc_funcs,
|
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 06:24:08 +08:00
|
|
|
DRM_MODE_ENCODER_LVDS);
|
|
|
|
|
2010-09-09 23:20:55 +08:00
|
|
|
intel_connector_attach_encoder(intel_connector, intel_encoder);
|
2010-03-26 02:11:14 +08:00
|
|
|
intel_encoder->type = INTEL_OUTPUT_LVDS;
|
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 06:24:08 +08:00
|
|
|
|
2010-03-26 02:11:14 +08:00
|
|
|
intel_encoder->clone_mask = (1 << INTEL_LVDS_CLONE_BIT);
|
|
|
|
intel_encoder->crtc_mask = (1 << 1);
|
2010-12-05 01:49:46 +08:00
|
|
|
if (INTEL_INFO(dev)->gen >= 5)
|
|
|
|
intel_encoder->crtc_mask |= (1 << 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 06:24:08 +08:00
|
|
|
drm_encoder_helper_add(encoder, &intel_lvds_helper_funcs);
|
|
|
|
drm_connector_helper_add(connector, &intel_lvds_connector_helper_funcs);
|
|
|
|
connector->display_info.subpixel_order = SubPixelHorizontalRGB;
|
|
|
|
connector->interlace_allowed = false;
|
|
|
|
connector->doublescan_allowed = false;
|
|
|
|
|
2009-06-22 15:31:25 +08:00
|
|
|
/* create the scaling mode property */
|
|
|
|
drm_mode_create_scaling_mode_property(dev);
|
|
|
|
/*
|
|
|
|
* the initial panel fitting mode will be FULL_SCREEN.
|
|
|
|
*/
|
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 06:24:08 +08:00
|
|
|
|
2010-03-29 16:40:50 +08:00
|
|
|
drm_connector_attach_property(&intel_connector->base,
|
2009-06-22 15:31:25 +08:00
|
|
|
dev->mode_config.scaling_mode_property,
|
2010-06-25 02:05:10 +08:00
|
|
|
DRM_MODE_SCALE_ASPECT);
|
2010-08-04 20:50:23 +08:00
|
|
|
intel_lvds->fitting_mode = DRM_MODE_SCALE_ASPECT;
|
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 06:24:08 +08:00
|
|
|
/*
|
|
|
|
* LVDS discovery:
|
|
|
|
* 1) check for EDID on DDC
|
|
|
|
* 2) check for VBT data
|
|
|
|
* 3) check to see if LVDS is already on
|
|
|
|
* if none of the above, no panel
|
|
|
|
* 4) make sure lid is open
|
|
|
|
* if closed, act like it's not there for now
|
|
|
|
*/
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Attempt to get the fixed panel mode from DDC. Assume that the
|
|
|
|
* preferred mode is the right one.
|
|
|
|
*/
|
2010-09-17 06:05:10 +08:00
|
|
|
intel_lvds->edid = drm_get_edid(connector,
|
2010-09-24 08:15:02 +08:00
|
|
|
&dev_priv->gmbus[pin].adapter);
|
2010-11-09 07:20:52 +08:00
|
|
|
if (intel_lvds->edid) {
|
|
|
|
if (drm_add_edid_modes(connector,
|
|
|
|
intel_lvds->edid)) {
|
|
|
|
drm_mode_connector_update_edid_property(connector,
|
|
|
|
intel_lvds->edid);
|
|
|
|
} else {
|
|
|
|
kfree(intel_lvds->edid);
|
|
|
|
intel_lvds->edid = NULL;
|
|
|
|
}
|
|
|
|
}
|
2010-09-17 06:05:10 +08:00
|
|
|
if (!intel_lvds->edid) {
|
2010-09-13 00:34:41 +08:00
|
|
|
/* Didn't get an EDID, so
|
|
|
|
* Set wide sync ranges so we get all modes
|
|
|
|
* handed to valid_mode for checking
|
|
|
|
*/
|
|
|
|
connector->display_info.min_vfreq = 0;
|
|
|
|
connector->display_info.max_vfreq = 200;
|
|
|
|
connector->display_info.min_hfreq = 0;
|
|
|
|
connector->display_info.max_hfreq = 200;
|
|
|
|
}
|
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 06:24:08 +08:00
|
|
|
|
|
|
|
list_for_each_entry(scan, &connector->probed_modes, head) {
|
|
|
|
if (scan->type & DRM_MODE_TYPE_PREFERRED) {
|
2010-09-13 00:34:41 +08:00
|
|
|
intel_lvds->fixed_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 06:24:08 +08:00
|
|
|
drm_mode_duplicate(dev, scan);
|
2010-09-13 00:34:41 +08:00
|
|
|
intel_find_lvds_downclock(dev,
|
|
|
|
intel_lvds->fixed_mode,
|
|
|
|
connector);
|
2009-02-04 18:05:41 +08:00
|
|
|
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 06:24:08 +08:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Failed to get EDID, what about VBT? */
|
2009-05-13 11:19:55 +08:00
|
|
|
if (dev_priv->lfp_lvds_vbt_mode) {
|
2010-09-13 00:34:41 +08:00
|
|
|
intel_lvds->fixed_mode =
|
2009-05-13 11:19:55 +08:00
|
|
|
drm_mode_duplicate(dev, dev_priv->lfp_lvds_vbt_mode);
|
2010-09-13 00:34:41 +08:00
|
|
|
if (intel_lvds->fixed_mode) {
|
|
|
|
intel_lvds->fixed_mode->type |=
|
2009-01-15 02:53:36 +08:00
|
|
|
DRM_MODE_TYPE_PREFERRED;
|
|
|
|
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 06:24:08 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* If we didn't get EDID, try checking if the panel is already turned
|
|
|
|
* on. If so, assume that whatever is currently programmed is the
|
|
|
|
* correct mode.
|
|
|
|
*/
|
2009-06-05 15:38:44 +08:00
|
|
|
|
2009-12-04 06:14:42 +08:00
|
|
|
/* Ironlake: FIXME if still fail, not try pipe mode now */
|
2010-01-29 08:45:52 +08:00
|
|
|
if (HAS_PCH_SPLIT(dev))
|
2009-06-05 15:38:44 +08:00
|
|
|
goto failed;
|
|
|
|
|
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 06:24:08 +08:00
|
|
|
lvds = I915_READ(LVDS);
|
|
|
|
pipe = (lvds & LVDS_PIPEB_SELECT) ? 1 : 0;
|
2010-09-09 22:44:14 +08:00
|
|
|
crtc = intel_get_crtc_for_pipe(dev, 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 06:24:08 +08:00
|
|
|
|
|
|
|
if (crtc && (lvds & LVDS_PORT_EN)) {
|
2010-09-13 00:34:41 +08:00
|
|
|
intel_lvds->fixed_mode = intel_crtc_mode_get(dev, crtc);
|
|
|
|
if (intel_lvds->fixed_mode) {
|
|
|
|
intel_lvds->fixed_mode->type |=
|
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 06:24:08 +08:00
|
|
|
DRM_MODE_TYPE_PREFERRED;
|
2009-02-04 18:05:41 +08:00
|
|
|
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 06:24:08 +08:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/* If we still don't have a mode after all that, give up. */
|
2010-09-13 00:34:41 +08:00
|
|
|
if (!intel_lvds->fixed_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 06:24:08 +08:00
|
|
|
goto failed;
|
|
|
|
|
|
|
|
out:
|
2010-01-29 08:45:52 +08:00
|
|
|
if (HAS_PCH_SPLIT(dev)) {
|
2009-06-05 15:38:44 +08:00
|
|
|
u32 pwm;
|
2010-12-04 04:17:19 +08:00
|
|
|
|
|
|
|
pipe = (I915_READ(PCH_LVDS) & LVDS_PIPEB_SELECT) ? 1 : 0;
|
|
|
|
|
|
|
|
/* make sure PWM is enabled and locked to the LVDS pipe */
|
2009-06-05 15:38:44 +08:00
|
|
|
pwm = I915_READ(BLC_PWM_CPU_CTL2);
|
2010-12-04 04:17:19 +08:00
|
|
|
if (pipe == 0 && (pwm & PWM_PIPE_B))
|
|
|
|
I915_WRITE(BLC_PWM_CPU_CTL2, pwm & ~PWM_ENABLE);
|
|
|
|
if (pipe)
|
|
|
|
pwm |= PWM_PIPE_B;
|
|
|
|
else
|
|
|
|
pwm &= ~PWM_PIPE_B;
|
|
|
|
I915_WRITE(BLC_PWM_CPU_CTL2, pwm | PWM_ENABLE);
|
2009-06-05 15:38:44 +08:00
|
|
|
|
|
|
|
pwm = I915_READ(BLC_PWM_PCH_CTL1);
|
|
|
|
pwm |= PWM_PCH_ENABLE;
|
|
|
|
I915_WRITE(BLC_PWM_PCH_CTL1, pwm);
|
|
|
|
}
|
2009-09-11 06:28:03 +08:00
|
|
|
dev_priv->lid_notifier.notifier_call = intel_lid_notify;
|
|
|
|
if (acpi_lid_notifier_register(&dev_priv->lid_notifier)) {
|
2009-10-09 11:39:41 +08:00
|
|
|
DRM_DEBUG_KMS("lid notifier registration failed\n");
|
2009-09-11 06:28:03 +08:00
|
|
|
dev_priv->lid_notifier.notifier_call = NULL;
|
|
|
|
}
|
drm/i915: Update LVDS connector status when receiving ACPI LID event
Dirk reports that nothing is displayed on LVDS when using ubuntu 9.1 after
close/reopen the LID. And I also reproduce this issue on another laptop.
After some tests and debug, it seems that it is related with that the
LVDS status is not updated in time in course of suspend/resume.
Now the LID state is used to check whether the LVDS is connected or
disconnected. And when the LID is closed, it means that the LVDS is
disconnected. When it is reopened, it means that the LVDS is connected.
At the same time on some distributions the LID event is also used to put
the system into suspend state. When the LID is closed, the system will enter
the suspend state. When the LID is reopened, the system will be resumed.
In such case when the LID is closed, user-space script will receive the LID
notification event and detect the LVDS as disconnected. Then the system will
enter the suspended state. When the LID is reopened, the system will be
resumed. As the LVDS status is not updated in course of resume, it will cause
that the LVDS connector is marked as unused and disabled. After the resume is
finished,user-space script will try to configure the display mode for LVDS.
But unfortunately as the LVDS status is not updated in time and it is still
marked as disconnected, the LVDS and its corresponding CRTC will be disabled
again in the function of drm_helper_disable_unused_functions after changing
mode for LVDS.
So we had better check and update the status of LVDS connector after receiving
the LID notication event. Then after the system is resumed from suspended
state, we can set the display mode for LVDS correctly.
Signed-off-by: Zhao Yakui <yakui.zhao@intel.com>
Reported-by: Dirk Hohndel <hohndel@infradead.org>
Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>
CC: stable@kernel.org
Signed-off-by: Eric Anholt <eric@anholt.net>
2009-12-11 09:26:11 +08:00
|
|
|
/* keep the LVDS connector */
|
|
|
|
dev_priv->int_lvds_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 06:24:08 +08:00
|
|
|
drm_sysfs_connector_add(connector);
|
2010-11-30 02:00:23 +08:00
|
|
|
return true;
|
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 06:24:08 +08:00
|
|
|
|
|
|
|
failed:
|
2009-07-20 13:48:04 +08:00
|
|
|
DRM_DEBUG_KMS("No LVDS modes found, disabling.\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 06:24:08 +08:00
|
|
|
drm_connector_cleanup(connector);
|
2009-11-17 17:19:23 +08:00
|
|
|
drm_encoder_cleanup(encoder);
|
2010-08-04 20:50:23 +08:00
|
|
|
kfree(intel_lvds);
|
2010-03-29 16:40:50 +08:00
|
|
|
kfree(intel_connector);
|
2010-11-30 02:00:23 +08:00
|
|
|
return 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 06:24:08 +08:00
|
|
|
}
|