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-07 15:24:08 -07:00
|
|
|
/*
|
|
|
|
* Copyright 2006 Dave Airlie <airlied@linux.ie>
|
|
|
|
* Copyright © 2006-2007 Intel Corporation
|
|
|
|
* Jesse Barnes <jesse.barnes@intel.com>
|
|
|
|
*
|
|
|
|
* 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>
|
|
|
|
*/
|
|
|
|
#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 02:04:11 -06: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-07 15:24:08 -07:00
|
|
|
#include <linux/delay.h>
|
2011-08-30 16:16:33 -06:00
|
|
|
#include <linux/export.h>
|
2012-10-02 11:01:07 -06:00
|
|
|
#include <drm/drmP.h>
|
|
|
|
#include <drm/drm_crtc.h>
|
|
|
|
#include <drm/drm_edid.h>
|
2010-08-04 06:50:23 -06:00
|
|
|
#include "intel_drv.h"
|
2012-10-02 11:01:07 -06:00
|
|
|
#include <drm/i915_drm.h>
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-07 15:24:08 -07:00
|
|
|
#include "i915_drv.h"
|
|
|
|
#include "intel_sdvo_regs.h"
|
|
|
|
|
2010-03-30 00:06:33 -06:00
|
|
|
#define SDVO_TMDS_MASK (SDVO_OUTPUT_TMDS0 | SDVO_OUTPUT_TMDS1)
|
|
|
|
#define SDVO_RGB_MASK (SDVO_OUTPUT_RGB0 | SDVO_OUTPUT_RGB1)
|
|
|
|
#define SDVO_LVDS_MASK (SDVO_OUTPUT_LVDS0 | SDVO_OUTPUT_LVDS1)
|
2011-09-30 15:56:41 -06:00
|
|
|
#define SDVO_TV_MASK (SDVO_OUTPUT_CVBS0 | SDVO_OUTPUT_SVID0 | SDVO_OUTPUT_YPRPB0)
|
2010-03-30 00:06:33 -06:00
|
|
|
|
|
|
|
#define SDVO_OUTPUT_MASK (SDVO_TMDS_MASK | SDVO_RGB_MASK | SDVO_LVDS_MASK |\
|
2011-08-16 13:34:10 -06:00
|
|
|
SDVO_TV_MASK)
|
2010-03-30 00:06:33 -06:00
|
|
|
|
|
|
|
#define IS_TV(c) (c->output_flag & SDVO_TV_MASK)
|
2011-02-09 13:01:16 -07:00
|
|
|
#define IS_TMDS(c) (c->output_flag & SDVO_TMDS_MASK)
|
2010-03-30 00:06:33 -06:00
|
|
|
#define IS_LVDS(c) (c->output_flag & SDVO_LVDS_MASK)
|
2010-08-04 06:50:25 -06:00
|
|
|
#define IS_TV_OR_LVDS(c) (c->output_flag & (SDVO_TV_MASK | SDVO_LVDS_MASK))
|
2011-06-20 07:45:50 -06:00
|
|
|
#define IS_DIGITAL(c) (c->output_flag & (SDVO_TMDS_MASK | SDVO_LVDS_MASK))
|
2010-03-30 00:06:33 -06: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-07 15:24:08 -07:00
|
|
|
|
2010-08-07 04:01:27 -06:00
|
|
|
static const char *tv_format_names[] = {
|
2009-08-23 23:50:26 -06:00
|
|
|
"NTSC_M" , "NTSC_J" , "NTSC_443",
|
|
|
|
"PAL_B" , "PAL_D" , "PAL_G" ,
|
|
|
|
"PAL_H" , "PAL_I" , "PAL_M" ,
|
|
|
|
"PAL_N" , "PAL_NC" , "PAL_60" ,
|
|
|
|
"SECAM_B" , "SECAM_D" , "SECAM_G" ,
|
|
|
|
"SECAM_K" , "SECAM_K1", "SECAM_L" ,
|
|
|
|
"SECAM_60"
|
|
|
|
};
|
|
|
|
|
|
|
|
#define TV_FORMAT_NUM (sizeof(tv_format_names) / sizeof(*tv_format_names))
|
|
|
|
|
2010-08-04 06:50:23 -06:00
|
|
|
struct intel_sdvo {
|
|
|
|
struct intel_encoder base;
|
|
|
|
|
2010-07-20 16:44:45 -06:00
|
|
|
struct i2c_adapter *i2c;
|
2009-05-30 13:16:25 -06:00
|
|
|
u8 slave_addr;
|
2009-02-02 16:11:52 -07:00
|
|
|
|
2010-09-24 05:52:03 -06:00
|
|
|
struct i2c_adapter ddc;
|
|
|
|
|
2009-02-02 16:11:52 -07:00
|
|
|
/* Register for the SDVO device: SDVOB or SDVOC */
|
2012-03-23 16:43:35 -06:00
|
|
|
uint32_t sdvo_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-07 15:24:08 -07:00
|
|
|
|
2009-02-02 16:11:52 -07:00
|
|
|
/* Active outputs controlled by this SDVO output */
|
|
|
|
uint16_t controlled_output;
|
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-07 15:24:08 -07:00
|
|
|
|
2009-02-02 16:11:52 -07:00
|
|
|
/*
|
|
|
|
* Capabilities of the SDVO device returned by
|
2013-06-10 06:28:42 -06:00
|
|
|
* intel_sdvo_get_capabilities()
|
2009-02-02 16:11:52 -07:00
|
|
|
*/
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-07 15:24:08 -07:00
|
|
|
struct intel_sdvo_caps caps;
|
2009-02-02 16:11:52 -07:00
|
|
|
|
|
|
|
/* Pixel clock limitations reported by the SDVO device, in kHz */
|
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-07 15:24:08 -07:00
|
|
|
int pixel_clock_min, pixel_clock_max;
|
|
|
|
|
2009-07-23 03:11:34 -06:00
|
|
|
/*
|
|
|
|
* For multiple function SDVO device,
|
|
|
|
* this is for current attached outputs.
|
|
|
|
*/
|
|
|
|
uint16_t attached_output;
|
|
|
|
|
2011-09-21 10:13:30 -06:00
|
|
|
/*
|
|
|
|
* Hotplug activation bits for this device
|
|
|
|
*/
|
2012-08-29 07:43:58 -06:00
|
|
|
uint16_t hotplug_active;
|
2011-09-21 10:13:30 -06:00
|
|
|
|
2011-02-21 15:23:52 -07:00
|
|
|
/**
|
|
|
|
* This is used to select the color range of RBG outputs in HDMI mode.
|
|
|
|
* It is only valid when using TMDS encoding and 8 bit per color mode.
|
|
|
|
*/
|
|
|
|
uint32_t color_range;
|
2013-01-17 07:31:29 -07:00
|
|
|
bool color_range_auto;
|
2011-02-21 15:23:52 -07:00
|
|
|
|
2009-02-02 16:11:52 -07:00
|
|
|
/**
|
|
|
|
* This is set if we're going to treat the device as TV-out.
|
|
|
|
*
|
|
|
|
* While we have these nice friendly flags for output types that ought
|
|
|
|
* to decide this for us, the S-Video output on our HDMI+S-Video card
|
|
|
|
* shows up as RGB1 (VGA).
|
|
|
|
*/
|
|
|
|
bool is_tv;
|
|
|
|
|
2012-03-23 16:43:35 -06:00
|
|
|
/* On different gens SDVOB is at different places. */
|
|
|
|
bool is_sdvob;
|
|
|
|
|
2009-08-23 23:50:26 -06:00
|
|
|
/* This is for current tv format name */
|
2010-08-04 06:50:26 -06:00
|
|
|
int tv_format_index;
|
2009-08-23 23:50:26 -06:00
|
|
|
|
2009-02-02 16:11:52 -07:00
|
|
|
/**
|
|
|
|
* This is set if we treat the device as HDMI, instead of DVI.
|
|
|
|
*/
|
|
|
|
bool is_hdmi;
|
2010-11-22 04:12:46 -07:00
|
|
|
bool has_hdmi_monitor;
|
|
|
|
bool has_hdmi_audio;
|
2013-01-17 07:31:31 -07:00
|
|
|
bool rgb_quant_range_selectable;
|
2009-06-29 21:35:35 -06:00
|
|
|
|
2009-05-12 21:20:06 -06:00
|
|
|
/**
|
2010-08-25 03:05:17 -06:00
|
|
|
* This is set if we detect output of sdvo device as LVDS and
|
|
|
|
* have a valid fixed mode to use with the panel.
|
2009-05-12 21:20:06 -06:00
|
|
|
*/
|
|
|
|
bool is_lvds;
|
2009-02-02 16:11:52 -07:00
|
|
|
|
2009-06-29 21:35:35 -06:00
|
|
|
/**
|
|
|
|
* This is sdvo fixed pannel mode pointer
|
|
|
|
*/
|
|
|
|
struct drm_display_mode *sdvo_lvds_fixed_mode;
|
|
|
|
|
2010-03-25 12:48:48 -06:00
|
|
|
/* DDC bus used by this SDVO encoder */
|
2009-02-02 16:11:52 -07:00
|
|
|
uint8_t ddc_bus;
|
2012-10-13 06:29:31 -06:00
|
|
|
|
|
|
|
/*
|
|
|
|
* the sdvo flag gets lost in round trip: dtd->adjusted_mode->dtd
|
|
|
|
*/
|
|
|
|
uint8_t dtd_sdvo_flags;
|
2010-03-30 00:06:33 -06:00
|
|
|
};
|
|
|
|
|
|
|
|
struct intel_sdvo_connector {
|
2010-08-04 06:50:24 -06:00
|
|
|
struct intel_connector base;
|
|
|
|
|
2010-03-30 00:06:33 -06:00
|
|
|
/* Mark the type of connector */
|
|
|
|
uint16_t output_flag;
|
|
|
|
|
2012-02-23 09:14:47 -07:00
|
|
|
enum hdmi_force_audio force_audio;
|
2010-09-19 02:29:33 -06:00
|
|
|
|
2010-03-30 00:06:33 -06:00
|
|
|
/* This contains all current supported TV format */
|
2010-08-04 06:50:26 -06:00
|
|
|
u8 tv_format_supported[TV_FORMAT_NUM];
|
2010-03-30 00:06:33 -06:00
|
|
|
int format_supported_num;
|
2010-08-04 06:50:28 -06:00
|
|
|
struct drm_property *tv_format;
|
2010-03-30 00:06:33 -06:00
|
|
|
|
2009-09-10 01:45:46 -06:00
|
|
|
/* add the property for the SDVO-TV */
|
2010-08-04 06:50:28 -06:00
|
|
|
struct drm_property *left;
|
|
|
|
struct drm_property *right;
|
|
|
|
struct drm_property *top;
|
|
|
|
struct drm_property *bottom;
|
|
|
|
struct drm_property *hpos;
|
|
|
|
struct drm_property *vpos;
|
|
|
|
struct drm_property *contrast;
|
|
|
|
struct drm_property *saturation;
|
|
|
|
struct drm_property *hue;
|
|
|
|
struct drm_property *sharpness;
|
|
|
|
struct drm_property *flicker_filter;
|
|
|
|
struct drm_property *flicker_filter_adaptive;
|
|
|
|
struct drm_property *flicker_filter_2d;
|
|
|
|
struct drm_property *tv_chroma_filter;
|
|
|
|
struct drm_property *tv_luma_filter;
|
2010-08-04 06:50:29 -06:00
|
|
|
struct drm_property *dot_crawl;
|
2009-09-10 01:45:46 -06:00
|
|
|
|
|
|
|
/* add the property for the SDVO-TV/LVDS */
|
2010-08-04 06:50:28 -06:00
|
|
|
struct drm_property *brightness;
|
2009-09-10 01:45:46 -06:00
|
|
|
|
|
|
|
/* Add variable to record current setting for the above property */
|
|
|
|
u32 left_margin, right_margin, top_margin, bottom_margin;
|
2010-08-04 06:50:28 -06:00
|
|
|
|
2009-09-10 01:45:46 -06:00
|
|
|
/* this is to get the range of margin.*/
|
|
|
|
u32 max_hscan, max_vscan;
|
|
|
|
u32 max_hpos, cur_hpos;
|
|
|
|
u32 max_vpos, cur_vpos;
|
|
|
|
u32 cur_brightness, max_brightness;
|
|
|
|
u32 cur_contrast, max_contrast;
|
|
|
|
u32 cur_saturation, max_saturation;
|
|
|
|
u32 cur_hue, max_hue;
|
2010-08-04 06:50:28 -06:00
|
|
|
u32 cur_sharpness, max_sharpness;
|
|
|
|
u32 cur_flicker_filter, max_flicker_filter;
|
|
|
|
u32 cur_flicker_filter_adaptive, max_flicker_filter_adaptive;
|
|
|
|
u32 cur_flicker_filter_2d, max_flicker_filter_2d;
|
|
|
|
u32 cur_tv_chroma_filter, max_tv_chroma_filter;
|
|
|
|
u32 cur_tv_luma_filter, max_tv_luma_filter;
|
2010-08-04 06:50:29 -06:00
|
|
|
u32 cur_dot_crawl, max_dot_crawl;
|
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-07 15:24:08 -07:00
|
|
|
};
|
|
|
|
|
2010-09-14 09:46:59 -06:00
|
|
|
static struct intel_sdvo *to_intel_sdvo(struct drm_encoder *encoder)
|
2010-08-04 06:50:23 -06:00
|
|
|
{
|
2010-09-09 08:14:28 -06:00
|
|
|
return container_of(encoder, struct intel_sdvo, base.base);
|
2010-08-04 06:50:23 -06:00
|
|
|
}
|
|
|
|
|
2010-09-09 09:20:55 -06:00
|
|
|
static struct intel_sdvo *intel_attached_sdvo(struct drm_connector *connector)
|
|
|
|
{
|
|
|
|
return container_of(intel_attached_encoder(connector),
|
|
|
|
struct intel_sdvo, base);
|
|
|
|
}
|
|
|
|
|
2010-08-04 06:50:24 -06:00
|
|
|
static struct intel_sdvo_connector *to_intel_sdvo_connector(struct drm_connector *connector)
|
|
|
|
{
|
|
|
|
return container_of(to_intel_connector(connector), struct intel_sdvo_connector, base);
|
|
|
|
}
|
|
|
|
|
2009-07-23 03:11:34 -06:00
|
|
|
static bool
|
2010-08-04 06:50:23 -06:00
|
|
|
intel_sdvo_output_setup(struct intel_sdvo *intel_sdvo, uint16_t flags);
|
2010-08-04 06:50:25 -06:00
|
|
|
static bool
|
|
|
|
intel_sdvo_tv_create_property(struct intel_sdvo *intel_sdvo,
|
|
|
|
struct intel_sdvo_connector *intel_sdvo_connector,
|
|
|
|
int type);
|
|
|
|
static bool
|
|
|
|
intel_sdvo_create_enhance_property(struct intel_sdvo *intel_sdvo,
|
|
|
|
struct intel_sdvo_connector *intel_sdvo_connector);
|
2009-07-23 03:11:34 -06: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-07 15:24:08 -07:00
|
|
|
/**
|
|
|
|
* Writes the SDVOB or SDVOC with the given value, but always writes both
|
|
|
|
* SDVOB and SDVOC to work around apparent hardware issues (according to
|
|
|
|
* comments in the BIOS).
|
|
|
|
*/
|
2010-08-04 06:50:23 -06:00
|
|
|
static void intel_sdvo_write_sdvox(struct intel_sdvo *intel_sdvo, u32 val)
|
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-07 15:24:08 -07:00
|
|
|
{
|
2010-09-09 08:14:28 -06:00
|
|
|
struct drm_device *dev = intel_sdvo->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-07 15:24:08 -07:00
|
|
|
struct drm_i915_private *dev_priv = dev->dev_private;
|
|
|
|
u32 bval = val, cval = val;
|
|
|
|
int i;
|
|
|
|
|
2010-08-04 06:50:23 -06:00
|
|
|
if (intel_sdvo->sdvo_reg == PCH_SDVOB) {
|
|
|
|
I915_WRITE(intel_sdvo->sdvo_reg, val);
|
|
|
|
I915_READ(intel_sdvo->sdvo_reg);
|
2010-03-30 01:11:33 -06:00
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
drm/i915: clarify confusion between SDVO and HDMI registers
Some HDMI registers can be used for SDVO, so saying "HDMIB" should be
the same as saying "SDVOB" for a given HW generation. This was not
true and led to confusions and even a regression.
Previously we had:
- SDVO{B,C} defined as the Gen3+ registers
- HDMI{B,C,D} and PCH_SDVOB defined as the PCH registers
But now:
- SDVO{B,C} became GEN3_SDVO{B,C} on SDVO code
- SDVO{B,C} became GEN4_HDMI{B,C} on HDMI code
- HDMI{B,C,D} became PCH_HDMI{B,C,D}
- PCH_SDVOB is still the same thing
v2: Rebase (v1 was sent in May 2012).
Signed-off-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
2013-02-18 15:00:27 -07:00
|
|
|
if (intel_sdvo->sdvo_reg == GEN3_SDVOB)
|
|
|
|
cval = I915_READ(GEN3_SDVOC);
|
|
|
|
else
|
|
|
|
bval = I915_READ(GEN3_SDVOB);
|
|
|
|
|
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-07 15:24:08 -07:00
|
|
|
/*
|
|
|
|
* Write the registers twice for luck. Sometimes,
|
|
|
|
* writing them only once doesn't appear to 'stick'.
|
|
|
|
* The BIOS does this too. Yay, magic
|
|
|
|
*/
|
|
|
|
for (i = 0; i < 2; i++)
|
|
|
|
{
|
drm/i915: clarify confusion between SDVO and HDMI registers
Some HDMI registers can be used for SDVO, so saying "HDMIB" should be
the same as saying "SDVOB" for a given HW generation. This was not
true and led to confusions and even a regression.
Previously we had:
- SDVO{B,C} defined as the Gen3+ registers
- HDMI{B,C,D} and PCH_SDVOB defined as the PCH registers
But now:
- SDVO{B,C} became GEN3_SDVO{B,C} on SDVO code
- SDVO{B,C} became GEN4_HDMI{B,C} on HDMI code
- HDMI{B,C,D} became PCH_HDMI{B,C,D}
- PCH_SDVOB is still the same thing
v2: Rebase (v1 was sent in May 2012).
Signed-off-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
2013-02-18 15:00:27 -07:00
|
|
|
I915_WRITE(GEN3_SDVOB, bval);
|
|
|
|
I915_READ(GEN3_SDVOB);
|
|
|
|
I915_WRITE(GEN3_SDVOC, cval);
|
|
|
|
I915_READ(GEN3_SDVOC);
|
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-07 15:24:08 -07:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2010-08-04 06:50:25 -06:00
|
|
|
static bool intel_sdvo_read_byte(struct intel_sdvo *intel_sdvo, u8 addr, u8 *ch)
|
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-07 15:24:08 -07:00
|
|
|
{
|
|
|
|
struct i2c_msg msgs[] = {
|
|
|
|
{
|
2010-09-24 05:52:03 -06:00
|
|
|
.addr = intel_sdvo->slave_addr,
|
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-07 15:24:08 -07:00
|
|
|
.flags = 0,
|
|
|
|
.len = 1,
|
2010-09-24 05:52:03 -06:00
|
|
|
.buf = &addr,
|
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-07 15:24:08 -07:00
|
|
|
},
|
|
|
|
{
|
2010-09-24 05:52:03 -06:00
|
|
|
.addr = intel_sdvo->slave_addr,
|
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-07 15:24:08 -07:00
|
|
|
.flags = I2C_M_RD,
|
|
|
|
.len = 1,
|
2010-09-24 05:52:03 -06:00
|
|
|
.buf = ch,
|
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-07 15:24:08 -07:00
|
|
|
}
|
|
|
|
};
|
2010-08-04 06:50:25 -06:00
|
|
|
int ret;
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-07 15:24:08 -07:00
|
|
|
|
2010-07-20 16:44:45 -06:00
|
|
|
if ((ret = i2c_transfer(intel_sdvo->i2c, msgs, 2)) == 2)
|
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-07 15:24:08 -07:00
|
|
|
return true;
|
|
|
|
|
2009-07-19 23:48:04 -06:00
|
|
|
DRM_DEBUG_KMS("i2c transfer returned %d\n", ret);
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-07 15:24:08 -07:00
|
|
|
return false;
|
|
|
|
}
|
|
|
|
|
|
|
|
#define SDVO_CMD_NAME_ENTRY(cmd) {cmd, #cmd}
|
|
|
|
/** Mapping of command numbers to names, for debug output */
|
2009-02-09 14:02:42 -07:00
|
|
|
static const struct _sdvo_cmd_name {
|
2009-02-02 16:11:52 -07:00
|
|
|
u8 cmd;
|
2010-08-07 04:01:27 -06:00
|
|
|
const char *name;
|
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-07 15:24:08 -07:00
|
|
|
} sdvo_cmd_names[] = {
|
2011-08-16 13:34:10 -06:00
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_RESET),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_DEVICE_CAPS),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_FIRMWARE_REV),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_TRAINED_INPUTS),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_ACTIVE_OUTPUTS),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_SET_ACTIVE_OUTPUTS),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_IN_OUT_MAP),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_SET_IN_OUT_MAP),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_ATTACHED_DISPLAYS),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_HOT_PLUG_SUPPORT),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_SET_ACTIVE_HOT_PLUG),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_ACTIVE_HOT_PLUG),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_INTERRUPT_EVENT_SOURCE),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_SET_TARGET_INPUT),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_SET_TARGET_OUTPUT),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_INPUT_TIMINGS_PART1),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_INPUT_TIMINGS_PART2),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_SET_INPUT_TIMINGS_PART1),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_SET_INPUT_TIMINGS_PART2),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_SET_INPUT_TIMINGS_PART1),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_SET_OUTPUT_TIMINGS_PART1),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_SET_OUTPUT_TIMINGS_PART2),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_OUTPUT_TIMINGS_PART1),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_OUTPUT_TIMINGS_PART2),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_CREATE_PREFERRED_INPUT_TIMING),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_PREFERRED_INPUT_TIMING_PART1),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_PREFERRED_INPUT_TIMING_PART2),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_INPUT_PIXEL_CLOCK_RANGE),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_OUTPUT_PIXEL_CLOCK_RANGE),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_SUPPORTED_CLOCK_RATE_MULTS),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_CLOCK_RATE_MULT),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_SET_CLOCK_RATE_MULT),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_SUPPORTED_TV_FORMATS),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_TV_FORMAT),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_SET_TV_FORMAT),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_SUPPORTED_POWER_STATES),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_POWER_STATE),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_SET_ENCODER_POWER_STATE),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_SET_DISPLAY_POWER_STATE),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_SET_CONTROL_BUS_SWITCH),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_SDTV_RESOLUTION_SUPPORT),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_SCALED_HDTV_RESOLUTION_SUPPORT),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_SUPPORTED_ENHANCEMENTS),
|
|
|
|
|
|
|
|
/* Add the op code for SDVO enhancements */
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_MAX_HPOS),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_HPOS),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_SET_HPOS),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_MAX_VPOS),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_VPOS),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_SET_VPOS),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_MAX_SATURATION),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_SATURATION),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_SET_SATURATION),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_MAX_HUE),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_HUE),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_SET_HUE),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_MAX_CONTRAST),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_CONTRAST),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_SET_CONTRAST),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_MAX_BRIGHTNESS),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_BRIGHTNESS),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_SET_BRIGHTNESS),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_MAX_OVERSCAN_H),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_OVERSCAN_H),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_SET_OVERSCAN_H),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_MAX_OVERSCAN_V),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_OVERSCAN_V),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_SET_OVERSCAN_V),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_MAX_FLICKER_FILTER),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_FLICKER_FILTER),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_SET_FLICKER_FILTER),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_MAX_FLICKER_FILTER_ADAPTIVE),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_FLICKER_FILTER_ADAPTIVE),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_SET_FLICKER_FILTER_ADAPTIVE),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_MAX_FLICKER_FILTER_2D),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_FLICKER_FILTER_2D),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_SET_FLICKER_FILTER_2D),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_MAX_SHARPNESS),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_SHARPNESS),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_SET_SHARPNESS),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_DOT_CRAWL),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_SET_DOT_CRAWL),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_MAX_TV_CHROMA_FILTER),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_TV_CHROMA_FILTER),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_SET_TV_CHROMA_FILTER),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_MAX_TV_LUMA_FILTER),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_TV_LUMA_FILTER),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_SET_TV_LUMA_FILTER),
|
|
|
|
|
|
|
|
/* HDMI op code */
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_SUPP_ENCODE),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_ENCODE),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_SET_ENCODE),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_SET_PIXEL_REPLI),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_PIXEL_REPLI),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_COLORIMETRY_CAP),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_SET_COLORIMETRY),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_COLORIMETRY),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_AUDIO_ENCRYPT_PREFER),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_SET_AUDIO_STAT),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_AUDIO_STAT),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_HBUF_INDEX),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_SET_HBUF_INDEX),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_HBUF_INFO),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_HBUF_AV_SPLIT),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_SET_HBUF_AV_SPLIT),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_HBUF_TXRATE),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_SET_HBUF_TXRATE),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_SET_HBUF_DATA),
|
|
|
|
SDVO_CMD_NAME_ENTRY(SDVO_CMD_GET_HBUF_DATA),
|
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-07 15:24:08 -07:00
|
|
|
};
|
|
|
|
|
2012-03-23 16:43:35 -06:00
|
|
|
#define SDVO_NAME(svdo) ((svdo)->is_sdvob ? "SDVOB" : "SDVOC")
|
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-07 15:24:08 -07:00
|
|
|
|
2010-08-04 06:50:23 -06:00
|
|
|
static void intel_sdvo_debug_write(struct intel_sdvo *intel_sdvo, u8 cmd,
|
2010-08-04 06:50:25 -06:00
|
|
|
const void *args, int args_len)
|
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-07 15:24:08 -07:00
|
|
|
{
|
|
|
|
int i;
|
|
|
|
|
2009-07-19 23:48:04 -06:00
|
|
|
DRM_DEBUG_KMS("%s: W: %02X ",
|
2010-08-04 06:50:23 -06:00
|
|
|
SDVO_NAME(intel_sdvo), cmd);
|
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-07 15:24:08 -07:00
|
|
|
for (i = 0; i < args_len; i++)
|
2009-06-02 00:12:00 -06:00
|
|
|
DRM_LOG_KMS("%02X ", ((u8 *)args)[i]);
|
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-07 15:24:08 -07:00
|
|
|
for (; i < 8; i++)
|
2009-06-02 00:12:00 -06:00
|
|
|
DRM_LOG_KMS(" ");
|
2010-06-28 05:54:56 -06:00
|
|
|
for (i = 0; i < ARRAY_SIZE(sdvo_cmd_names); i++) {
|
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-07 15:24:08 -07:00
|
|
|
if (cmd == sdvo_cmd_names[i].cmd) {
|
2009-06-02 00:12:00 -06:00
|
|
|
DRM_LOG_KMS("(%s)", sdvo_cmd_names[i].name);
|
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-07 15:24:08 -07:00
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
2010-06-28 05:54:56 -06:00
|
|
|
if (i == ARRAY_SIZE(sdvo_cmd_names))
|
2009-06-02 00:12:00 -06:00
|
|
|
DRM_LOG_KMS("(%02X)", cmd);
|
|
|
|
DRM_LOG_KMS("\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-07 15:24:08 -07:00
|
|
|
}
|
|
|
|
|
2010-09-24 05:52:03 -06:00
|
|
|
static const char *cmd_status_names[] = {
|
|
|
|
"Power on",
|
|
|
|
"Success",
|
|
|
|
"Not supported",
|
|
|
|
"Invalid arg",
|
|
|
|
"Pending",
|
|
|
|
"Target not specified",
|
|
|
|
"Scaling not supported"
|
|
|
|
};
|
|
|
|
|
2010-08-04 06:50:25 -06:00
|
|
|
static bool intel_sdvo_write_cmd(struct intel_sdvo *intel_sdvo, u8 cmd,
|
|
|
|
const void *args, int args_len)
|
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-07 15:24:08 -07:00
|
|
|
{
|
2012-04-16 15:07:41 -06:00
|
|
|
u8 *buf, status;
|
|
|
|
struct i2c_msg *msgs;
|
|
|
|
int i, ret = true;
|
|
|
|
|
2012-07-25 06:51:04 -06:00
|
|
|
/* Would be simpler to allocate both in one go ? */
|
2013-03-10 06:22:48 -06:00
|
|
|
buf = kzalloc(args_len * 2 + 2, GFP_KERNEL);
|
2012-04-16 15:07:41 -06:00
|
|
|
if (!buf)
|
|
|
|
return false;
|
|
|
|
|
|
|
|
msgs = kcalloc(args_len + 3, sizeof(*msgs), GFP_KERNEL);
|
2012-07-25 06:51:04 -06:00
|
|
|
if (!msgs) {
|
|
|
|
kfree(buf);
|
2012-04-16 15:07:41 -06:00
|
|
|
return false;
|
2012-07-25 06:51:04 -06: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-07 15:24:08 -07:00
|
|
|
|
2010-08-04 06:50:23 -06:00
|
|
|
intel_sdvo_debug_write(intel_sdvo, cmd, args, args_len);
|
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-07 15:24:08 -07:00
|
|
|
|
|
|
|
for (i = 0; i < args_len; i++) {
|
2010-09-24 05:52:03 -06:00
|
|
|
msgs[i].addr = intel_sdvo->slave_addr;
|
|
|
|
msgs[i].flags = 0;
|
|
|
|
msgs[i].len = 2;
|
|
|
|
msgs[i].buf = buf + 2 *i;
|
|
|
|
buf[2*i + 0] = SDVO_I2C_ARG_0 - i;
|
|
|
|
buf[2*i + 1] = ((u8*)args)[i];
|
|
|
|
}
|
|
|
|
msgs[i].addr = intel_sdvo->slave_addr;
|
|
|
|
msgs[i].flags = 0;
|
|
|
|
msgs[i].len = 2;
|
|
|
|
msgs[i].buf = buf + 2*i;
|
|
|
|
buf[2*i + 0] = SDVO_I2C_OPCODE;
|
|
|
|
buf[2*i + 1] = cmd;
|
|
|
|
|
|
|
|
/* the following two are to read the response */
|
|
|
|
status = SDVO_I2C_CMD_STATUS;
|
|
|
|
msgs[i+1].addr = intel_sdvo->slave_addr;
|
|
|
|
msgs[i+1].flags = 0;
|
|
|
|
msgs[i+1].len = 1;
|
|
|
|
msgs[i+1].buf = &status;
|
|
|
|
|
|
|
|
msgs[i+2].addr = intel_sdvo->slave_addr;
|
|
|
|
msgs[i+2].flags = I2C_M_RD;
|
|
|
|
msgs[i+2].len = 1;
|
|
|
|
msgs[i+2].buf = &status;
|
|
|
|
|
|
|
|
ret = i2c_transfer(intel_sdvo->i2c, msgs, i+3);
|
|
|
|
if (ret < 0) {
|
|
|
|
DRM_DEBUG_KMS("I2c transfer returned %d\n", ret);
|
2012-04-16 15:07:41 -06:00
|
|
|
ret = false;
|
|
|
|
goto out;
|
2010-09-24 05:52:03 -06:00
|
|
|
}
|
|
|
|
if (ret != i+3) {
|
|
|
|
/* failure in I2C transfer */
|
|
|
|
DRM_DEBUG_KMS("I2c transfer returned %d/%d\n", ret, i+3);
|
2012-04-16 15:07:41 -06:00
|
|
|
ret = false;
|
2010-09-24 05:52:03 -06:00
|
|
|
}
|
|
|
|
|
2012-04-16 15:07:41 -06:00
|
|
|
out:
|
|
|
|
kfree(msgs);
|
|
|
|
kfree(buf);
|
|
|
|
return ret;
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-07 15:24:08 -07:00
|
|
|
}
|
|
|
|
|
2010-09-09 12:06:13 -06:00
|
|
|
static bool intel_sdvo_read_response(struct intel_sdvo *intel_sdvo,
|
|
|
|
void *response, int response_len)
|
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-07 15:24:08 -07:00
|
|
|
{
|
2012-11-23 04:57:56 -07:00
|
|
|
u8 retry = 15; /* 5 quick checks, followed by 10 long checks */
|
2010-09-09 12:06:13 -06:00
|
|
|
u8 status;
|
2009-03-24 00:02:40 -06:00
|
|
|
int i;
|
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-07 15:24:08 -07:00
|
|
|
|
2011-01-25 08:00:01 -07:00
|
|
|
DRM_DEBUG_KMS("%s: R: ", SDVO_NAME(intel_sdvo));
|
|
|
|
|
2010-09-09 12:06:13 -06:00
|
|
|
/*
|
|
|
|
* The documentation states that all commands will be
|
|
|
|
* processed within 15µs, and that we need only poll
|
|
|
|
* the status byte a maximum of 3 times in order for the
|
|
|
|
* command to be complete.
|
|
|
|
*
|
|
|
|
* Check 5 times in case the hardware failed to read the docs.
|
2012-11-23 04:57:56 -07:00
|
|
|
*
|
|
|
|
* Also beware that the first response by many devices is to
|
|
|
|
* reply PENDING and stall for time. TVs are notorious for
|
|
|
|
* requiring longer than specified to complete their replies.
|
|
|
|
* Originally (in the DDX long ago), the delay was only ever 15ms
|
|
|
|
* with an additional delay of 30ms applied for TVs added later after
|
|
|
|
* many experiments. To accommodate both sets of delays, we do a
|
|
|
|
* sequence of slow checks if the device is falling behind and fails
|
|
|
|
* to reply within 5*15µs.
|
2010-09-09 12:06:13 -06:00
|
|
|
*/
|
2011-01-25 08:00:01 -07:00
|
|
|
if (!intel_sdvo_read_byte(intel_sdvo,
|
|
|
|
SDVO_I2C_CMD_STATUS,
|
|
|
|
&status))
|
|
|
|
goto log_fail;
|
|
|
|
|
2012-11-23 04:57:56 -07:00
|
|
|
while (status == SDVO_CMD_STATUS_PENDING && --retry) {
|
|
|
|
if (retry < 10)
|
|
|
|
msleep(15);
|
|
|
|
else
|
|
|
|
udelay(15);
|
|
|
|
|
2010-09-09 12:06:13 -06:00
|
|
|
if (!intel_sdvo_read_byte(intel_sdvo,
|
|
|
|
SDVO_I2C_CMD_STATUS,
|
|
|
|
&status))
|
2011-01-25 08:00:01 -07:00
|
|
|
goto log_fail;
|
|
|
|
}
|
2010-09-09 12:06:13 -06: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-07 15:24:08 -07:00
|
|
|
if (status <= SDVO_CMD_STATUS_SCALING_NOT_SUPP)
|
2009-06-02 00:12:00 -06:00
|
|
|
DRM_LOG_KMS("(%s)", cmd_status_names[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-07 15:24:08 -07:00
|
|
|
else
|
2009-06-02 00:12:00 -06:00
|
|
|
DRM_LOG_KMS("(??? %d)", 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-07 15:24:08 -07:00
|
|
|
|
2010-09-09 12:06:13 -06:00
|
|
|
if (status != SDVO_CMD_STATUS_SUCCESS)
|
|
|
|
goto log_fail;
|
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-07 15:24:08 -07:00
|
|
|
|
2010-09-09 12:06:13 -06:00
|
|
|
/* Read the command response */
|
|
|
|
for (i = 0; i < response_len; i++) {
|
|
|
|
if (!intel_sdvo_read_byte(intel_sdvo,
|
|
|
|
SDVO_I2C_RETURN_0 + i,
|
|
|
|
&((u8 *)response)[i]))
|
|
|
|
goto log_fail;
|
2010-09-24 05:52:03 -06:00
|
|
|
DRM_LOG_KMS(" %02X", ((u8 *)response)[i]);
|
2010-09-09 12:06:13 -06:00
|
|
|
}
|
|
|
|
DRM_LOG_KMS("\n");
|
|
|
|
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-07 15:24:08 -07:00
|
|
|
|
2010-09-09 12:06:13 -06:00
|
|
|
log_fail:
|
2011-01-25 08:00:01 -07:00
|
|
|
DRM_LOG_KMS("... failed\n");
|
2010-09-09 12:06:13 -06: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-07 15:24:08 -07:00
|
|
|
}
|
|
|
|
|
2008-12-18 13:18:47 -07:00
|
|
|
static int intel_sdvo_get_pixel_multiplier(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-07 15:24:08 -07:00
|
|
|
{
|
|
|
|
if (mode->clock >= 100000)
|
|
|
|
return 1;
|
|
|
|
else if (mode->clock >= 50000)
|
|
|
|
return 2;
|
|
|
|
else
|
|
|
|
return 4;
|
|
|
|
}
|
|
|
|
|
2010-09-24 05:52:03 -06:00
|
|
|
static bool intel_sdvo_set_control_bus_switch(struct intel_sdvo *intel_sdvo,
|
|
|
|
u8 ddc_bus)
|
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-07 15:24:08 -07:00
|
|
|
{
|
2011-01-25 08:00:01 -07:00
|
|
|
/* This must be the immediately preceding write before the i2c xfer */
|
2010-09-24 05:52:03 -06:00
|
|
|
return intel_sdvo_write_cmd(intel_sdvo,
|
|
|
|
SDVO_CMD_SET_CONTROL_BUS_SWITCH,
|
|
|
|
&ddc_bus, 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-07 15:24:08 -07:00
|
|
|
}
|
|
|
|
|
2010-08-04 06:50:25 -06:00
|
|
|
static bool intel_sdvo_set_value(struct intel_sdvo *intel_sdvo, u8 cmd, const void *data, int len)
|
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-07 15:24:08 -07:00
|
|
|
{
|
2011-01-25 08:00:01 -07:00
|
|
|
if (!intel_sdvo_write_cmd(intel_sdvo, cmd, data, len))
|
|
|
|
return false;
|
|
|
|
|
|
|
|
return intel_sdvo_read_response(intel_sdvo, NULL, 0);
|
2010-08-04 06:50:25 -06: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-07 15:24:08 -07:00
|
|
|
|
2010-08-04 06:50:25 -06:00
|
|
|
static bool
|
|
|
|
intel_sdvo_get_value(struct intel_sdvo *intel_sdvo, u8 cmd, void *value, int len)
|
|
|
|
{
|
|
|
|
if (!intel_sdvo_write_cmd(intel_sdvo, cmd, NULL, 0))
|
|
|
|
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-07 15:24:08 -07:00
|
|
|
|
2010-08-04 06:50:25 -06:00
|
|
|
return intel_sdvo_read_response(intel_sdvo, value, len);
|
|
|
|
}
|
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-07 15:24:08 -07:00
|
|
|
|
2010-08-04 06:50:25 -06:00
|
|
|
static bool intel_sdvo_set_target_input(struct intel_sdvo *intel_sdvo)
|
|
|
|
{
|
|
|
|
struct intel_sdvo_set_target_input_args targets = {0};
|
|
|
|
return intel_sdvo_set_value(intel_sdvo,
|
|
|
|
SDVO_CMD_SET_TARGET_INPUT,
|
|
|
|
&targets, sizeof(targets));
|
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-07 15:24:08 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* Return whether each input is trained.
|
|
|
|
*
|
|
|
|
* This function is making an assumption about the layout of the response,
|
|
|
|
* which should be checked against the docs.
|
|
|
|
*/
|
2010-08-04 06:50:23 -06:00
|
|
|
static bool intel_sdvo_get_trained_inputs(struct intel_sdvo *intel_sdvo, bool *input_1, bool *input_2)
|
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-07 15:24:08 -07:00
|
|
|
{
|
|
|
|
struct intel_sdvo_get_trained_inputs_response response;
|
|
|
|
|
2011-01-25 06:59:37 -07:00
|
|
|
BUILD_BUG_ON(sizeof(response) != 1);
|
2010-08-04 06:50:25 -06:00
|
|
|
if (!intel_sdvo_get_value(intel_sdvo, SDVO_CMD_GET_TRAINED_INPUTS,
|
|
|
|
&response, sizeof(response)))
|
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-07 15:24:08 -07:00
|
|
|
return false;
|
|
|
|
|
|
|
|
*input_1 = response.input0_trained;
|
|
|
|
*input_2 = response.input1_trained;
|
|
|
|
return true;
|
|
|
|
}
|
|
|
|
|
2010-08-04 06:50:23 -06:00
|
|
|
static bool intel_sdvo_set_active_outputs(struct intel_sdvo *intel_sdvo,
|
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-07 15:24:08 -07:00
|
|
|
u16 outputs)
|
|
|
|
{
|
2010-08-04 06:50:25 -06:00
|
|
|
return intel_sdvo_set_value(intel_sdvo,
|
|
|
|
SDVO_CMD_SET_ACTIVE_OUTPUTS,
|
|
|
|
&outputs, sizeof(outputs));
|
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-07 15:24:08 -07:00
|
|
|
}
|
|
|
|
|
2012-07-02 06:54:00 -06:00
|
|
|
static bool intel_sdvo_get_active_outputs(struct intel_sdvo *intel_sdvo,
|
|
|
|
u16 *outputs)
|
|
|
|
{
|
|
|
|
return intel_sdvo_get_value(intel_sdvo,
|
|
|
|
SDVO_CMD_GET_ACTIVE_OUTPUTS,
|
|
|
|
outputs, sizeof(*outputs));
|
|
|
|
}
|
|
|
|
|
2010-08-04 06:50:23 -06:00
|
|
|
static bool intel_sdvo_set_encoder_power_state(struct intel_sdvo *intel_sdvo,
|
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-07 15:24:08 -07:00
|
|
|
int mode)
|
|
|
|
{
|
2010-08-04 06:50:25 -06:00
|
|
|
u8 state = SDVO_ENCODER_STATE_ON;
|
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-07 15:24:08 -07:00
|
|
|
|
|
|
|
switch (mode) {
|
|
|
|
case DRM_MODE_DPMS_ON:
|
|
|
|
state = SDVO_ENCODER_STATE_ON;
|
|
|
|
break;
|
|
|
|
case DRM_MODE_DPMS_STANDBY:
|
|
|
|
state = SDVO_ENCODER_STATE_STANDBY;
|
|
|
|
break;
|
|
|
|
case DRM_MODE_DPMS_SUSPEND:
|
|
|
|
state = SDVO_ENCODER_STATE_SUSPEND;
|
|
|
|
break;
|
|
|
|
case DRM_MODE_DPMS_OFF:
|
|
|
|
state = SDVO_ENCODER_STATE_OFF;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
2010-08-04 06:50:25 -06:00
|
|
|
return intel_sdvo_set_value(intel_sdvo,
|
|
|
|
SDVO_CMD_SET_ENCODER_POWER_STATE, &state, sizeof(state));
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-07 15:24:08 -07:00
|
|
|
}
|
|
|
|
|
2010-08-04 06:50:23 -06:00
|
|
|
static bool intel_sdvo_get_input_pixel_clock_range(struct intel_sdvo *intel_sdvo,
|
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-07 15:24:08 -07:00
|
|
|
int *clock_min,
|
|
|
|
int *clock_max)
|
|
|
|
{
|
|
|
|
struct intel_sdvo_pixel_clock_range clocks;
|
|
|
|
|
2011-01-25 06:59:37 -07:00
|
|
|
BUILD_BUG_ON(sizeof(clocks) != 4);
|
2010-08-04 06:50:25 -06:00
|
|
|
if (!intel_sdvo_get_value(intel_sdvo,
|
|
|
|
SDVO_CMD_GET_INPUT_PIXEL_CLOCK_RANGE,
|
|
|
|
&clocks, sizeof(clocks)))
|
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-07 15:24:08 -07:00
|
|
|
return false;
|
|
|
|
|
|
|
|
/* Convert the values from units of 10 kHz to kHz. */
|
|
|
|
*clock_min = clocks.min * 10;
|
|
|
|
*clock_max = clocks.max * 10;
|
|
|
|
return true;
|
|
|
|
}
|
|
|
|
|
2010-08-04 06:50:23 -06:00
|
|
|
static bool intel_sdvo_set_target_output(struct intel_sdvo *intel_sdvo,
|
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-07 15:24:08 -07:00
|
|
|
u16 outputs)
|
|
|
|
{
|
2010-08-04 06:50:25 -06:00
|
|
|
return intel_sdvo_set_value(intel_sdvo,
|
|
|
|
SDVO_CMD_SET_TARGET_OUTPUT,
|
|
|
|
&outputs, sizeof(outputs));
|
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-07 15:24:08 -07:00
|
|
|
}
|
|
|
|
|
2010-08-04 06:50:23 -06:00
|
|
|
static bool intel_sdvo_set_timing(struct intel_sdvo *intel_sdvo, u8 cmd,
|
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-07 15:24:08 -07:00
|
|
|
struct intel_sdvo_dtd *dtd)
|
|
|
|
{
|
2010-08-04 06:50:25 -06:00
|
|
|
return intel_sdvo_set_value(intel_sdvo, cmd, &dtd->part1, sizeof(dtd->part1)) &&
|
|
|
|
intel_sdvo_set_value(intel_sdvo, cmd + 1, &dtd->part2, sizeof(dtd->part2));
|
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-07 15:24:08 -07:00
|
|
|
}
|
|
|
|
|
2013-05-14 18:08:26 -06:00
|
|
|
static bool intel_sdvo_get_timing(struct intel_sdvo *intel_sdvo, u8 cmd,
|
|
|
|
struct intel_sdvo_dtd *dtd)
|
|
|
|
{
|
|
|
|
return intel_sdvo_get_value(intel_sdvo, cmd, &dtd->part1, sizeof(dtd->part1)) &&
|
|
|
|
intel_sdvo_get_value(intel_sdvo, cmd + 1, &dtd->part2, sizeof(dtd->part2));
|
|
|
|
}
|
|
|
|
|
2010-08-04 06:50:23 -06:00
|
|
|
static bool intel_sdvo_set_input_timing(struct intel_sdvo *intel_sdvo,
|
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-07 15:24:08 -07:00
|
|
|
struct intel_sdvo_dtd *dtd)
|
|
|
|
{
|
2010-08-04 06:50:23 -06:00
|
|
|
return intel_sdvo_set_timing(intel_sdvo,
|
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-07 15:24:08 -07:00
|
|
|
SDVO_CMD_SET_INPUT_TIMINGS_PART1, dtd);
|
|
|
|
}
|
|
|
|
|
2010-08-04 06:50:23 -06:00
|
|
|
static bool intel_sdvo_set_output_timing(struct intel_sdvo *intel_sdvo,
|
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-07 15:24:08 -07:00
|
|
|
struct intel_sdvo_dtd *dtd)
|
|
|
|
{
|
2010-08-04 06:50:23 -06:00
|
|
|
return intel_sdvo_set_timing(intel_sdvo,
|
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-07 15:24:08 -07:00
|
|
|
SDVO_CMD_SET_OUTPUT_TIMINGS_PART1, dtd);
|
|
|
|
}
|
|
|
|
|
2013-05-14 18:08:26 -06:00
|
|
|
static bool intel_sdvo_get_input_timing(struct intel_sdvo *intel_sdvo,
|
|
|
|
struct intel_sdvo_dtd *dtd)
|
|
|
|
{
|
|
|
|
return intel_sdvo_get_timing(intel_sdvo,
|
|
|
|
SDVO_CMD_GET_INPUT_TIMINGS_PART1, dtd);
|
|
|
|
}
|
|
|
|
|
2009-02-02 16:11:52 -07:00
|
|
|
static bool
|
2010-08-04 06:50:23 -06:00
|
|
|
intel_sdvo_create_preferred_input_timing(struct intel_sdvo *intel_sdvo,
|
2009-02-02 16:11:52 -07:00
|
|
|
uint16_t clock,
|
|
|
|
uint16_t width,
|
|
|
|
uint16_t height)
|
|
|
|
{
|
|
|
|
struct intel_sdvo_preferred_input_timing_args args;
|
|
|
|
|
2009-03-24 00:02:42 -06:00
|
|
|
memset(&args, 0, sizeof(args));
|
2009-02-02 16:11:52 -07:00
|
|
|
args.clock = clock;
|
|
|
|
args.width = width;
|
|
|
|
args.height = height;
|
2009-03-24 00:02:42 -06:00
|
|
|
args.interlace = 0;
|
2009-06-29 21:35:35 -06:00
|
|
|
|
2010-08-04 06:50:23 -06:00
|
|
|
if (intel_sdvo->is_lvds &&
|
|
|
|
(intel_sdvo->sdvo_lvds_fixed_mode->hdisplay != width ||
|
|
|
|
intel_sdvo->sdvo_lvds_fixed_mode->vdisplay != height))
|
2009-06-29 21:35:35 -06:00
|
|
|
args.scaled = 1;
|
|
|
|
|
2010-08-04 06:50:25 -06:00
|
|
|
return intel_sdvo_set_value(intel_sdvo,
|
|
|
|
SDVO_CMD_CREATE_PREFERRED_INPUT_TIMING,
|
|
|
|
&args, sizeof(args));
|
2009-02-02 16:11:52 -07:00
|
|
|
}
|
|
|
|
|
2010-08-04 06:50:23 -06:00
|
|
|
static bool intel_sdvo_get_preferred_input_timing(struct intel_sdvo *intel_sdvo,
|
2009-02-02 16:11:52 -07:00
|
|
|
struct intel_sdvo_dtd *dtd)
|
|
|
|
{
|
2011-01-25 06:59:37 -07:00
|
|
|
BUILD_BUG_ON(sizeof(dtd->part1) != 8);
|
|
|
|
BUILD_BUG_ON(sizeof(dtd->part2) != 8);
|
2010-08-04 06:50:25 -06:00
|
|
|
return intel_sdvo_get_value(intel_sdvo, SDVO_CMD_GET_PREFERRED_INPUT_TIMING_PART1,
|
|
|
|
&dtd->part1, sizeof(dtd->part1)) &&
|
|
|
|
intel_sdvo_get_value(intel_sdvo, SDVO_CMD_GET_PREFERRED_INPUT_TIMING_PART2,
|
|
|
|
&dtd->part2, sizeof(dtd->part2));
|
2009-02-02 16:11:52 -07:00
|
|
|
}
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-07 15:24:08 -07:00
|
|
|
|
2010-08-04 06:50:23 -06:00
|
|
|
static bool intel_sdvo_set_clock_rate_mult(struct intel_sdvo *intel_sdvo, u8 val)
|
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-07 15:24:08 -07:00
|
|
|
{
|
2010-08-04 06:50:25 -06:00
|
|
|
return intel_sdvo_set_value(intel_sdvo, SDVO_CMD_SET_CLOCK_RATE_MULT, &val, 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-07 15:24:08 -07:00
|
|
|
}
|
|
|
|
|
2009-02-02 16:11:52 -07:00
|
|
|
static void intel_sdvo_get_dtd_from_mode(struct intel_sdvo_dtd *dtd,
|
2010-08-04 06:50:25 -06:00
|
|
|
const 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-07 15:24:08 -07:00
|
|
|
{
|
2009-02-02 16:11:52 -07:00
|
|
|
uint16_t width, height;
|
|
|
|
uint16_t h_blank_len, h_sync_len, v_blank_len, v_sync_len;
|
|
|
|
uint16_t h_sync_offset, v_sync_offset;
|
drm/i915: handle input/output sdvo timings separately in mode_set
We seem to have a decent confusion between the output timings and the
input timings of the sdvo encoder. If I understand the code correctly,
we use the original mode unchanged for the output timings, safe for
the lvds case. And we should use the adjusted mode for input timings.
Clarify the situation by adding an explicit output_dtd to the sdvo
mode_set function and streamline the code-flow by moving the input and
output mode setting in the sdvo encode together.
Furthermore testing showed that the sdvo input timing needs the
unadjusted dotclock, the sdvo chip will automatically compute the
required pixel multiplier to get a dotclock above 100 MHz.
Fix this up when converting a drm mode to an sdvo dtd.
This regression was introduced in
commit c74696b9c890074c1e1ee3d7496fc71eb3680ced
Author: Pavel Roskin <proski@gnu.org>
Date: Thu Sep 2 14:46:34 2010 -0400
i915: revert some checks added by commit 32aad86f
particularly the following hunk:
diff --git a/drivers/gpu/drm/i915/intel_sdvo.c
b/drivers/gpu/drm/i915/intel_sdvo.c
index 093e914..62d22ae 100644
--- a/drivers/gpu/drm/i915/intel_sdvo.c
+++ b/drivers/gpu/drm/i915/intel_sdvo.c
@@ -1122,11 +1123,9 @@ static void intel_sdvo_mode_set(struct drm_encoder *encoder,
/* We have tried to get input timing in mode_fixup, and filled into
adjusted_mode */
- if (intel_sdvo->is_tv || intel_sdvo->is_lvds) {
- intel_sdvo_get_dtd_from_mode(&input_dtd, adjusted_mode);
+ intel_sdvo_get_dtd_from_mode(&input_dtd, adjusted_mode);
+ if (intel_sdvo->is_tv || intel_sdvo->is_lvds)
input_dtd.part2.sdvo_flags = intel_sdvo->sdvo_flags;
- } else
- intel_sdvo_get_dtd_from_mode(&input_dtd, mode);
/* If it's a TV, we already set the output timing in mode_fixup.
* Otherwise, the output timing is equal to the input timing.
Due to questions raised in review, below a more elaborate analysis of
the bug at hand:
Sdvo seems to have two timings, one is the output timing which will be
sent over whatever is connected on the other side of the sdvo chip (panel,
hdmi screen, tv), the other is the input timing which will be generated by
the gmch pipe. It looks like sdvo is expected to scale between the two.
To make things slightly more complicated, we have a bunch of special
cases:
- For lvds panel we always use a fixed output timing, namely
intel_sdvo->sdvo_lvds_fixed_mode, hence that special case.
- Sdvo has an interface to generate a preferred input timing for a given
output timing. This is the confusing thing that I've tried to clear up
with the follow-on patches.
- A special requirement is that the input pixel clock needs to be between
100MHz and 200MHz (likely to keep it within the electromechanical design
range of PCIe), 270MHz on later gen4+. Lower pixel clocks are
doubled/quadrupled.
The thing this patch tries to fix is that the pipe needs to be
explicitly instructed to double/quadruple the pixels and needs the
correspondingly higher pixel clock, whereas the sdvo adaptor seems to
do that itself and needs the unadjusted pixel clock. For the sdvo
encode side we already set the pixel mutliplier with a different
command (0x21).
This patch tries to fix this mess by:
- Keeping the output mode timing in the unadjusted plain mode, safe
for the lvds case.
- Storing the input timing in the adjusted_mode with the adjusted
pixel clock. This way we don't need to frob around with the core
crtc mode set code.
- Fixing up the pixelclock when constructing the sdvo dtd timing
struct. This is why the first hunk of the patch is an integral part
of the series.
- Dropping the is_tv special case because input_dtd is equivalent to
adjusted_mode after these changes. Follow-up patches clear this up
further (by simply ripping out intel_sdvo->input_dtd because it's
not needed).
v2: Extend commit message with an in-depth bug analysis.
Reported-and-Tested-by: Bernard Blackham <b-linuxgit@largestprime.net>
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=48157
Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: stable@kernel.org
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
2012-04-01 11:16:18 -06:00
|
|
|
int mode_clock;
|
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-07 15:24:08 -07:00
|
|
|
|
2012-04-24 10:27:57 -06:00
|
|
|
width = mode->hdisplay;
|
|
|
|
height = mode->vdisplay;
|
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-07 15:24:08 -07:00
|
|
|
|
|
|
|
/* do some mode translations */
|
2012-04-24 10:27:57 -06:00
|
|
|
h_blank_len = mode->htotal - mode->hdisplay;
|
|
|
|
h_sync_len = mode->hsync_end - mode->hsync_start;
|
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-07 15:24:08 -07:00
|
|
|
|
2012-04-24 10:27:57 -06:00
|
|
|
v_blank_len = mode->vtotal - mode->vdisplay;
|
|
|
|
v_sync_len = mode->vsync_end - mode->vsync_start;
|
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-07 15:24:08 -07:00
|
|
|
|
2012-04-24 10:27:57 -06:00
|
|
|
h_sync_offset = mode->hsync_start - mode->hdisplay;
|
|
|
|
v_sync_offset = mode->vsync_start - mode->vdisplay;
|
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-07 15:24:08 -07:00
|
|
|
|
drm/i915: handle input/output sdvo timings separately in mode_set
We seem to have a decent confusion between the output timings and the
input timings of the sdvo encoder. If I understand the code correctly,
we use the original mode unchanged for the output timings, safe for
the lvds case. And we should use the adjusted mode for input timings.
Clarify the situation by adding an explicit output_dtd to the sdvo
mode_set function and streamline the code-flow by moving the input and
output mode setting in the sdvo encode together.
Furthermore testing showed that the sdvo input timing needs the
unadjusted dotclock, the sdvo chip will automatically compute the
required pixel multiplier to get a dotclock above 100 MHz.
Fix this up when converting a drm mode to an sdvo dtd.
This regression was introduced in
commit c74696b9c890074c1e1ee3d7496fc71eb3680ced
Author: Pavel Roskin <proski@gnu.org>
Date: Thu Sep 2 14:46:34 2010 -0400
i915: revert some checks added by commit 32aad86f
particularly the following hunk:
diff --git a/drivers/gpu/drm/i915/intel_sdvo.c
b/drivers/gpu/drm/i915/intel_sdvo.c
index 093e914..62d22ae 100644
--- a/drivers/gpu/drm/i915/intel_sdvo.c
+++ b/drivers/gpu/drm/i915/intel_sdvo.c
@@ -1122,11 +1123,9 @@ static void intel_sdvo_mode_set(struct drm_encoder *encoder,
/* We have tried to get input timing in mode_fixup, and filled into
adjusted_mode */
- if (intel_sdvo->is_tv || intel_sdvo->is_lvds) {
- intel_sdvo_get_dtd_from_mode(&input_dtd, adjusted_mode);
+ intel_sdvo_get_dtd_from_mode(&input_dtd, adjusted_mode);
+ if (intel_sdvo->is_tv || intel_sdvo->is_lvds)
input_dtd.part2.sdvo_flags = intel_sdvo->sdvo_flags;
- } else
- intel_sdvo_get_dtd_from_mode(&input_dtd, mode);
/* If it's a TV, we already set the output timing in mode_fixup.
* Otherwise, the output timing is equal to the input timing.
Due to questions raised in review, below a more elaborate analysis of
the bug at hand:
Sdvo seems to have two timings, one is the output timing which will be
sent over whatever is connected on the other side of the sdvo chip (panel,
hdmi screen, tv), the other is the input timing which will be generated by
the gmch pipe. It looks like sdvo is expected to scale between the two.
To make things slightly more complicated, we have a bunch of special
cases:
- For lvds panel we always use a fixed output timing, namely
intel_sdvo->sdvo_lvds_fixed_mode, hence that special case.
- Sdvo has an interface to generate a preferred input timing for a given
output timing. This is the confusing thing that I've tried to clear up
with the follow-on patches.
- A special requirement is that the input pixel clock needs to be between
100MHz and 200MHz (likely to keep it within the electromechanical design
range of PCIe), 270MHz on later gen4+. Lower pixel clocks are
doubled/quadrupled.
The thing this patch tries to fix is that the pipe needs to be
explicitly instructed to double/quadruple the pixels and needs the
correspondingly higher pixel clock, whereas the sdvo adaptor seems to
do that itself and needs the unadjusted pixel clock. For the sdvo
encode side we already set the pixel mutliplier with a different
command (0x21).
This patch tries to fix this mess by:
- Keeping the output mode timing in the unadjusted plain mode, safe
for the lvds case.
- Storing the input timing in the adjusted_mode with the adjusted
pixel clock. This way we don't need to frob around with the core
crtc mode set code.
- Fixing up the pixelclock when constructing the sdvo dtd timing
struct. This is why the first hunk of the patch is an integral part
of the series.
- Dropping the is_tv special case because input_dtd is equivalent to
adjusted_mode after these changes. Follow-up patches clear this up
further (by simply ripping out intel_sdvo->input_dtd because it's
not needed).
v2: Extend commit message with an in-depth bug analysis.
Reported-and-Tested-by: Bernard Blackham <b-linuxgit@largestprime.net>
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=48157
Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: stable@kernel.org
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
2012-04-01 11:16:18 -06:00
|
|
|
mode_clock = mode->clock;
|
|
|
|
mode_clock /= 10;
|
|
|
|
dtd->part1.clock = mode_clock;
|
|
|
|
|
2009-02-02 16:11:52 -07:00
|
|
|
dtd->part1.h_active = width & 0xff;
|
|
|
|
dtd->part1.h_blank = h_blank_len & 0xff;
|
|
|
|
dtd->part1.h_high = (((width >> 8) & 0xf) << 4) |
|
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-07 15:24:08 -07:00
|
|
|
((h_blank_len >> 8) & 0xf);
|
2009-02-02 16:11:52 -07:00
|
|
|
dtd->part1.v_active = height & 0xff;
|
|
|
|
dtd->part1.v_blank = v_blank_len & 0xff;
|
|
|
|
dtd->part1.v_high = (((height >> 8) & 0xf) << 4) |
|
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-07 15:24:08 -07:00
|
|
|
((v_blank_len >> 8) & 0xf);
|
|
|
|
|
2009-03-24 00:02:41 -06:00
|
|
|
dtd->part2.h_sync_off = h_sync_offset & 0xff;
|
2009-02-02 16:11:52 -07:00
|
|
|
dtd->part2.h_sync_width = h_sync_len & 0xff;
|
|
|
|
dtd->part2.v_sync_off_width = (v_sync_offset & 0xf) << 4 |
|
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-07 15:24:08 -07:00
|
|
|
(v_sync_len & 0xf);
|
2009-02-02 16:11:52 -07:00
|
|
|
dtd->part2.sync_off_width_high = ((h_sync_offset & 0x300) >> 2) |
|
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-07 15:24:08 -07:00
|
|
|
((h_sync_len & 0x300) >> 4) | ((v_sync_offset & 0x30) >> 2) |
|
|
|
|
((v_sync_len & 0x30) >> 4);
|
|
|
|
|
2009-02-02 16:11:52 -07:00
|
|
|
dtd->part2.dtd_flags = 0x18;
|
2012-05-12 14:22:58 -06:00
|
|
|
if (mode->flags & DRM_MODE_FLAG_INTERLACE)
|
|
|
|
dtd->part2.dtd_flags |= DTD_FLAG_INTERLACE;
|
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-07 15:24:08 -07:00
|
|
|
if (mode->flags & DRM_MODE_FLAG_PHSYNC)
|
2012-05-12 14:22:58 -06:00
|
|
|
dtd->part2.dtd_flags |= DTD_FLAG_HSYNC_POSITIVE;
|
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-07 15:24:08 -07:00
|
|
|
if (mode->flags & DRM_MODE_FLAG_PVSYNC)
|
2012-05-12 14:22:58 -06:00
|
|
|
dtd->part2.dtd_flags |= DTD_FLAG_VSYNC_POSITIVE;
|
2009-02-02 16:11:52 -07:00
|
|
|
|
|
|
|
dtd->part2.sdvo_flags = 0;
|
|
|
|
dtd->part2.v_sync_off_high = v_sync_offset & 0xc0;
|
|
|
|
dtd->part2.reserved = 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void intel_sdvo_get_mode_from_dtd(struct drm_display_mode * mode,
|
2010-08-04 06:50:25 -06:00
|
|
|
const struct intel_sdvo_dtd *dtd)
|
2009-02-02 16:11:52 -07:00
|
|
|
{
|
|
|
|
mode->hdisplay = dtd->part1.h_active;
|
|
|
|
mode->hdisplay += ((dtd->part1.h_high >> 4) & 0x0f) << 8;
|
|
|
|
mode->hsync_start = mode->hdisplay + dtd->part2.h_sync_off;
|
2009-03-24 00:02:41 -06:00
|
|
|
mode->hsync_start += (dtd->part2.sync_off_width_high & 0xc0) << 2;
|
2009-02-02 16:11:52 -07:00
|
|
|
mode->hsync_end = mode->hsync_start + dtd->part2.h_sync_width;
|
|
|
|
mode->hsync_end += (dtd->part2.sync_off_width_high & 0x30) << 4;
|
|
|
|
mode->htotal = mode->hdisplay + dtd->part1.h_blank;
|
|
|
|
mode->htotal += (dtd->part1.h_high & 0xf) << 8;
|
|
|
|
|
|
|
|
mode->vdisplay = dtd->part1.v_active;
|
|
|
|
mode->vdisplay += ((dtd->part1.v_high >> 4) & 0x0f) << 8;
|
|
|
|
mode->vsync_start = mode->vdisplay;
|
|
|
|
mode->vsync_start += (dtd->part2.v_sync_off_width >> 4) & 0xf;
|
2009-03-24 00:02:41 -06:00
|
|
|
mode->vsync_start += (dtd->part2.sync_off_width_high & 0x0c) << 2;
|
2009-02-02 16:11:52 -07:00
|
|
|
mode->vsync_start += dtd->part2.v_sync_off_high & 0xc0;
|
|
|
|
mode->vsync_end = mode->vsync_start +
|
|
|
|
(dtd->part2.v_sync_off_width & 0xf);
|
|
|
|
mode->vsync_end += (dtd->part2.sync_off_width_high & 0x3) << 4;
|
|
|
|
mode->vtotal = mode->vdisplay + dtd->part1.v_blank;
|
|
|
|
mode->vtotal += (dtd->part1.v_high & 0xf) << 8;
|
|
|
|
|
|
|
|
mode->clock = dtd->part1.clock * 10;
|
|
|
|
|
2009-03-24 00:02:41 -06:00
|
|
|
mode->flags &= ~(DRM_MODE_FLAG_PHSYNC | DRM_MODE_FLAG_PVSYNC);
|
2012-05-12 14:22:58 -06:00
|
|
|
if (dtd->part2.dtd_flags & DTD_FLAG_INTERLACE)
|
|
|
|
mode->flags |= DRM_MODE_FLAG_INTERLACE;
|
|
|
|
if (dtd->part2.dtd_flags & DTD_FLAG_HSYNC_POSITIVE)
|
2009-02-02 16:11:52 -07:00
|
|
|
mode->flags |= DRM_MODE_FLAG_PHSYNC;
|
2012-05-12 14:22:58 -06:00
|
|
|
if (dtd->part2.dtd_flags & DTD_FLAG_VSYNC_POSITIVE)
|
2009-02-02 16:11:52 -07:00
|
|
|
mode->flags |= DRM_MODE_FLAG_PVSYNC;
|
|
|
|
}
|
|
|
|
|
2010-10-22 02:15:22 -06:00
|
|
|
static bool intel_sdvo_check_supp_encode(struct intel_sdvo *intel_sdvo)
|
2009-02-02 16:11:52 -07:00
|
|
|
{
|
2010-10-22 02:15:22 -06:00
|
|
|
struct intel_sdvo_encode encode;
|
2009-02-02 16:11:52 -07:00
|
|
|
|
2011-01-25 06:59:37 -07:00
|
|
|
BUILD_BUG_ON(sizeof(encode) != 2);
|
2010-10-22 02:15:22 -06:00
|
|
|
return intel_sdvo_get_value(intel_sdvo,
|
|
|
|
SDVO_CMD_GET_SUPP_ENCODE,
|
|
|
|
&encode, sizeof(encode));
|
2009-02-02 16:11:52 -07:00
|
|
|
}
|
|
|
|
|
2010-08-04 06:50:23 -06:00
|
|
|
static bool intel_sdvo_set_encode(struct intel_sdvo *intel_sdvo,
|
2010-03-25 12:48:48 -06:00
|
|
|
uint8_t mode)
|
2009-02-02 16:11:52 -07:00
|
|
|
{
|
2010-08-04 06:50:25 -06:00
|
|
|
return intel_sdvo_set_value(intel_sdvo, SDVO_CMD_SET_ENCODE, &mode, 1);
|
2009-02-02 16:11:52 -07:00
|
|
|
}
|
|
|
|
|
2010-08-04 06:50:23 -06:00
|
|
|
static bool intel_sdvo_set_colorimetry(struct intel_sdvo *intel_sdvo,
|
2009-02-02 16:11:52 -07:00
|
|
|
uint8_t mode)
|
|
|
|
{
|
2010-08-04 06:50:25 -06:00
|
|
|
return intel_sdvo_set_value(intel_sdvo, SDVO_CMD_SET_COLORIMETRY, &mode, 1);
|
2009-02-02 16:11:52 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
#if 0
|
2010-08-04 06:50:23 -06:00
|
|
|
static void intel_sdvo_dump_hdmi_buf(struct intel_sdvo *intel_sdvo)
|
2009-02-02 16:11:52 -07:00
|
|
|
{
|
|
|
|
int i, j;
|
|
|
|
uint8_t set_buf_index[2];
|
|
|
|
uint8_t av_split;
|
|
|
|
uint8_t buf_size;
|
|
|
|
uint8_t buf[48];
|
|
|
|
uint8_t *pos;
|
|
|
|
|
2010-08-04 06:50:25 -06:00
|
|
|
intel_sdvo_get_value(encoder, SDVO_CMD_GET_HBUF_AV_SPLIT, &av_split, 1);
|
2009-02-02 16:11:52 -07:00
|
|
|
|
|
|
|
for (i = 0; i <= av_split; i++) {
|
|
|
|
set_buf_index[0] = i; set_buf_index[1] = 0;
|
2010-03-25 12:48:48 -06:00
|
|
|
intel_sdvo_write_cmd(encoder, SDVO_CMD_SET_HBUF_INDEX,
|
2009-02-02 16:11:52 -07:00
|
|
|
set_buf_index, 2);
|
2010-03-25 12:48:48 -06:00
|
|
|
intel_sdvo_write_cmd(encoder, SDVO_CMD_GET_HBUF_INFO, NULL, 0);
|
|
|
|
intel_sdvo_read_response(encoder, &buf_size, 1);
|
2009-02-02 16:11:52 -07:00
|
|
|
|
|
|
|
pos = buf;
|
|
|
|
for (j = 0; j <= buf_size; j += 8) {
|
2010-03-25 12:48:48 -06:00
|
|
|
intel_sdvo_write_cmd(encoder, SDVO_CMD_GET_HBUF_DATA,
|
2009-02-02 16:11:52 -07:00
|
|
|
NULL, 0);
|
2010-03-25 12:48:48 -06:00
|
|
|
intel_sdvo_read_response(encoder, pos, 8);
|
2009-02-02 16:11:52 -07:00
|
|
|
pos += 8;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
#endif
|
|
|
|
|
2012-10-21 04:52:39 -06:00
|
|
|
static bool intel_sdvo_write_infoframe(struct intel_sdvo *intel_sdvo,
|
|
|
|
unsigned if_index, uint8_t tx_rate,
|
|
|
|
uint8_t *data, unsigned length)
|
|
|
|
{
|
|
|
|
uint8_t set_buf_index[2] = { if_index, 0 };
|
|
|
|
uint8_t hbuf_size, tmp[8];
|
|
|
|
int i;
|
|
|
|
|
|
|
|
if (!intel_sdvo_set_value(intel_sdvo,
|
|
|
|
SDVO_CMD_SET_HBUF_INDEX,
|
|
|
|
set_buf_index, 2))
|
|
|
|
return false;
|
|
|
|
|
|
|
|
if (!intel_sdvo_get_value(intel_sdvo, SDVO_CMD_GET_HBUF_INFO,
|
|
|
|
&hbuf_size, 1))
|
|
|
|
return false;
|
|
|
|
|
|
|
|
/* Buffer size is 0 based, hooray! */
|
|
|
|
hbuf_size++;
|
|
|
|
|
|
|
|
DRM_DEBUG_KMS("writing sdvo hbuf: %i, hbuf_size %i, hbuf_size: %i\n",
|
|
|
|
if_index, length, hbuf_size);
|
|
|
|
|
|
|
|
for (i = 0; i < hbuf_size; i += 8) {
|
|
|
|
memset(tmp, 0, 8);
|
|
|
|
if (i < length)
|
|
|
|
memcpy(tmp, data + i, min_t(unsigned, 8, length - i));
|
|
|
|
|
|
|
|
if (!intel_sdvo_set_value(intel_sdvo,
|
|
|
|
SDVO_CMD_SET_HBUF_DATA,
|
|
|
|
tmp, 8))
|
|
|
|
return false;
|
|
|
|
}
|
|
|
|
|
|
|
|
return intel_sdvo_set_value(intel_sdvo,
|
|
|
|
SDVO_CMD_SET_HBUF_TXRATE,
|
|
|
|
&tx_rate, 1);
|
|
|
|
}
|
|
|
|
|
2013-01-17 07:31:31 -07:00
|
|
|
static bool intel_sdvo_set_avi_infoframe(struct intel_sdvo *intel_sdvo,
|
|
|
|
const struct drm_display_mode *adjusted_mode)
|
2009-02-02 16:11:52 -07:00
|
|
|
{
|
|
|
|
struct dip_infoframe avi_if = {
|
|
|
|
.type = DIP_TYPE_AVI,
|
2010-09-24 13:44:32 -06:00
|
|
|
.ver = DIP_VERSION_AVI,
|
2009-02-02 16:11:52 -07:00
|
|
|
.len = DIP_LEN_AVI,
|
|
|
|
};
|
2012-05-12 12:22:00 -06:00
|
|
|
uint8_t sdvo_data[4 + sizeof(avi_if.body.avi)];
|
2013-03-26 17:44:56 -06:00
|
|
|
struct intel_crtc *intel_crtc = to_intel_crtc(intel_sdvo->base.base.crtc);
|
2010-09-24 13:44:32 -06:00
|
|
|
|
2013-01-17 07:31:31 -07:00
|
|
|
if (intel_sdvo->rgb_quant_range_selectable) {
|
2013-03-26 17:44:56 -06:00
|
|
|
if (intel_crtc->config.limited_color_range)
|
2013-01-17 07:31:31 -07:00
|
|
|
avi_if.body.avi.ITC_EC_Q_SC |= DIP_AVI_RGB_QUANT_RANGE_LIMITED;
|
|
|
|
else
|
|
|
|
avi_if.body.avi.ITC_EC_Q_SC |= DIP_AVI_RGB_QUANT_RANGE_FULL;
|
|
|
|
}
|
|
|
|
|
2013-03-20 10:10:07 -06:00
|
|
|
avi_if.body.avi.VIC = drm_match_cea_mode(adjusted_mode);
|
|
|
|
|
2010-09-24 13:44:32 -06:00
|
|
|
intel_dip_infoframe_csum(&avi_if);
|
|
|
|
|
2012-05-12 12:22:00 -06:00
|
|
|
/* sdvo spec says that the ecc is handled by the hw, and it looks like
|
|
|
|
* we must not send the ecc field, either. */
|
|
|
|
memcpy(sdvo_data, &avi_if, 3);
|
|
|
|
sdvo_data[3] = avi_if.checksum;
|
|
|
|
memcpy(&sdvo_data[4], &avi_if.body, sizeof(avi_if.body.avi));
|
|
|
|
|
2012-10-21 04:52:39 -06:00
|
|
|
return intel_sdvo_write_infoframe(intel_sdvo, SDVO_HBUF_INDEX_AVI_IF,
|
|
|
|
SDVO_HBUF_TX_VSYNC,
|
|
|
|
sdvo_data, sizeof(sdvo_data));
|
2009-02-02 16:11:52 -07:00
|
|
|
}
|
|
|
|
|
2010-08-04 06:50:25 -06:00
|
|
|
static bool intel_sdvo_set_tv_format(struct intel_sdvo *intel_sdvo)
|
2009-03-24 00:02:43 -06:00
|
|
|
{
|
2009-08-23 23:50:26 -06:00
|
|
|
struct intel_sdvo_tv_format format;
|
2010-08-04 06:50:26 -06:00
|
|
|
uint32_t format_map;
|
2009-08-23 23:50:26 -06:00
|
|
|
|
2010-08-04 06:50:26 -06:00
|
|
|
format_map = 1 << intel_sdvo->tv_format_index;
|
2009-08-23 23:50:26 -06:00
|
|
|
memset(&format, 0, sizeof(format));
|
2010-08-04 06:50:25 -06:00
|
|
|
memcpy(&format, &format_map, min(sizeof(format), sizeof(format_map)));
|
2009-08-23 23:50:26 -06:00
|
|
|
|
2010-08-04 06:50:25 -06:00
|
|
|
BUILD_BUG_ON(sizeof(format) != 6);
|
|
|
|
return intel_sdvo_set_value(intel_sdvo,
|
|
|
|
SDVO_CMD_SET_TV_FORMAT,
|
|
|
|
&format, sizeof(format));
|
2009-03-24 00:02:43 -06:00
|
|
|
}
|
|
|
|
|
2010-08-04 06:50:25 -06:00
|
|
|
static bool
|
|
|
|
intel_sdvo_set_output_timings_from_mode(struct intel_sdvo *intel_sdvo,
|
2012-07-17 09:56:50 -06:00
|
|
|
const struct drm_display_mode *mode)
|
2009-02-02 16:11:52 -07:00
|
|
|
{
|
2010-08-04 06:50:25 -06:00
|
|
|
struct intel_sdvo_dtd output_dtd;
|
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-07 15:24:08 -07:00
|
|
|
|
2010-08-04 06:50:25 -06:00
|
|
|
if (!intel_sdvo_set_target_output(intel_sdvo,
|
|
|
|
intel_sdvo->attached_output))
|
|
|
|
return false;
|
2009-02-02 16:11:52 -07:00
|
|
|
|
2010-08-04 06:50:25 -06:00
|
|
|
intel_sdvo_get_dtd_from_mode(&output_dtd, mode);
|
|
|
|
if (!intel_sdvo_set_output_timing(intel_sdvo, &output_dtd))
|
|
|
|
return false;
|
2009-02-02 16:11:52 -07:00
|
|
|
|
2010-08-04 06:50:25 -06:00
|
|
|
return true;
|
|
|
|
}
|
|
|
|
|
2012-04-10 05:55:47 -06:00
|
|
|
/* Asks the sdvo controller for the preferred input mode given the output mode.
|
|
|
|
* Unfortunately we have to set up the full output mode to do that. */
|
2010-08-04 06:50:25 -06:00
|
|
|
static bool
|
2012-04-10 05:55:47 -06:00
|
|
|
intel_sdvo_get_preferred_input_mode(struct intel_sdvo *intel_sdvo,
|
2012-07-17 09:56:50 -06:00
|
|
|
const struct drm_display_mode *mode,
|
2012-04-10 05:55:47 -06:00
|
|
|
struct drm_display_mode *adjusted_mode)
|
2010-08-04 06:50:25 -06:00
|
|
|
{
|
2012-04-10 05:55:47 -06:00
|
|
|
struct intel_sdvo_dtd input_dtd;
|
|
|
|
|
2010-08-04 06:50:25 -06:00
|
|
|
/* Reset the input timing to the screen. Assume always input 0. */
|
|
|
|
if (!intel_sdvo_set_target_input(intel_sdvo))
|
|
|
|
return false;
|
2009-02-02 16:11:52 -07:00
|
|
|
|
2010-08-04 06:50:25 -06:00
|
|
|
if (!intel_sdvo_create_preferred_input_timing(intel_sdvo,
|
|
|
|
mode->clock / 10,
|
|
|
|
mode->hdisplay,
|
|
|
|
mode->vdisplay))
|
|
|
|
return false;
|
2009-02-02 16:11:52 -07:00
|
|
|
|
2010-08-04 06:50:25 -06:00
|
|
|
if (!intel_sdvo_get_preferred_input_timing(intel_sdvo,
|
2012-04-10 05:55:47 -06:00
|
|
|
&input_dtd))
|
2010-08-04 06:50:25 -06:00
|
|
|
return false;
|
2009-02-02 16:11:52 -07:00
|
|
|
|
2012-04-10 05:55:47 -06:00
|
|
|
intel_sdvo_get_mode_from_dtd(adjusted_mode, &input_dtd);
|
2012-10-13 06:29:31 -06:00
|
|
|
intel_sdvo->dtd_sdvo_flags = input_dtd.part2.sdvo_flags;
|
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-07 15:24:08 -07:00
|
|
|
|
2010-08-04 06:50:25 -06:00
|
|
|
return true;
|
|
|
|
}
|
2009-06-29 21:35:35 -06:00
|
|
|
|
2013-04-30 06:01:41 -06:00
|
|
|
static void i9xx_adjust_sdvo_tv_clock(struct intel_crtc_config *pipe_config)
|
|
|
|
{
|
|
|
|
unsigned dotclock = pipe_config->adjusted_mode.clock;
|
|
|
|
struct dpll *clock = &pipe_config->dpll;
|
|
|
|
|
|
|
|
/* SDVO TV has fixed PLL values depend on its clock range,
|
|
|
|
this mirrors vbios setting. */
|
|
|
|
if (dotclock >= 100000 && dotclock < 140500) {
|
|
|
|
clock->p1 = 2;
|
|
|
|
clock->p2 = 10;
|
|
|
|
clock->n = 3;
|
|
|
|
clock->m1 = 16;
|
|
|
|
clock->m2 = 8;
|
|
|
|
} else if (dotclock >= 140500 && dotclock <= 200000) {
|
|
|
|
clock->p1 = 1;
|
|
|
|
clock->p2 = 10;
|
|
|
|
clock->n = 6;
|
|
|
|
clock->m1 = 12;
|
|
|
|
clock->m2 = 8;
|
|
|
|
} else {
|
|
|
|
WARN(1, "SDVO TV clock out of range: %i\n", dotclock);
|
|
|
|
}
|
|
|
|
|
|
|
|
pipe_config->clock_set = true;
|
|
|
|
}
|
|
|
|
|
2013-03-26 17:44:53 -06:00
|
|
|
static bool intel_sdvo_compute_config(struct intel_encoder *encoder,
|
|
|
|
struct intel_crtc_config *pipe_config)
|
2010-08-04 06:50:25 -06:00
|
|
|
{
|
2013-03-26 17:44:53 -06:00
|
|
|
struct intel_sdvo *intel_sdvo = to_intel_sdvo(&encoder->base);
|
|
|
|
struct drm_display_mode *adjusted_mode = &pipe_config->adjusted_mode;
|
|
|
|
struct drm_display_mode *mode = &pipe_config->requested_mode;
|
2009-06-29 21:35:35 -06:00
|
|
|
|
2013-03-26 17:45:01 -06:00
|
|
|
DRM_DEBUG_KMS("forcing bpc to 8 for SDVO\n");
|
|
|
|
pipe_config->pipe_bpp = 8*3;
|
|
|
|
|
2013-03-26 17:44:55 -06:00
|
|
|
if (HAS_PCH_SPLIT(encoder->base.dev))
|
|
|
|
pipe_config->has_pch_encoder = true;
|
|
|
|
|
2010-08-04 06:50:25 -06:00
|
|
|
/* We need to construct preferred input timings based on our
|
|
|
|
* output timings. To do that, we have to set the output
|
|
|
|
* timings, even though this isn't really the right place in
|
|
|
|
* the sequence to do it. Oh well.
|
|
|
|
*/
|
|
|
|
if (intel_sdvo->is_tv) {
|
|
|
|
if (!intel_sdvo_set_output_timings_from_mode(intel_sdvo, mode))
|
|
|
|
return false;
|
2009-06-29 21:35:35 -06:00
|
|
|
|
2012-04-10 05:55:47 -06:00
|
|
|
(void) intel_sdvo_get_preferred_input_mode(intel_sdvo,
|
|
|
|
mode,
|
|
|
|
adjusted_mode);
|
2013-04-30 06:01:45 -06:00
|
|
|
pipe_config->sdvo_tv_clock = true;
|
2010-08-04 06:50:23 -06:00
|
|
|
} else if (intel_sdvo->is_lvds) {
|
2010-08-04 06:50:25 -06:00
|
|
|
if (!intel_sdvo_set_output_timings_from_mode(intel_sdvo,
|
2010-08-25 03:05:17 -06:00
|
|
|
intel_sdvo->sdvo_lvds_fixed_mode))
|
2009-02-02 16:11:52 -07:00
|
|
|
return false;
|
2009-06-29 21:35:35 -06:00
|
|
|
|
2012-04-10 05:55:47 -06:00
|
|
|
(void) intel_sdvo_get_preferred_input_mode(intel_sdvo,
|
|
|
|
mode,
|
|
|
|
adjusted_mode);
|
2009-02-02 16:11:52 -07:00
|
|
|
}
|
2010-08-04 06:50:25 -06:00
|
|
|
|
|
|
|
/* Make the CRTC code factor in the SDVO pixel multiplier. The
|
2010-08-25 03:05:17 -06:00
|
|
|
* SDVO device will factor out the multiplier during mode_set.
|
2010-08-04 06:50:25 -06:00
|
|
|
*/
|
2013-03-26 17:44:53 -06:00
|
|
|
pipe_config->pixel_multiplier =
|
|
|
|
intel_sdvo_get_pixel_multiplier(adjusted_mode);
|
|
|
|
adjusted_mode->clock *= pipe_config->pixel_multiplier;
|
2010-08-04 06:50:25 -06:00
|
|
|
|
2013-01-17 07:31:29 -07:00
|
|
|
if (intel_sdvo->color_range_auto) {
|
|
|
|
/* See CEA-861-E - 5.1 Default Encoding Parameters */
|
2013-02-19 12:21:47 -07:00
|
|
|
/* FIXME: This bit is only valid when using TMDS encoding and 8
|
|
|
|
* bit per color mode. */
|
2013-01-17 07:31:29 -07:00
|
|
|
if (intel_sdvo->has_hdmi_monitor &&
|
2012-12-20 07:41:44 -07:00
|
|
|
drm_match_cea_mode(adjusted_mode) > 1)
|
2013-02-19 12:21:47 -07:00
|
|
|
intel_sdvo->color_range = HDMI_COLOR_RANGE_16_235;
|
2013-01-17 07:31:29 -07:00
|
|
|
else
|
|
|
|
intel_sdvo->color_range = 0;
|
|
|
|
}
|
|
|
|
|
2013-01-17 07:31:28 -07:00
|
|
|
if (intel_sdvo->color_range)
|
2013-03-26 17:44:56 -06:00
|
|
|
pipe_config->limited_color_range = true;
|
2013-01-17 07:31:28 -07:00
|
|
|
|
2013-04-30 06:01:41 -06:00
|
|
|
/* Clock computation needs to happen after pixel multiplier. */
|
|
|
|
if (intel_sdvo->is_tv)
|
|
|
|
i9xx_adjust_sdvo_tv_clock(pipe_config);
|
|
|
|
|
2009-02-02 16:11:52 -07:00
|
|
|
return true;
|
|
|
|
}
|
|
|
|
|
2013-03-26 17:44:53 -06:00
|
|
|
static void intel_sdvo_mode_set(struct intel_encoder *intel_encoder)
|
2009-02-02 16:11:52 -07:00
|
|
|
{
|
2013-03-26 17:44:53 -06:00
|
|
|
struct drm_device *dev = intel_encoder->base.dev;
|
2009-02-02 16:11:52 -07:00
|
|
|
struct drm_i915_private *dev_priv = dev->dev_private;
|
2013-03-26 17:44:53 -06:00
|
|
|
struct drm_crtc *crtc = intel_encoder->base.crtc;
|
2009-02-02 16:11:52 -07:00
|
|
|
struct intel_crtc *intel_crtc = to_intel_crtc(crtc);
|
2013-03-26 17:44:53 -06:00
|
|
|
struct drm_display_mode *adjusted_mode =
|
|
|
|
&intel_crtc->config.adjusted_mode;
|
|
|
|
struct drm_display_mode *mode = &intel_crtc->config.requested_mode;
|
|
|
|
struct intel_sdvo *intel_sdvo = to_intel_sdvo(&intel_encoder->base);
|
2010-08-25 03:05:17 -06:00
|
|
|
u32 sdvox;
|
2009-02-02 16:11:52 -07:00
|
|
|
struct intel_sdvo_in_out_map in_out;
|
drm/i915: handle input/output sdvo timings separately in mode_set
We seem to have a decent confusion between the output timings and the
input timings of the sdvo encoder. If I understand the code correctly,
we use the original mode unchanged for the output timings, safe for
the lvds case. And we should use the adjusted mode for input timings.
Clarify the situation by adding an explicit output_dtd to the sdvo
mode_set function and streamline the code-flow by moving the input and
output mode setting in the sdvo encode together.
Furthermore testing showed that the sdvo input timing needs the
unadjusted dotclock, the sdvo chip will automatically compute the
required pixel multiplier to get a dotclock above 100 MHz.
Fix this up when converting a drm mode to an sdvo dtd.
This regression was introduced in
commit c74696b9c890074c1e1ee3d7496fc71eb3680ced
Author: Pavel Roskin <proski@gnu.org>
Date: Thu Sep 2 14:46:34 2010 -0400
i915: revert some checks added by commit 32aad86f
particularly the following hunk:
diff --git a/drivers/gpu/drm/i915/intel_sdvo.c
b/drivers/gpu/drm/i915/intel_sdvo.c
index 093e914..62d22ae 100644
--- a/drivers/gpu/drm/i915/intel_sdvo.c
+++ b/drivers/gpu/drm/i915/intel_sdvo.c
@@ -1122,11 +1123,9 @@ static void intel_sdvo_mode_set(struct drm_encoder *encoder,
/* We have tried to get input timing in mode_fixup, and filled into
adjusted_mode */
- if (intel_sdvo->is_tv || intel_sdvo->is_lvds) {
- intel_sdvo_get_dtd_from_mode(&input_dtd, adjusted_mode);
+ intel_sdvo_get_dtd_from_mode(&input_dtd, adjusted_mode);
+ if (intel_sdvo->is_tv || intel_sdvo->is_lvds)
input_dtd.part2.sdvo_flags = intel_sdvo->sdvo_flags;
- } else
- intel_sdvo_get_dtd_from_mode(&input_dtd, mode);
/* If it's a TV, we already set the output timing in mode_fixup.
* Otherwise, the output timing is equal to the input timing.
Due to questions raised in review, below a more elaborate analysis of
the bug at hand:
Sdvo seems to have two timings, one is the output timing which will be
sent over whatever is connected on the other side of the sdvo chip (panel,
hdmi screen, tv), the other is the input timing which will be generated by
the gmch pipe. It looks like sdvo is expected to scale between the two.
To make things slightly more complicated, we have a bunch of special
cases:
- For lvds panel we always use a fixed output timing, namely
intel_sdvo->sdvo_lvds_fixed_mode, hence that special case.
- Sdvo has an interface to generate a preferred input timing for a given
output timing. This is the confusing thing that I've tried to clear up
with the follow-on patches.
- A special requirement is that the input pixel clock needs to be between
100MHz and 200MHz (likely to keep it within the electromechanical design
range of PCIe), 270MHz on later gen4+. Lower pixel clocks are
doubled/quadrupled.
The thing this patch tries to fix is that the pipe needs to be
explicitly instructed to double/quadruple the pixels and needs the
correspondingly higher pixel clock, whereas the sdvo adaptor seems to
do that itself and needs the unadjusted pixel clock. For the sdvo
encode side we already set the pixel mutliplier with a different
command (0x21).
This patch tries to fix this mess by:
- Keeping the output mode timing in the unadjusted plain mode, safe
for the lvds case.
- Storing the input timing in the adjusted_mode with the adjusted
pixel clock. This way we don't need to frob around with the core
crtc mode set code.
- Fixing up the pixelclock when constructing the sdvo dtd timing
struct. This is why the first hunk of the patch is an integral part
of the series.
- Dropping the is_tv special case because input_dtd is equivalent to
adjusted_mode after these changes. Follow-up patches clear this up
further (by simply ripping out intel_sdvo->input_dtd because it's
not needed).
v2: Extend commit message with an in-depth bug analysis.
Reported-and-Tested-by: Bernard Blackham <b-linuxgit@largestprime.net>
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=48157
Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: stable@kernel.org
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
2012-04-01 11:16:18 -06:00
|
|
|
struct intel_sdvo_dtd input_dtd, output_dtd;
|
2010-08-25 03:05:17 -06:00
|
|
|
int rate;
|
2009-02-02 16:11:52 -07:00
|
|
|
|
|
|
|
if (!mode)
|
|
|
|
return;
|
|
|
|
|
|
|
|
/* First, set the input mapping for the first input to our controlled
|
|
|
|
* output. This is only correct if we're a single-input device, in
|
|
|
|
* which case the first input is the output from the appropriate SDVO
|
|
|
|
* channel on the motherboard. In a two-input device, the first input
|
|
|
|
* will be SDVOB and the second SDVOC.
|
|
|
|
*/
|
2010-08-04 06:50:23 -06:00
|
|
|
in_out.in0 = intel_sdvo->attached_output;
|
2009-02-02 16:11:52 -07:00
|
|
|
in_out.in1 = 0;
|
|
|
|
|
2010-09-02 12:46:34 -06:00
|
|
|
intel_sdvo_set_value(intel_sdvo,
|
|
|
|
SDVO_CMD_SET_IN_OUT_MAP,
|
|
|
|
&in_out, sizeof(in_out));
|
2009-02-02 16:11:52 -07:00
|
|
|
|
2010-08-25 03:05:17 -06:00
|
|
|
/* Set the output timings to the screen */
|
|
|
|
if (!intel_sdvo_set_target_output(intel_sdvo,
|
|
|
|
intel_sdvo->attached_output))
|
|
|
|
return;
|
2009-02-02 16:11:52 -07:00
|
|
|
|
drm/i915: handle input/output sdvo timings separately in mode_set
We seem to have a decent confusion between the output timings and the
input timings of the sdvo encoder. If I understand the code correctly,
we use the original mode unchanged for the output timings, safe for
the lvds case. And we should use the adjusted mode for input timings.
Clarify the situation by adding an explicit output_dtd to the sdvo
mode_set function and streamline the code-flow by moving the input and
output mode setting in the sdvo encode together.
Furthermore testing showed that the sdvo input timing needs the
unadjusted dotclock, the sdvo chip will automatically compute the
required pixel multiplier to get a dotclock above 100 MHz.
Fix this up when converting a drm mode to an sdvo dtd.
This regression was introduced in
commit c74696b9c890074c1e1ee3d7496fc71eb3680ced
Author: Pavel Roskin <proski@gnu.org>
Date: Thu Sep 2 14:46:34 2010 -0400
i915: revert some checks added by commit 32aad86f
particularly the following hunk:
diff --git a/drivers/gpu/drm/i915/intel_sdvo.c
b/drivers/gpu/drm/i915/intel_sdvo.c
index 093e914..62d22ae 100644
--- a/drivers/gpu/drm/i915/intel_sdvo.c
+++ b/drivers/gpu/drm/i915/intel_sdvo.c
@@ -1122,11 +1123,9 @@ static void intel_sdvo_mode_set(struct drm_encoder *encoder,
/* We have tried to get input timing in mode_fixup, and filled into
adjusted_mode */
- if (intel_sdvo->is_tv || intel_sdvo->is_lvds) {
- intel_sdvo_get_dtd_from_mode(&input_dtd, adjusted_mode);
+ intel_sdvo_get_dtd_from_mode(&input_dtd, adjusted_mode);
+ if (intel_sdvo->is_tv || intel_sdvo->is_lvds)
input_dtd.part2.sdvo_flags = intel_sdvo->sdvo_flags;
- } else
- intel_sdvo_get_dtd_from_mode(&input_dtd, mode);
/* If it's a TV, we already set the output timing in mode_fixup.
* Otherwise, the output timing is equal to the input timing.
Due to questions raised in review, below a more elaborate analysis of
the bug at hand:
Sdvo seems to have two timings, one is the output timing which will be
sent over whatever is connected on the other side of the sdvo chip (panel,
hdmi screen, tv), the other is the input timing which will be generated by
the gmch pipe. It looks like sdvo is expected to scale between the two.
To make things slightly more complicated, we have a bunch of special
cases:
- For lvds panel we always use a fixed output timing, namely
intel_sdvo->sdvo_lvds_fixed_mode, hence that special case.
- Sdvo has an interface to generate a preferred input timing for a given
output timing. This is the confusing thing that I've tried to clear up
with the follow-on patches.
- A special requirement is that the input pixel clock needs to be between
100MHz and 200MHz (likely to keep it within the electromechanical design
range of PCIe), 270MHz on later gen4+. Lower pixel clocks are
doubled/quadrupled.
The thing this patch tries to fix is that the pipe needs to be
explicitly instructed to double/quadruple the pixels and needs the
correspondingly higher pixel clock, whereas the sdvo adaptor seems to
do that itself and needs the unadjusted pixel clock. For the sdvo
encode side we already set the pixel mutliplier with a different
command (0x21).
This patch tries to fix this mess by:
- Keeping the output mode timing in the unadjusted plain mode, safe
for the lvds case.
- Storing the input timing in the adjusted_mode with the adjusted
pixel clock. This way we don't need to frob around with the core
crtc mode set code.
- Fixing up the pixelclock when constructing the sdvo dtd timing
struct. This is why the first hunk of the patch is an integral part
of the series.
- Dropping the is_tv special case because input_dtd is equivalent to
adjusted_mode after these changes. Follow-up patches clear this up
further (by simply ripping out intel_sdvo->input_dtd because it's
not needed).
v2: Extend commit message with an in-depth bug analysis.
Reported-and-Tested-by: Bernard Blackham <b-linuxgit@largestprime.net>
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=48157
Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: stable@kernel.org
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
2012-04-01 11:16:18 -06:00
|
|
|
/* lvds has a special fixed output timing. */
|
|
|
|
if (intel_sdvo->is_lvds)
|
|
|
|
intel_sdvo_get_dtd_from_mode(&output_dtd,
|
|
|
|
intel_sdvo->sdvo_lvds_fixed_mode);
|
|
|
|
else
|
|
|
|
intel_sdvo_get_dtd_from_mode(&output_dtd, mode);
|
2012-04-10 05:55:48 -06:00
|
|
|
if (!intel_sdvo_set_output_timing(intel_sdvo, &output_dtd))
|
|
|
|
DRM_INFO("Setting output timings on %s failed\n",
|
|
|
|
SDVO_NAME(intel_sdvo));
|
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-07 15:24:08 -07:00
|
|
|
|
|
|
|
/* Set the input timing to the screen. Assume always input 0. */
|
2010-08-04 06:50:25 -06:00
|
|
|
if (!intel_sdvo_set_target_input(intel_sdvo))
|
|
|
|
return;
|
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-07 15:24:08 -07:00
|
|
|
|
2011-01-04 13:10:52 -07:00
|
|
|
if (intel_sdvo->has_hdmi_monitor) {
|
|
|
|
intel_sdvo_set_encode(intel_sdvo, SDVO_ENCODE_HDMI);
|
|
|
|
intel_sdvo_set_colorimetry(intel_sdvo,
|
|
|
|
SDVO_COLORIMETRY_RGB256);
|
2013-01-17 07:31:31 -07:00
|
|
|
intel_sdvo_set_avi_infoframe(intel_sdvo, adjusted_mode);
|
2011-01-04 13:10:52 -07:00
|
|
|
} else
|
|
|
|
intel_sdvo_set_encode(intel_sdvo, SDVO_ENCODE_DVI);
|
2009-03-24 00:02:43 -06:00
|
|
|
|
2010-08-25 03:05:17 -06:00
|
|
|
if (intel_sdvo->is_tv &&
|
|
|
|
!intel_sdvo_set_tv_format(intel_sdvo))
|
|
|
|
return;
|
2009-02-02 16:11:52 -07:00
|
|
|
|
drm/i915: handle input/output sdvo timings separately in mode_set
We seem to have a decent confusion between the output timings and the
input timings of the sdvo encoder. If I understand the code correctly,
we use the original mode unchanged for the output timings, safe for
the lvds case. And we should use the adjusted mode for input timings.
Clarify the situation by adding an explicit output_dtd to the sdvo
mode_set function and streamline the code-flow by moving the input and
output mode setting in the sdvo encode together.
Furthermore testing showed that the sdvo input timing needs the
unadjusted dotclock, the sdvo chip will automatically compute the
required pixel multiplier to get a dotclock above 100 MHz.
Fix this up when converting a drm mode to an sdvo dtd.
This regression was introduced in
commit c74696b9c890074c1e1ee3d7496fc71eb3680ced
Author: Pavel Roskin <proski@gnu.org>
Date: Thu Sep 2 14:46:34 2010 -0400
i915: revert some checks added by commit 32aad86f
particularly the following hunk:
diff --git a/drivers/gpu/drm/i915/intel_sdvo.c
b/drivers/gpu/drm/i915/intel_sdvo.c
index 093e914..62d22ae 100644
--- a/drivers/gpu/drm/i915/intel_sdvo.c
+++ b/drivers/gpu/drm/i915/intel_sdvo.c
@@ -1122,11 +1123,9 @@ static void intel_sdvo_mode_set(struct drm_encoder *encoder,
/* We have tried to get input timing in mode_fixup, and filled into
adjusted_mode */
- if (intel_sdvo->is_tv || intel_sdvo->is_lvds) {
- intel_sdvo_get_dtd_from_mode(&input_dtd, adjusted_mode);
+ intel_sdvo_get_dtd_from_mode(&input_dtd, adjusted_mode);
+ if (intel_sdvo->is_tv || intel_sdvo->is_lvds)
input_dtd.part2.sdvo_flags = intel_sdvo->sdvo_flags;
- } else
- intel_sdvo_get_dtd_from_mode(&input_dtd, mode);
/* If it's a TV, we already set the output timing in mode_fixup.
* Otherwise, the output timing is equal to the input timing.
Due to questions raised in review, below a more elaborate analysis of
the bug at hand:
Sdvo seems to have two timings, one is the output timing which will be
sent over whatever is connected on the other side of the sdvo chip (panel,
hdmi screen, tv), the other is the input timing which will be generated by
the gmch pipe. It looks like sdvo is expected to scale between the two.
To make things slightly more complicated, we have a bunch of special
cases:
- For lvds panel we always use a fixed output timing, namely
intel_sdvo->sdvo_lvds_fixed_mode, hence that special case.
- Sdvo has an interface to generate a preferred input timing for a given
output timing. This is the confusing thing that I've tried to clear up
with the follow-on patches.
- A special requirement is that the input pixel clock needs to be between
100MHz and 200MHz (likely to keep it within the electromechanical design
range of PCIe), 270MHz on later gen4+. Lower pixel clocks are
doubled/quadrupled.
The thing this patch tries to fix is that the pipe needs to be
explicitly instructed to double/quadruple the pixels and needs the
correspondingly higher pixel clock, whereas the sdvo adaptor seems to
do that itself and needs the unadjusted pixel clock. For the sdvo
encode side we already set the pixel mutliplier with a different
command (0x21).
This patch tries to fix this mess by:
- Keeping the output mode timing in the unadjusted plain mode, safe
for the lvds case.
- Storing the input timing in the adjusted_mode with the adjusted
pixel clock. This way we don't need to frob around with the core
crtc mode set code.
- Fixing up the pixelclock when constructing the sdvo dtd timing
struct. This is why the first hunk of the patch is an integral part
of the series.
- Dropping the is_tv special case because input_dtd is equivalent to
adjusted_mode after these changes. Follow-up patches clear this up
further (by simply ripping out intel_sdvo->input_dtd because it's
not needed).
v2: Extend commit message with an in-depth bug analysis.
Reported-and-Tested-by: Bernard Blackham <b-linuxgit@largestprime.net>
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=48157
Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: stable@kernel.org
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
2012-04-01 11:16:18 -06:00
|
|
|
/* We have tried to get input timing in mode_fixup, and filled into
|
|
|
|
* adjusted_mode.
|
|
|
|
*/
|
|
|
|
intel_sdvo_get_dtd_from_mode(&input_dtd, adjusted_mode);
|
2012-10-13 06:29:31 -06:00
|
|
|
if (intel_sdvo->is_tv || intel_sdvo->is_lvds)
|
|
|
|
input_dtd.part2.sdvo_flags = intel_sdvo->dtd_sdvo_flags;
|
2012-04-10 05:55:48 -06:00
|
|
|
if (!intel_sdvo_set_input_timing(intel_sdvo, &input_dtd))
|
|
|
|
DRM_INFO("Setting input timings on %s failed\n",
|
|
|
|
SDVO_NAME(intel_sdvo));
|
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-07 15:24:08 -07:00
|
|
|
|
2013-03-26 17:44:53 -06:00
|
|
|
switch (intel_crtc->config.pixel_multiplier) {
|
2010-08-25 03:05:17 -06:00
|
|
|
default:
|
2013-06-01 09:17:04 -06:00
|
|
|
WARN(1, "unknown pixel mutlipler specified\n");
|
2010-08-04 06:50:25 -06:00
|
|
|
case 1: rate = SDVO_CLOCK_RATE_MULT_1X; break;
|
|
|
|
case 2: rate = SDVO_CLOCK_RATE_MULT_2X; break;
|
|
|
|
case 4: rate = SDVO_CLOCK_RATE_MULT_4X; break;
|
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-07 15:24:08 -07:00
|
|
|
}
|
2010-08-04 06:50:25 -06:00
|
|
|
if (!intel_sdvo_set_clock_rate_mult(intel_sdvo, rate))
|
|
|
|
return;
|
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-07 15:24:08 -07:00
|
|
|
|
|
|
|
/* Set the SDVO control regs. */
|
2010-09-16 17:32:17 -06:00
|
|
|
if (INTEL_INFO(dev)->gen >= 4) {
|
2012-01-06 14:45:34 -07:00
|
|
|
/* The real mode polarity is set by the SDVO commands, using
|
|
|
|
* struct intel_sdvo_dtd. */
|
|
|
|
sdvox = SDVO_VSYNC_ACTIVE_HIGH | SDVO_HSYNC_ACTIVE_HIGH;
|
2013-01-17 07:31:28 -07:00
|
|
|
if (!HAS_PCH_SPLIT(dev) && intel_sdvo->is_hdmi)
|
2011-02-21 15:23:52 -07:00
|
|
|
sdvox |= intel_sdvo->color_range;
|
2010-12-16 21:10:51 -07:00
|
|
|
if (INTEL_INFO(dev)->gen < 5)
|
|
|
|
sdvox |= SDVO_BORDER_ENABLE;
|
2009-02-02 16:11:52 -07:00
|
|
|
} else {
|
2010-08-25 03:05:17 -06:00
|
|
|
sdvox = I915_READ(intel_sdvo->sdvo_reg);
|
2010-08-04 06:50:23 -06:00
|
|
|
switch (intel_sdvo->sdvo_reg) {
|
drm/i915: clarify confusion between SDVO and HDMI registers
Some HDMI registers can be used for SDVO, so saying "HDMIB" should be
the same as saying "SDVOB" for a given HW generation. This was not
true and led to confusions and even a regression.
Previously we had:
- SDVO{B,C} defined as the Gen3+ registers
- HDMI{B,C,D} and PCH_SDVOB defined as the PCH registers
But now:
- SDVO{B,C} became GEN3_SDVO{B,C} on SDVO code
- SDVO{B,C} became GEN4_HDMI{B,C} on HDMI code
- HDMI{B,C,D} became PCH_HDMI{B,C,D}
- PCH_SDVOB is still the same thing
v2: Rebase (v1 was sent in May 2012).
Signed-off-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
2013-02-18 15:00:27 -07:00
|
|
|
case GEN3_SDVOB:
|
2009-02-02 16:11:52 -07:00
|
|
|
sdvox &= SDVOB_PRESERVE_MASK;
|
|
|
|
break;
|
drm/i915: clarify confusion between SDVO and HDMI registers
Some HDMI registers can be used for SDVO, so saying "HDMIB" should be
the same as saying "SDVOB" for a given HW generation. This was not
true and led to confusions and even a regression.
Previously we had:
- SDVO{B,C} defined as the Gen3+ registers
- HDMI{B,C,D} and PCH_SDVOB defined as the PCH registers
But now:
- SDVO{B,C} became GEN3_SDVO{B,C} on SDVO code
- SDVO{B,C} became GEN4_HDMI{B,C} on HDMI code
- HDMI{B,C,D} became PCH_HDMI{B,C,D}
- PCH_SDVOB is still the same thing
v2: Rebase (v1 was sent in May 2012).
Signed-off-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
2013-02-18 15:00:27 -07:00
|
|
|
case GEN3_SDVOC:
|
2009-02-02 16:11:52 -07:00
|
|
|
sdvox &= SDVOC_PRESERVE_MASK;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
sdvox |= (9 << 19) | SDVO_BORDER_ENABLE;
|
|
|
|
}
|
2011-10-14 15:16:22 -06:00
|
|
|
|
|
|
|
if (INTEL_PCH_TYPE(dev) >= PCH_CPT)
|
2013-02-19 12:21:46 -07:00
|
|
|
sdvox |= SDVO_PIPE_SEL_CPT(intel_crtc->pipe);
|
2011-10-14 15:16:22 -06:00
|
|
|
else
|
2013-02-19 12:21:46 -07:00
|
|
|
sdvox |= SDVO_PIPE_SEL(intel_crtc->pipe);
|
2011-10-14 15:16:22 -06:00
|
|
|
|
2010-11-22 04:12:46 -07:00
|
|
|
if (intel_sdvo->has_hdmi_audio)
|
2010-08-25 03:05:17 -06:00
|
|
|
sdvox |= SDVO_AUDIO_ENABLE;
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-07 15:24:08 -07:00
|
|
|
|
2010-09-16 17:32:17 -06:00
|
|
|
if (INTEL_INFO(dev)->gen >= 4) {
|
2009-02-02 16:11:52 -07:00
|
|
|
/* done in crtc_mode_set as the dpll_md reg must be written early */
|
|
|
|
} else if (IS_I945G(dev) || IS_I945GM(dev) || IS_G33(dev)) {
|
|
|
|
/* done in crtc_mode_set as it lives inside the dpll register */
|
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-07 15:24:08 -07:00
|
|
|
} else {
|
2013-03-26 17:44:53 -06:00
|
|
|
sdvox |= (intel_crtc->config.pixel_multiplier - 1)
|
|
|
|
<< SDVO_PORT_MULTIPLY_SHIFT;
|
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-07 15:24:08 -07:00
|
|
|
}
|
|
|
|
|
2010-12-16 21:10:51 -07:00
|
|
|
if (input_dtd.part2.sdvo_flags & SDVO_NEED_TO_STALL &&
|
|
|
|
INTEL_INFO(dev)->gen < 5)
|
2009-06-29 21:35:35 -06:00
|
|
|
sdvox |= SDVO_STALL_SELECT;
|
2010-08-04 06:50:23 -06:00
|
|
|
intel_sdvo_write_sdvox(intel_sdvo, sdvox);
|
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-07 15:24:08 -07:00
|
|
|
}
|
|
|
|
|
2012-07-02 06:54:00 -06:00
|
|
|
static bool intel_sdvo_connector_get_hw_state(struct intel_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-07 15:24:08 -07:00
|
|
|
{
|
2012-07-02 06:54:00 -06:00
|
|
|
struct intel_sdvo_connector *intel_sdvo_connector =
|
|
|
|
to_intel_sdvo_connector(&connector->base);
|
|
|
|
struct intel_sdvo *intel_sdvo = intel_attached_sdvo(&connector->base);
|
2013-06-10 06:49:25 -06:00
|
|
|
u16 active_outputs = 0;
|
2012-07-02 06:54:00 -06:00
|
|
|
|
|
|
|
intel_sdvo_get_active_outputs(intel_sdvo, &active_outputs);
|
|
|
|
|
|
|
|
if (active_outputs & intel_sdvo_connector->output_flag)
|
|
|
|
return true;
|
|
|
|
else
|
|
|
|
return false;
|
|
|
|
}
|
|
|
|
|
|
|
|
static bool intel_sdvo_get_hw_state(struct intel_encoder *encoder,
|
|
|
|
enum pipe *pipe)
|
|
|
|
{
|
|
|
|
struct drm_device *dev = encoder->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-07 15:24:08 -07:00
|
|
|
struct drm_i915_private *dev_priv = dev->dev_private;
|
2012-07-02 06:54:00 -06:00
|
|
|
struct intel_sdvo *intel_sdvo = to_intel_sdvo(&encoder->base);
|
2013-06-10 06:49:25 -06:00
|
|
|
u16 active_outputs = 0;
|
2012-07-02 06:54:00 -06:00
|
|
|
u32 tmp;
|
|
|
|
|
|
|
|
tmp = I915_READ(intel_sdvo->sdvo_reg);
|
2013-04-04 14:04:02 -06:00
|
|
|
intel_sdvo_get_active_outputs(intel_sdvo, &active_outputs);
|
2012-07-02 06:54:00 -06:00
|
|
|
|
2013-04-04 14:04:02 -06:00
|
|
|
if (!(tmp & SDVO_ENABLE) && (active_outputs == 0))
|
2012-07-02 06:54:00 -06:00
|
|
|
return false;
|
|
|
|
|
|
|
|
if (HAS_PCH_CPT(dev))
|
|
|
|
*pipe = PORT_TO_PIPE_CPT(tmp);
|
|
|
|
else
|
|
|
|
*pipe = PORT_TO_PIPE(tmp);
|
|
|
|
|
|
|
|
return true;
|
|
|
|
}
|
|
|
|
|
2013-05-14 18:08:26 -06:00
|
|
|
static void intel_sdvo_get_config(struct intel_encoder *encoder,
|
|
|
|
struct intel_crtc_config *pipe_config)
|
|
|
|
{
|
2013-06-06 04:45:25 -06:00
|
|
|
struct drm_device *dev = encoder->base.dev;
|
|
|
|
struct drm_i915_private *dev_priv = dev->dev_private;
|
2013-05-14 18:08:26 -06:00
|
|
|
struct intel_sdvo *intel_sdvo = to_intel_sdvo(&encoder->base);
|
|
|
|
struct intel_sdvo_dtd dtd;
|
2013-06-06 04:45:25 -06:00
|
|
|
int encoder_pixel_multiplier = 0;
|
|
|
|
u32 flags = 0, sdvox;
|
|
|
|
u8 val;
|
2013-05-14 18:08:26 -06:00
|
|
|
bool ret;
|
|
|
|
|
|
|
|
ret = intel_sdvo_get_input_timing(intel_sdvo, &dtd);
|
|
|
|
if (!ret) {
|
2013-06-06 06:55:52 -06:00
|
|
|
/* Some sdvo encoders are not spec compliant and don't
|
|
|
|
* implement the mandatory get_timings function. */
|
2013-05-14 18:08:26 -06:00
|
|
|
DRM_DEBUG_DRIVER("failed to retrieve SDVO DTD\n");
|
2013-06-06 06:55:52 -06:00
|
|
|
pipe_config->quirks |= PIPE_CONFIG_QUIRK_MODE_SYNC_FLAGS;
|
|
|
|
} else {
|
|
|
|
if (dtd.part2.dtd_flags & DTD_FLAG_HSYNC_POSITIVE)
|
|
|
|
flags |= DRM_MODE_FLAG_PHSYNC;
|
|
|
|
else
|
|
|
|
flags |= DRM_MODE_FLAG_NHSYNC;
|
2013-05-14 18:08:26 -06:00
|
|
|
|
2013-06-06 06:55:52 -06:00
|
|
|
if (dtd.part2.dtd_flags & DTD_FLAG_VSYNC_POSITIVE)
|
|
|
|
flags |= DRM_MODE_FLAG_PVSYNC;
|
|
|
|
else
|
|
|
|
flags |= DRM_MODE_FLAG_NVSYNC;
|
2013-05-14 18:08:26 -06:00
|
|
|
}
|
|
|
|
|
|
|
|
pipe_config->adjusted_mode.flags |= flags;
|
|
|
|
|
2013-06-12 03:47:24 -06:00
|
|
|
/*
|
|
|
|
* pixel multiplier readout is tricky: Only on i915g/gm it is stored in
|
|
|
|
* the sdvo port register, on all other platforms it is part of the dpll
|
|
|
|
* state. Since the general pipe state readout happens before the
|
|
|
|
* encoder->get_config we so already have a valid pixel multplier on all
|
|
|
|
* other platfroms.
|
|
|
|
*/
|
2013-06-06 04:45:25 -06:00
|
|
|
if (IS_I915G(dev) || IS_I915GM(dev)) {
|
|
|
|
sdvox = I915_READ(intel_sdvo->sdvo_reg);
|
|
|
|
pipe_config->pixel_multiplier =
|
|
|
|
((sdvox & SDVO_PORT_MULTIPLY_MASK)
|
|
|
|
>> SDVO_PORT_MULTIPLY_SHIFT) + 1;
|
|
|
|
}
|
2013-05-14 18:08:26 -06:00
|
|
|
|
2013-06-06 04:45:25 -06:00
|
|
|
/* Cross check the port pixel multiplier with the sdvo encoder state. */
|
|
|
|
intel_sdvo_get_value(intel_sdvo, SDVO_CMD_GET_CLOCK_RATE_MULT, &val, 1);
|
|
|
|
switch (val) {
|
|
|
|
case SDVO_CLOCK_RATE_MULT_1X:
|
|
|
|
encoder_pixel_multiplier = 1;
|
|
|
|
break;
|
|
|
|
case SDVO_CLOCK_RATE_MULT_2X:
|
|
|
|
encoder_pixel_multiplier = 2;
|
|
|
|
break;
|
|
|
|
case SDVO_CLOCK_RATE_MULT_4X:
|
|
|
|
encoder_pixel_multiplier = 4;
|
|
|
|
break;
|
|
|
|
}
|
2013-06-12 03:47:24 -06:00
|
|
|
|
|
|
|
if(HAS_PCH_SPLIT(dev))
|
|
|
|
return; /* no pixel multiplier readout support yet */
|
|
|
|
|
2013-06-06 04:45:25 -06:00
|
|
|
WARN(encoder_pixel_multiplier != pipe_config->pixel_multiplier,
|
|
|
|
"SDVO pixel multiplier mismatch, port: %i, encoder: %i\n",
|
|
|
|
pipe_config->pixel_multiplier, encoder_pixel_multiplier);
|
2013-05-14 18:08:26 -06:00
|
|
|
}
|
|
|
|
|
2012-07-01 07:31:04 -06:00
|
|
|
static void intel_disable_sdvo(struct intel_encoder *encoder)
|
|
|
|
{
|
|
|
|
struct drm_i915_private *dev_priv = encoder->base.dev->dev_private;
|
|
|
|
struct intel_sdvo *intel_sdvo = to_intel_sdvo(&encoder->base);
|
|
|
|
u32 temp;
|
|
|
|
|
|
|
|
intel_sdvo_set_active_outputs(intel_sdvo, 0);
|
|
|
|
if (0)
|
|
|
|
intel_sdvo_set_encoder_power_state(intel_sdvo,
|
|
|
|
DRM_MODE_DPMS_OFF);
|
|
|
|
|
|
|
|
temp = I915_READ(intel_sdvo->sdvo_reg);
|
|
|
|
if ((temp & SDVO_ENABLE) != 0) {
|
2012-11-21 03:44:23 -07:00
|
|
|
/* HW workaround for IBX, we need to move the port to
|
|
|
|
* transcoder A before disabling it. */
|
|
|
|
if (HAS_PCH_IBX(encoder->base.dev)) {
|
|
|
|
struct drm_crtc *crtc = encoder->base.crtc;
|
|
|
|
int pipe = crtc ? to_intel_crtc(crtc)->pipe : -1;
|
|
|
|
|
|
|
|
if (temp & SDVO_PIPE_B_SELECT) {
|
|
|
|
temp &= ~SDVO_PIPE_B_SELECT;
|
|
|
|
I915_WRITE(intel_sdvo->sdvo_reg, temp);
|
|
|
|
POSTING_READ(intel_sdvo->sdvo_reg);
|
|
|
|
|
|
|
|
/* Again we need to write this twice. */
|
|
|
|
I915_WRITE(intel_sdvo->sdvo_reg, temp);
|
|
|
|
POSTING_READ(intel_sdvo->sdvo_reg);
|
|
|
|
|
|
|
|
/* Transcoder selection bits only update
|
|
|
|
* effectively on vblank. */
|
|
|
|
if (crtc)
|
|
|
|
intel_wait_for_vblank(encoder->base.dev, pipe);
|
|
|
|
else
|
|
|
|
msleep(50);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2012-07-01 07:31:04 -06:00
|
|
|
intel_sdvo_write_sdvox(intel_sdvo, temp & ~SDVO_ENABLE);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
static void intel_enable_sdvo(struct intel_encoder *encoder)
|
|
|
|
{
|
|
|
|
struct drm_device *dev = encoder->base.dev;
|
|
|
|
struct drm_i915_private *dev_priv = dev->dev_private;
|
|
|
|
struct intel_sdvo *intel_sdvo = to_intel_sdvo(&encoder->base);
|
|
|
|
struct intel_crtc *intel_crtc = to_intel_crtc(encoder->base.crtc);
|
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-07 15:24:08 -07:00
|
|
|
u32 temp;
|
2012-07-01 07:31:04 -06:00
|
|
|
bool input1, input2;
|
|
|
|
int i;
|
|
|
|
u8 status;
|
|
|
|
|
|
|
|
temp = I915_READ(intel_sdvo->sdvo_reg);
|
2012-11-21 03:44:23 -07:00
|
|
|
if ((temp & SDVO_ENABLE) == 0) {
|
|
|
|
/* HW workaround for IBX, we need to move the port
|
2013-02-19 12:21:46 -07:00
|
|
|
* to transcoder A before disabling it, so restore it here. */
|
|
|
|
if (HAS_PCH_IBX(dev))
|
|
|
|
temp |= SDVO_PIPE_SEL(intel_crtc->pipe);
|
2012-11-21 03:44:23 -07:00
|
|
|
|
2012-07-01 07:31:04 -06:00
|
|
|
intel_sdvo_write_sdvox(intel_sdvo, temp | SDVO_ENABLE);
|
2012-11-21 03:44:23 -07:00
|
|
|
}
|
2012-07-01 07:31:04 -06:00
|
|
|
for (i = 0; i < 2; i++)
|
|
|
|
intel_wait_for_vblank(dev, intel_crtc->pipe);
|
|
|
|
|
|
|
|
status = intel_sdvo_get_trained_inputs(intel_sdvo, &input1, &input2);
|
|
|
|
/* Warn if the device reported failure to sync.
|
|
|
|
* A lot of SDVO devices fail to notify of sync, but it's
|
|
|
|
* a given it the status is a success, we succeeded.
|
|
|
|
*/
|
|
|
|
if (status == SDVO_CMD_STATUS_SUCCESS && !input1) {
|
|
|
|
DRM_DEBUG_KMS("First %s output reported failure to "
|
|
|
|
"sync\n", SDVO_NAME(intel_sdvo));
|
|
|
|
}
|
|
|
|
|
|
|
|
if (0)
|
|
|
|
intel_sdvo_set_encoder_power_state(intel_sdvo,
|
|
|
|
DRM_MODE_DPMS_ON);
|
|
|
|
intel_sdvo_set_active_outputs(intel_sdvo, intel_sdvo->attached_output);
|
|
|
|
}
|
|
|
|
|
2013-05-28 03:35:02 -06:00
|
|
|
/* Special dpms function to support cloning between dvo/sdvo/crt. */
|
drm/i915: convert dpms functions of dvo/sdvo/crt
Yeah, big patch but I couldn't come up with a neat idea of how to
split it up further, that wouldn't break dpms on cloned configs
somehow. But the changes in dvo/sdvo/crt are all pretty much
orthonogal, so it's not too bad a patch.
These are the only encoders that support cloning, which requires a few
special changes compared to the previous patches.
- Compute the desired state of the display pipe by walking all
connected encoders and checking whether any has active connectors.
To make this clearer, drop the old mode parameter to the crtc dpms
function and rename it to intel_crtc_update_dpms.
- There's the curious case of intel_crtc->dpms_mode. With the previous
patches to remove the overlay pipe A code and to rework the load
detect pipe code, the big users are gone. We still keep it to avoid
enabling the pipe twice, but we duplicate this logic with
crtc->active, too. Still, leave this for now and just push a fake
dpms mode into it that reflects the state of the display pipe.
Changes in the encoder dpms functions:
- We clamp the dpms state to the supported range right away. This is
escpecially important for the VGA outputs, where only older hw
supports the intermediate states. This (and the crt->adpa_reg patch)
allows us to unify the crt dpms code again between all variants
(gmch, vlv and pch).
- We only enable/disable the output for dvo/sdvo and leave the encoder
running. The encoder will be disabled/enabled when we switch the
state of the entire output pipeline (which will happen right away
for non-cloned setups). This way the duplication is reduced and
strange interaction when disabling output ports at the wrong time
avoided.
The dpms code for all three types of connectors contains a bit of
duplicated logic, but I think keeping these special cases separate is
simpler: CRT is the only one that hanldes intermediate dpms state
(which requires extra logic to enable/disable things in the right
order), and introducing some abstraction just to share the code
between dvo and sdvo smells like overkill. We can do that once someone
bothers to implement cloning for the more modern outputs. But I doubt
that this will ever happen.
v2: s/crtc/crt/_set_dpms, noticed by Paulo Zanoni.
Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-Off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
2012-07-01 14:42:24 -06:00
|
|
|
static void intel_sdvo_dpms(struct drm_connector *connector, int 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-07 15:24:08 -07:00
|
|
|
{
|
drm/i915: convert dpms functions of dvo/sdvo/crt
Yeah, big patch but I couldn't come up with a neat idea of how to
split it up further, that wouldn't break dpms on cloned configs
somehow. But the changes in dvo/sdvo/crt are all pretty much
orthonogal, so it's not too bad a patch.
These are the only encoders that support cloning, which requires a few
special changes compared to the previous patches.
- Compute the desired state of the display pipe by walking all
connected encoders and checking whether any has active connectors.
To make this clearer, drop the old mode parameter to the crtc dpms
function and rename it to intel_crtc_update_dpms.
- There's the curious case of intel_crtc->dpms_mode. With the previous
patches to remove the overlay pipe A code and to rework the load
detect pipe code, the big users are gone. We still keep it to avoid
enabling the pipe twice, but we duplicate this logic with
crtc->active, too. Still, leave this for now and just push a fake
dpms mode into it that reflects the state of the display pipe.
Changes in the encoder dpms functions:
- We clamp the dpms state to the supported range right away. This is
escpecially important for the VGA outputs, where only older hw
supports the intermediate states. This (and the crt->adpa_reg patch)
allows us to unify the crt dpms code again between all variants
(gmch, vlv and pch).
- We only enable/disable the output for dvo/sdvo and leave the encoder
running. The encoder will be disabled/enabled when we switch the
state of the entire output pipeline (which will happen right away
for non-cloned setups). This way the duplication is reduced and
strange interaction when disabling output ports at the wrong time
avoided.
The dpms code for all three types of connectors contains a bit of
duplicated logic, but I think keeping these special cases separate is
simpler: CRT is the only one that hanldes intermediate dpms state
(which requires extra logic to enable/disable things in the right
order), and introducing some abstraction just to share the code
between dvo and sdvo smells like overkill. We can do that once someone
bothers to implement cloning for the more modern outputs. But I doubt
that this will ever happen.
v2: s/crtc/crt/_set_dpms, noticed by Paulo Zanoni.
Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-Off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
2012-07-01 14:42:24 -06:00
|
|
|
struct drm_crtc *crtc;
|
|
|
|
struct intel_sdvo *intel_sdvo = intel_attached_sdvo(connector);
|
|
|
|
|
|
|
|
/* dvo supports only 2 dpms states. */
|
|
|
|
if (mode != DRM_MODE_DPMS_ON)
|
|
|
|
mode = DRM_MODE_DPMS_OFF;
|
|
|
|
|
|
|
|
if (mode == connector->dpms)
|
|
|
|
return;
|
|
|
|
|
|
|
|
connector->dpms = mode;
|
|
|
|
|
|
|
|
/* Only need to change hw state when actually enabled */
|
|
|
|
crtc = intel_sdvo->base.base.crtc;
|
|
|
|
if (!crtc) {
|
|
|
|
intel_sdvo->base.connectors_active = false;
|
|
|
|
return;
|
|
|
|
}
|
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-07 15:24:08 -07:00
|
|
|
|
2013-05-28 03:35:02 -06:00
|
|
|
/* We set active outputs manually below in case pipe dpms doesn't change
|
|
|
|
* due to cloning. */
|
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-07 15:24:08 -07:00
|
|
|
if (mode != DRM_MODE_DPMS_ON) {
|
2010-08-04 06:50:23 -06:00
|
|
|
intel_sdvo_set_active_outputs(intel_sdvo, 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-07 15:24:08 -07:00
|
|
|
if (0)
|
2010-08-04 06:50:23 -06:00
|
|
|
intel_sdvo_set_encoder_power_state(intel_sdvo, 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-07 15:24:08 -07:00
|
|
|
|
drm/i915: convert dpms functions of dvo/sdvo/crt
Yeah, big patch but I couldn't come up with a neat idea of how to
split it up further, that wouldn't break dpms on cloned configs
somehow. But the changes in dvo/sdvo/crt are all pretty much
orthonogal, so it's not too bad a patch.
These are the only encoders that support cloning, which requires a few
special changes compared to the previous patches.
- Compute the desired state of the display pipe by walking all
connected encoders and checking whether any has active connectors.
To make this clearer, drop the old mode parameter to the crtc dpms
function and rename it to intel_crtc_update_dpms.
- There's the curious case of intel_crtc->dpms_mode. With the previous
patches to remove the overlay pipe A code and to rework the load
detect pipe code, the big users are gone. We still keep it to avoid
enabling the pipe twice, but we duplicate this logic with
crtc->active, too. Still, leave this for now and just push a fake
dpms mode into it that reflects the state of the display pipe.
Changes in the encoder dpms functions:
- We clamp the dpms state to the supported range right away. This is
escpecially important for the VGA outputs, where only older hw
supports the intermediate states. This (and the crt->adpa_reg patch)
allows us to unify the crt dpms code again between all variants
(gmch, vlv and pch).
- We only enable/disable the output for dvo/sdvo and leave the encoder
running. The encoder will be disabled/enabled when we switch the
state of the entire output pipeline (which will happen right away
for non-cloned setups). This way the duplication is reduced and
strange interaction when disabling output ports at the wrong time
avoided.
The dpms code for all three types of connectors contains a bit of
duplicated logic, but I think keeping these special cases separate is
simpler: CRT is the only one that hanldes intermediate dpms state
(which requires extra logic to enable/disable things in the right
order), and introducing some abstraction just to share the code
between dvo and sdvo smells like overkill. We can do that once someone
bothers to implement cloning for the more modern outputs. But I doubt
that this will ever happen.
v2: s/crtc/crt/_set_dpms, noticed by Paulo Zanoni.
Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-Off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
2012-07-01 14:42:24 -06:00
|
|
|
intel_sdvo->base.connectors_active = false;
|
|
|
|
|
|
|
|
intel_crtc_update_dpms(crtc);
|
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-07 15:24:08 -07:00
|
|
|
} else {
|
drm/i915: convert dpms functions of dvo/sdvo/crt
Yeah, big patch but I couldn't come up with a neat idea of how to
split it up further, that wouldn't break dpms on cloned configs
somehow. But the changes in dvo/sdvo/crt are all pretty much
orthonogal, so it's not too bad a patch.
These are the only encoders that support cloning, which requires a few
special changes compared to the previous patches.
- Compute the desired state of the display pipe by walking all
connected encoders and checking whether any has active connectors.
To make this clearer, drop the old mode parameter to the crtc dpms
function and rename it to intel_crtc_update_dpms.
- There's the curious case of intel_crtc->dpms_mode. With the previous
patches to remove the overlay pipe A code and to rework the load
detect pipe code, the big users are gone. We still keep it to avoid
enabling the pipe twice, but we duplicate this logic with
crtc->active, too. Still, leave this for now and just push a fake
dpms mode into it that reflects the state of the display pipe.
Changes in the encoder dpms functions:
- We clamp the dpms state to the supported range right away. This is
escpecially important for the VGA outputs, where only older hw
supports the intermediate states. This (and the crt->adpa_reg patch)
allows us to unify the crt dpms code again between all variants
(gmch, vlv and pch).
- We only enable/disable the output for dvo/sdvo and leave the encoder
running. The encoder will be disabled/enabled when we switch the
state of the entire output pipeline (which will happen right away
for non-cloned setups). This way the duplication is reduced and
strange interaction when disabling output ports at the wrong time
avoided.
The dpms code for all three types of connectors contains a bit of
duplicated logic, but I think keeping these special cases separate is
simpler: CRT is the only one that hanldes intermediate dpms state
(which requires extra logic to enable/disable things in the right
order), and introducing some abstraction just to share the code
between dvo and sdvo smells like overkill. We can do that once someone
bothers to implement cloning for the more modern outputs. But I doubt
that this will ever happen.
v2: s/crtc/crt/_set_dpms, noticed by Paulo Zanoni.
Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-Off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
2012-07-01 14:42:24 -06:00
|
|
|
intel_sdvo->base.connectors_active = true;
|
|
|
|
|
|
|
|
intel_crtc_update_dpms(crtc);
|
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-07 15:24:08 -07:00
|
|
|
|
|
|
|
if (0)
|
2010-08-04 06:50:23 -06:00
|
|
|
intel_sdvo_set_encoder_power_state(intel_sdvo, mode);
|
|
|
|
intel_sdvo_set_active_outputs(intel_sdvo, intel_sdvo->attached_output);
|
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-07 15:24:08 -07:00
|
|
|
}
|
2012-07-02 13:54:27 -06:00
|
|
|
|
2012-08-31 09:37:33 -06:00
|
|
|
intel_modeset_check_state(connector->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-07 15:24:08 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
static int intel_sdvo_mode_valid(struct drm_connector *connector,
|
|
|
|
struct drm_display_mode *mode)
|
|
|
|
{
|
2010-09-09 09:20:55 -06:00
|
|
|
struct intel_sdvo *intel_sdvo = intel_attached_sdvo(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-07 15:24:08 -07:00
|
|
|
|
|
|
|
if (mode->flags & DRM_MODE_FLAG_DBLSCAN)
|
|
|
|
return MODE_NO_DBLESCAN;
|
|
|
|
|
2010-08-04 06:50:23 -06:00
|
|
|
if (intel_sdvo->pixel_clock_min > mode->clock)
|
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-07 15:24:08 -07:00
|
|
|
return MODE_CLOCK_LOW;
|
|
|
|
|
2010-08-04 06:50:23 -06:00
|
|
|
if (intel_sdvo->pixel_clock_max < mode->clock)
|
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-07 15:24:08 -07:00
|
|
|
return MODE_CLOCK_HIGH;
|
|
|
|
|
2010-08-08 07:28:23 -06:00
|
|
|
if (intel_sdvo->is_lvds) {
|
2010-08-04 06:50:23 -06:00
|
|
|
if (mode->hdisplay > intel_sdvo->sdvo_lvds_fixed_mode->hdisplay)
|
2009-06-29 21:35:35 -06:00
|
|
|
return MODE_PANEL;
|
|
|
|
|
2010-08-04 06:50:23 -06:00
|
|
|
if (mode->vdisplay > intel_sdvo->sdvo_lvds_fixed_mode->vdisplay)
|
2009-06-29 21:35:35 -06:00
|
|
|
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-07 15:24:08 -07:00
|
|
|
return MODE_OK;
|
|
|
|
}
|
|
|
|
|
2010-08-04 06:50:23 -06:00
|
|
|
static bool intel_sdvo_get_capabilities(struct intel_sdvo *intel_sdvo, struct intel_sdvo_caps *caps)
|
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-07 15:24:08 -07:00
|
|
|
{
|
2011-01-25 06:59:37 -07:00
|
|
|
BUILD_BUG_ON(sizeof(*caps) != 8);
|
2010-09-24 05:52:03 -06:00
|
|
|
if (!intel_sdvo_get_value(intel_sdvo,
|
|
|
|
SDVO_CMD_GET_DEVICE_CAPS,
|
|
|
|
caps, sizeof(*caps)))
|
|
|
|
return false;
|
|
|
|
|
|
|
|
DRM_DEBUG_KMS("SDVO capabilities:\n"
|
|
|
|
" vendor_id: %d\n"
|
|
|
|
" device_id: %d\n"
|
|
|
|
" device_rev_id: %d\n"
|
|
|
|
" sdvo_version_major: %d\n"
|
|
|
|
" sdvo_version_minor: %d\n"
|
|
|
|
" sdvo_inputs_mask: %d\n"
|
|
|
|
" smooth_scaling: %d\n"
|
|
|
|
" sharp_scaling: %d\n"
|
|
|
|
" up_scaling: %d\n"
|
|
|
|
" down_scaling: %d\n"
|
|
|
|
" stall_support: %d\n"
|
|
|
|
" output_flags: %d\n",
|
|
|
|
caps->vendor_id,
|
|
|
|
caps->device_id,
|
|
|
|
caps->device_rev_id,
|
|
|
|
caps->sdvo_version_major,
|
|
|
|
caps->sdvo_version_minor,
|
|
|
|
caps->sdvo_inputs_mask,
|
|
|
|
caps->smooth_scaling,
|
|
|
|
caps->sharp_scaling,
|
|
|
|
caps->up_scaling,
|
|
|
|
caps->down_scaling,
|
|
|
|
caps->stall_support,
|
|
|
|
caps->output_flags);
|
|
|
|
|
|
|
|
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-07 15:24:08 -07:00
|
|
|
}
|
|
|
|
|
2012-08-29 07:43:58 -06:00
|
|
|
static uint16_t intel_sdvo_get_hotplug_support(struct intel_sdvo *intel_sdvo)
|
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-07 15:24:08 -07:00
|
|
|
{
|
2012-05-04 03:29:56 -06:00
|
|
|
struct drm_device *dev = intel_sdvo->base.base.dev;
|
2012-08-29 07:43:58 -06:00
|
|
|
uint16_t hotplug;
|
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-07 15:24:08 -07:00
|
|
|
|
2012-05-04 03:29:56 -06:00
|
|
|
/* HW Erratum: SDVO Hotplug is broken on all i945G chips, there's noise
|
|
|
|
* on the line. */
|
|
|
|
if (IS_I945G(dev) || IS_I945GM(dev))
|
2012-08-29 07:43:58 -06:00
|
|
|
return 0;
|
2012-05-04 03:29:56 -06:00
|
|
|
|
2012-08-29 07:43:58 -06:00
|
|
|
if (!intel_sdvo_get_value(intel_sdvo, SDVO_CMD_GET_HOT_PLUG_SUPPORT,
|
|
|
|
&hotplug, sizeof(hotplug)))
|
|
|
|
return 0;
|
2012-05-04 03:29:56 -06:00
|
|
|
|
2012-08-29 07:43:58 -06:00
|
|
|
return hotplug;
|
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-07 15:24:08 -07:00
|
|
|
}
|
|
|
|
|
2011-09-21 10:13:30 -06:00
|
|
|
static void intel_sdvo_enable_hotplug(struct intel_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-07 15:24:08 -07:00
|
|
|
{
|
2011-09-21 10:13:30 -06:00
|
|
|
struct intel_sdvo *intel_sdvo = to_intel_sdvo(&encoder->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-07 15:24:08 -07:00
|
|
|
|
2012-08-29 07:43:58 -06:00
|
|
|
intel_sdvo_write_cmd(intel_sdvo, SDVO_CMD_SET_ACTIVE_HOT_PLUG,
|
|
|
|
&intel_sdvo->hotplug_active, 2);
|
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-07 15:24:08 -07:00
|
|
|
}
|
|
|
|
|
2009-07-23 03:11:34 -06:00
|
|
|
static bool
|
2010-08-04 06:50:23 -06:00
|
|
|
intel_sdvo_multifunc_encoder(struct intel_sdvo *intel_sdvo)
|
2009-07-23 03:11:34 -06:00
|
|
|
{
|
2011-01-25 06:28:29 -07:00
|
|
|
/* Is there more than one type of output? */
|
2011-06-16 14:36:24 -06:00
|
|
|
return hweight16(intel_sdvo->caps.output_flags) > 1;
|
2009-07-23 03:11:34 -06:00
|
|
|
}
|
|
|
|
|
2010-07-20 16:44:45 -06:00
|
|
|
static struct edid *
|
2010-09-24 05:52:03 -06:00
|
|
|
intel_sdvo_get_edid(struct drm_connector *connector)
|
2010-07-20 16:44:45 -06:00
|
|
|
{
|
2010-09-24 05:52:03 -06:00
|
|
|
struct intel_sdvo *sdvo = intel_attached_sdvo(connector);
|
|
|
|
return drm_get_edid(connector, &sdvo->ddc);
|
2010-07-20 16:44:45 -06:00
|
|
|
}
|
|
|
|
|
2010-09-15 03:40:38 -06:00
|
|
|
/* Mac mini hack -- use the same DDC as the analog connector */
|
|
|
|
static struct edid *
|
|
|
|
intel_sdvo_get_analog_edid(struct drm_connector *connector)
|
|
|
|
{
|
2010-07-20 16:44:45 -06:00
|
|
|
struct drm_i915_private *dev_priv = connector->dev->dev_private;
|
2010-09-15 03:40:38 -06:00
|
|
|
|
2010-11-23 15:37:01 -07:00
|
|
|
return drm_get_edid(connector,
|
2012-03-27 12:36:14 -06:00
|
|
|
intel_gmbus_get_adapter(dev_priv,
|
2013-05-09 17:03:18 -06:00
|
|
|
dev_priv->vbt.crt_ddc_pin));
|
2010-09-15 03:40:38 -06:00
|
|
|
}
|
|
|
|
|
2012-04-16 15:07:40 -06:00
|
|
|
static enum drm_connector_status
|
2011-06-16 14:36:25 -06:00
|
|
|
intel_sdvo_tmds_sink_detect(struct drm_connector *connector)
|
2009-04-01 23:13:26 -06:00
|
|
|
{
|
2010-09-09 09:20:55 -06:00
|
|
|
struct intel_sdvo *intel_sdvo = intel_attached_sdvo(connector);
|
2010-09-14 10:58:19 -06:00
|
|
|
enum drm_connector_status status;
|
|
|
|
struct edid *edid;
|
2009-04-01 23:13:26 -06:00
|
|
|
|
2010-09-24 05:52:03 -06:00
|
|
|
edid = intel_sdvo_get_edid(connector);
|
2009-09-03 23:07:54 -06:00
|
|
|
|
2010-08-04 06:50:23 -06:00
|
|
|
if (edid == NULL && intel_sdvo_multifunc_encoder(intel_sdvo)) {
|
2010-09-24 05:52:03 -06:00
|
|
|
u8 ddc, saved_ddc = intel_sdvo->ddc_bus;
|
2010-09-14 10:58:19 -06:00
|
|
|
|
2010-01-07 19:58:20 -07:00
|
|
|
/*
|
|
|
|
* Don't use the 1 as the argument of DDC bus switch to get
|
|
|
|
* the EDID. It is used for SDVO SPD ROM.
|
|
|
|
*/
|
2010-09-14 10:58:19 -06:00
|
|
|
for (ddc = intel_sdvo->ddc_bus >> 1; ddc > 1; ddc >>= 1) {
|
2010-09-24 05:52:03 -06:00
|
|
|
intel_sdvo->ddc_bus = ddc;
|
|
|
|
edid = intel_sdvo_get_edid(connector);
|
|
|
|
if (edid)
|
2010-01-07 19:58:20 -07:00
|
|
|
break;
|
|
|
|
}
|
2010-09-24 05:52:03 -06:00
|
|
|
/*
|
|
|
|
* If we found the EDID on the other bus,
|
|
|
|
* assume that is the correct DDC bus.
|
|
|
|
*/
|
|
|
|
if (edid == NULL)
|
|
|
|
intel_sdvo->ddc_bus = saved_ddc;
|
2010-01-07 19:58:20 -07:00
|
|
|
}
|
2010-09-14 10:58:19 -06:00
|
|
|
|
|
|
|
/*
|
|
|
|
* When there is no edid and no monitor is connected with VGA
|
|
|
|
* port, try to use the CRT ddc to read the EDID for DVI-connector.
|
2009-09-03 23:07:54 -06:00
|
|
|
*/
|
2010-09-15 03:40:38 -06:00
|
|
|
if (edid == NULL)
|
|
|
|
edid = intel_sdvo_get_analog_edid(connector);
|
2010-04-29 12:05:18 -06:00
|
|
|
|
2010-09-15 03:42:50 -06:00
|
|
|
status = connector_status_unknown;
|
2009-04-01 23:13:26 -06:00
|
|
|
if (edid != NULL) {
|
2010-04-29 12:05:18 -06:00
|
|
|
/* DDC bus is shared, match EDID to connector type */
|
2010-09-14 10:58:19 -06:00
|
|
|
if (edid->input & DRM_EDID_INPUT_DIGITAL) {
|
|
|
|
status = connector_status_connected;
|
2010-11-22 04:12:46 -07:00
|
|
|
if (intel_sdvo->is_hdmi) {
|
|
|
|
intel_sdvo->has_hdmi_monitor = drm_detect_hdmi_monitor(edid);
|
|
|
|
intel_sdvo->has_hdmi_audio = drm_detect_monitor_audio(edid);
|
2013-01-17 07:31:31 -07:00
|
|
|
intel_sdvo->rgb_quant_range_selectable =
|
|
|
|
drm_rgb_quant_range_selectable(edid);
|
2010-11-22 04:12:46 -07:00
|
|
|
}
|
2011-02-09 13:01:16 -07:00
|
|
|
} else
|
|
|
|
status = connector_status_disconnected;
|
2010-09-14 10:58:19 -06:00
|
|
|
kfree(edid);
|
|
|
|
}
|
2010-09-19 02:29:33 -06:00
|
|
|
|
|
|
|
if (status == connector_status_connected) {
|
|
|
|
struct intel_sdvo_connector *intel_sdvo_connector = to_intel_sdvo_connector(connector);
|
2012-02-23 09:14:47 -07:00
|
|
|
if (intel_sdvo_connector->force_audio != HDMI_AUDIO_AUTO)
|
|
|
|
intel_sdvo->has_hdmi_audio = (intel_sdvo_connector->force_audio == HDMI_AUDIO_ON);
|
2010-09-19 02:29:33 -06:00
|
|
|
}
|
|
|
|
|
2009-07-28 21:31:18 -06:00
|
|
|
return status;
|
2009-04-01 23:13:26 -06:00
|
|
|
}
|
|
|
|
|
2011-06-20 07:45:50 -06:00
|
|
|
static bool
|
|
|
|
intel_sdvo_connector_matches_edid(struct intel_sdvo_connector *sdvo,
|
|
|
|
struct edid *edid)
|
|
|
|
{
|
|
|
|
bool monitor_is_digital = !!(edid->input & DRM_EDID_INPUT_DIGITAL);
|
|
|
|
bool connector_is_digital = !!IS_DIGITAL(sdvo);
|
|
|
|
|
|
|
|
DRM_DEBUG_KMS("connector_is_digital? %d, monitor_is_digital? %d\n",
|
|
|
|
connector_is_digital, monitor_is_digital);
|
|
|
|
return connector_is_digital == monitor_is_digital;
|
|
|
|
}
|
|
|
|
|
2010-09-09 16:51:02 -06:00
|
|
|
static enum drm_connector_status
|
2010-09-14 04:07:23 -06:00
|
|
|
intel_sdvo_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-07 15:24:08 -07:00
|
|
|
{
|
2009-07-23 03:11:34 -06:00
|
|
|
uint16_t response;
|
2010-09-09 09:20:55 -06:00
|
|
|
struct intel_sdvo *intel_sdvo = intel_attached_sdvo(connector);
|
2010-08-04 06:50:24 -06:00
|
|
|
struct intel_sdvo_connector *intel_sdvo_connector = to_intel_sdvo_connector(connector);
|
2010-03-30 00:06:33 -06:00
|
|
|
enum drm_connector_status ret;
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-07 15:24:08 -07:00
|
|
|
|
2012-11-23 04:57:56 -07:00
|
|
|
if (!intel_sdvo_get_value(intel_sdvo,
|
|
|
|
SDVO_CMD_GET_ATTACHED_DISPLAYS,
|
|
|
|
&response, 2))
|
2010-08-04 06:50:25 -06:00
|
|
|
return connector_status_unknown;
|
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-07 15:24:08 -07:00
|
|
|
|
2010-09-24 05:52:03 -06:00
|
|
|
DRM_DEBUG_KMS("SDVO response %d %d [%x]\n",
|
|
|
|
response & 0xff, response >> 8,
|
|
|
|
intel_sdvo_connector->output_flag);
|
2009-02-02 16:11:52 -07:00
|
|
|
|
2009-07-23 03:11:34 -06:00
|
|
|
if (response == 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-07 15:24:08 -07:00
|
|
|
return connector_status_disconnected;
|
2009-07-23 03:11:34 -06:00
|
|
|
|
2010-08-04 06:50:23 -06:00
|
|
|
intel_sdvo->attached_output = response;
|
2010-03-30 00:06:33 -06:00
|
|
|
|
2011-01-04 13:10:52 -07:00
|
|
|
intel_sdvo->has_hdmi_monitor = false;
|
|
|
|
intel_sdvo->has_hdmi_audio = false;
|
2013-01-17 07:31:31 -07:00
|
|
|
intel_sdvo->rgb_quant_range_selectable = false;
|
2011-01-04 13:10:52 -07:00
|
|
|
|
2010-08-04 06:50:24 -06:00
|
|
|
if ((intel_sdvo_connector->output_flag & response) == 0)
|
2010-03-30 00:06:33 -06:00
|
|
|
ret = connector_status_disconnected;
|
2011-02-09 13:01:16 -07:00
|
|
|
else if (IS_TMDS(intel_sdvo_connector))
|
2011-06-16 14:36:25 -06:00
|
|
|
ret = intel_sdvo_tmds_sink_detect(connector);
|
2011-02-09 13:01:16 -07:00
|
|
|
else {
|
|
|
|
struct edid *edid;
|
|
|
|
|
|
|
|
/* if we have an edid check it matches the connection */
|
|
|
|
edid = intel_sdvo_get_edid(connector);
|
|
|
|
if (edid == NULL)
|
|
|
|
edid = intel_sdvo_get_analog_edid(connector);
|
|
|
|
if (edid != NULL) {
|
2011-06-20 07:45:50 -06:00
|
|
|
if (intel_sdvo_connector_matches_edid(intel_sdvo_connector,
|
|
|
|
edid))
|
2011-02-09 13:01:16 -07:00
|
|
|
ret = connector_status_connected;
|
2011-06-20 07:45:50 -06:00
|
|
|
else
|
|
|
|
ret = connector_status_disconnected;
|
|
|
|
|
2011-02-09 13:01:16 -07:00
|
|
|
kfree(edid);
|
|
|
|
} else
|
|
|
|
ret = connector_status_connected;
|
|
|
|
}
|
2010-03-30 00:06:33 -06:00
|
|
|
|
|
|
|
/* May update encoder flag for like clock for SDVO TV, etc.*/
|
|
|
|
if (ret == connector_status_connected) {
|
2010-08-04 06:50:23 -06:00
|
|
|
intel_sdvo->is_tv = false;
|
|
|
|
intel_sdvo->is_lvds = false;
|
2010-03-30 00:06:33 -06:00
|
|
|
|
2013-04-30 06:01:45 -06:00
|
|
|
if (response & SDVO_TV_MASK)
|
2010-08-04 06:50:23 -06:00
|
|
|
intel_sdvo->is_tv = true;
|
2010-03-30 00:06:33 -06:00
|
|
|
if (response & SDVO_LVDS_MASK)
|
2010-08-08 07:28:23 -06:00
|
|
|
intel_sdvo->is_lvds = intel_sdvo->sdvo_lvds_fixed_mode != NULL;
|
2009-07-23 03:11:34 -06:00
|
|
|
}
|
2010-03-30 00:06:33 -06:00
|
|
|
|
|
|
|
return ret;
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-07 15:24:08 -07:00
|
|
|
}
|
|
|
|
|
2009-02-02 16:11:52 -07:00
|
|
|
static void intel_sdvo_get_ddc_modes(struct drm_connector *connector)
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-07 15:24:08 -07:00
|
|
|
{
|
2010-09-15 03:40:38 -06:00
|
|
|
struct edid *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-07 15:24:08 -07:00
|
|
|
|
|
|
|
/* set the bus switch and get the modes */
|
2010-09-24 05:52:03 -06:00
|
|
|
edid = intel_sdvo_get_edid(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-07 15:24:08 -07:00
|
|
|
|
2009-09-03 23:07:54 -06:00
|
|
|
/*
|
|
|
|
* Mac mini hack. On this device, the DVI-I connector shares one DDC
|
|
|
|
* link between analog and digital outputs. So, if the regular SDVO
|
|
|
|
* DDC fails, check to see if the analog output is disconnected, in
|
|
|
|
* which case we'll look there for the digital DDC data.
|
2009-02-02 16:11:52 -07:00
|
|
|
*/
|
2010-07-20 16:44:45 -06:00
|
|
|
if (edid == NULL)
|
|
|
|
edid = intel_sdvo_get_analog_edid(connector);
|
|
|
|
|
2010-09-15 03:40:38 -06:00
|
|
|
if (edid != NULL) {
|
2011-06-20 07:45:50 -06:00
|
|
|
if (intel_sdvo_connector_matches_edid(to_intel_sdvo_connector(connector),
|
|
|
|
edid)) {
|
2010-11-23 15:37:01 -07:00
|
|
|
drm_mode_connector_update_edid_property(connector, edid);
|
|
|
|
drm_add_edid_modes(connector, edid);
|
|
|
|
}
|
2011-02-09 13:01:16 -07:00
|
|
|
|
2010-09-15 03:40:38 -06:00
|
|
|
kfree(edid);
|
2009-02-02 16:11:52 -07:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Set of SDVO TV modes.
|
|
|
|
* Note! This is in reply order (see loop in get_tv_modes).
|
|
|
|
* XXX: all 60Hz refresh?
|
|
|
|
*/
|
2011-01-26 02:49:47 -07:00
|
|
|
static const struct drm_display_mode sdvo_tv_modes[] = {
|
2009-03-24 00:02:43 -06:00
|
|
|
{ DRM_MODE("320x200", DRM_MODE_TYPE_DRIVER, 5815, 320, 321, 384,
|
|
|
|
416, 0, 200, 201, 232, 233, 0,
|
2009-02-02 16:11:52 -07:00
|
|
|
DRM_MODE_FLAG_PHSYNC | DRM_MODE_FLAG_PVSYNC) },
|
2009-03-24 00:02:43 -06:00
|
|
|
{ DRM_MODE("320x240", DRM_MODE_TYPE_DRIVER, 6814, 320, 321, 384,
|
|
|
|
416, 0, 240, 241, 272, 273, 0,
|
2009-02-02 16:11:52 -07:00
|
|
|
DRM_MODE_FLAG_PHSYNC | DRM_MODE_FLAG_PVSYNC) },
|
2009-03-24 00:02:43 -06:00
|
|
|
{ DRM_MODE("400x300", DRM_MODE_TYPE_DRIVER, 9910, 400, 401, 464,
|
|
|
|
496, 0, 300, 301, 332, 333, 0,
|
2009-02-02 16:11:52 -07:00
|
|
|
DRM_MODE_FLAG_PHSYNC | DRM_MODE_FLAG_PVSYNC) },
|
2009-03-24 00:02:43 -06:00
|
|
|
{ DRM_MODE("640x350", DRM_MODE_TYPE_DRIVER, 16913, 640, 641, 704,
|
|
|
|
736, 0, 350, 351, 382, 383, 0,
|
2009-02-02 16:11:52 -07:00
|
|
|
DRM_MODE_FLAG_PHSYNC | DRM_MODE_FLAG_PVSYNC) },
|
2009-03-24 00:02:43 -06:00
|
|
|
{ DRM_MODE("640x400", DRM_MODE_TYPE_DRIVER, 19121, 640, 641, 704,
|
|
|
|
736, 0, 400, 401, 432, 433, 0,
|
2009-02-02 16:11:52 -07:00
|
|
|
DRM_MODE_FLAG_PHSYNC | DRM_MODE_FLAG_PVSYNC) },
|
2009-03-24 00:02:43 -06:00
|
|
|
{ DRM_MODE("640x480", DRM_MODE_TYPE_DRIVER, 22654, 640, 641, 704,
|
|
|
|
736, 0, 480, 481, 512, 513, 0,
|
2009-02-02 16:11:52 -07:00
|
|
|
DRM_MODE_FLAG_PHSYNC | DRM_MODE_FLAG_PVSYNC) },
|
2009-03-24 00:02:43 -06:00
|
|
|
{ DRM_MODE("704x480", DRM_MODE_TYPE_DRIVER, 24624, 704, 705, 768,
|
|
|
|
800, 0, 480, 481, 512, 513, 0,
|
2009-02-02 16:11:52 -07:00
|
|
|
DRM_MODE_FLAG_PHSYNC | DRM_MODE_FLAG_PVSYNC) },
|
2009-03-24 00:02:43 -06:00
|
|
|
{ DRM_MODE("704x576", DRM_MODE_TYPE_DRIVER, 29232, 704, 705, 768,
|
|
|
|
800, 0, 576, 577, 608, 609, 0,
|
2009-02-02 16:11:52 -07:00
|
|
|
DRM_MODE_FLAG_PHSYNC | DRM_MODE_FLAG_PVSYNC) },
|
2009-03-24 00:02:43 -06:00
|
|
|
{ DRM_MODE("720x350", DRM_MODE_TYPE_DRIVER, 18751, 720, 721, 784,
|
|
|
|
816, 0, 350, 351, 382, 383, 0,
|
2009-02-02 16:11:52 -07:00
|
|
|
DRM_MODE_FLAG_PHSYNC | DRM_MODE_FLAG_PVSYNC) },
|
2009-03-24 00:02:43 -06:00
|
|
|
{ DRM_MODE("720x400", DRM_MODE_TYPE_DRIVER, 21199, 720, 721, 784,
|
|
|
|
816, 0, 400, 401, 432, 433, 0,
|
2009-02-02 16:11:52 -07:00
|
|
|
DRM_MODE_FLAG_PHSYNC | DRM_MODE_FLAG_PVSYNC) },
|
2009-03-24 00:02:43 -06:00
|
|
|
{ DRM_MODE("720x480", DRM_MODE_TYPE_DRIVER, 25116, 720, 721, 784,
|
|
|
|
816, 0, 480, 481, 512, 513, 0,
|
2009-02-02 16:11:52 -07:00
|
|
|
DRM_MODE_FLAG_PHSYNC | DRM_MODE_FLAG_PVSYNC) },
|
2009-03-24 00:02:43 -06:00
|
|
|
{ DRM_MODE("720x540", DRM_MODE_TYPE_DRIVER, 28054, 720, 721, 784,
|
|
|
|
816, 0, 540, 541, 572, 573, 0,
|
2009-02-02 16:11:52 -07:00
|
|
|
DRM_MODE_FLAG_PHSYNC | DRM_MODE_FLAG_PVSYNC) },
|
2009-03-24 00:02:43 -06:00
|
|
|
{ DRM_MODE("720x576", DRM_MODE_TYPE_DRIVER, 29816, 720, 721, 784,
|
|
|
|
816, 0, 576, 577, 608, 609, 0,
|
2009-02-02 16:11:52 -07:00
|
|
|
DRM_MODE_FLAG_PHSYNC | DRM_MODE_FLAG_PVSYNC) },
|
2009-03-24 00:02:43 -06:00
|
|
|
{ DRM_MODE("768x576", DRM_MODE_TYPE_DRIVER, 31570, 768, 769, 832,
|
|
|
|
864, 0, 576, 577, 608, 609, 0,
|
2009-02-02 16:11:52 -07:00
|
|
|
DRM_MODE_FLAG_PHSYNC | DRM_MODE_FLAG_PVSYNC) },
|
2009-03-24 00:02:43 -06:00
|
|
|
{ DRM_MODE("800x600", DRM_MODE_TYPE_DRIVER, 34030, 800, 801, 864,
|
|
|
|
896, 0, 600, 601, 632, 633, 0,
|
2009-02-02 16:11:52 -07:00
|
|
|
DRM_MODE_FLAG_PHSYNC | DRM_MODE_FLAG_PVSYNC) },
|
2009-03-24 00:02:43 -06:00
|
|
|
{ DRM_MODE("832x624", DRM_MODE_TYPE_DRIVER, 36581, 832, 833, 896,
|
|
|
|
928, 0, 624, 625, 656, 657, 0,
|
2009-02-02 16:11:52 -07:00
|
|
|
DRM_MODE_FLAG_PHSYNC | DRM_MODE_FLAG_PVSYNC) },
|
2009-03-24 00:02:43 -06:00
|
|
|
{ DRM_MODE("920x766", DRM_MODE_TYPE_DRIVER, 48707, 920, 921, 984,
|
|
|
|
1016, 0, 766, 767, 798, 799, 0,
|
2009-02-02 16:11:52 -07:00
|
|
|
DRM_MODE_FLAG_PHSYNC | DRM_MODE_FLAG_PVSYNC) },
|
2009-03-24 00:02:43 -06:00
|
|
|
{ DRM_MODE("1024x768", DRM_MODE_TYPE_DRIVER, 53827, 1024, 1025, 1088,
|
|
|
|
1120, 0, 768, 769, 800, 801, 0,
|
2009-02-02 16:11:52 -07:00
|
|
|
DRM_MODE_FLAG_PHSYNC | DRM_MODE_FLAG_PVSYNC) },
|
2009-03-24 00:02:43 -06:00
|
|
|
{ DRM_MODE("1280x1024", DRM_MODE_TYPE_DRIVER, 87265, 1280, 1281, 1344,
|
|
|
|
1376, 0, 1024, 1025, 1056, 1057, 0,
|
2009-02-02 16:11:52 -07:00
|
|
|
DRM_MODE_FLAG_PHSYNC | DRM_MODE_FLAG_PVSYNC) },
|
|
|
|
};
|
|
|
|
|
|
|
|
static void intel_sdvo_get_tv_modes(struct drm_connector *connector)
|
|
|
|
{
|
2010-09-09 09:20:55 -06:00
|
|
|
struct intel_sdvo *intel_sdvo = intel_attached_sdvo(connector);
|
2009-03-24 00:02:43 -06:00
|
|
|
struct intel_sdvo_sdtv_resolution_request tv_res;
|
2009-08-23 23:50:26 -06:00
|
|
|
uint32_t reply = 0, format_map = 0;
|
|
|
|
int i;
|
2009-02-02 16:11:52 -07:00
|
|
|
|
|
|
|
/* Read the list of supported input resolutions for the selected TV
|
|
|
|
* format.
|
|
|
|
*/
|
2010-08-04 06:50:26 -06:00
|
|
|
format_map = 1 << intel_sdvo->tv_format_index;
|
2009-08-23 23:50:26 -06:00
|
|
|
memcpy(&tv_res, &format_map,
|
2010-08-04 06:50:25 -06:00
|
|
|
min(sizeof(format_map), sizeof(struct intel_sdvo_sdtv_resolution_request)));
|
2009-08-23 23:50:26 -06:00
|
|
|
|
2010-08-04 06:50:25 -06:00
|
|
|
if (!intel_sdvo_set_target_output(intel_sdvo, intel_sdvo->attached_output))
|
|
|
|
return;
|
2009-08-23 23:50:26 -06:00
|
|
|
|
2010-08-04 06:50:25 -06:00
|
|
|
BUILD_BUG_ON(sizeof(tv_res) != 3);
|
2010-09-24 05:52:03 -06:00
|
|
|
if (!intel_sdvo_write_cmd(intel_sdvo,
|
|
|
|
SDVO_CMD_GET_SDTV_RESOLUTION_SUPPORT,
|
2010-08-04 06:50:25 -06:00
|
|
|
&tv_res, sizeof(tv_res)))
|
|
|
|
return;
|
|
|
|
if (!intel_sdvo_read_response(intel_sdvo, &reply, 3))
|
2009-02-02 16:11:52 -07:00
|
|
|
return;
|
|
|
|
|
|
|
|
for (i = 0; i < ARRAY_SIZE(sdvo_tv_modes); i++)
|
2009-03-24 00:02:43 -06:00
|
|
|
if (reply & (1 << i)) {
|
|
|
|
struct drm_display_mode *nmode;
|
|
|
|
nmode = drm_mode_duplicate(connector->dev,
|
2010-08-04 06:50:25 -06:00
|
|
|
&sdvo_tv_modes[i]);
|
2009-03-24 00:02:43 -06:00
|
|
|
if (nmode)
|
|
|
|
drm_mode_probed_add(connector, nmode);
|
|
|
|
}
|
2009-02-02 16:11:52 -07:00
|
|
|
}
|
|
|
|
|
2009-05-12 21:20:06 -06:00
|
|
|
static void intel_sdvo_get_lvds_modes(struct drm_connector *connector)
|
|
|
|
{
|
2010-09-09 09:20:55 -06:00
|
|
|
struct intel_sdvo *intel_sdvo = intel_attached_sdvo(connector);
|
2009-05-12 21:20:06 -06:00
|
|
|
struct drm_i915_private *dev_priv = connector->dev->dev_private;
|
2009-06-29 21:35:35 -06:00
|
|
|
struct drm_display_mode *newmode;
|
2009-05-12 21:20:06 -06:00
|
|
|
|
|
|
|
/*
|
2013-06-10 01:47:58 -06:00
|
|
|
* Fetch modes from VBT. For SDVO prefer the VBT mode since some
|
2013-06-27 04:40:44 -06:00
|
|
|
* SDVO->LVDS transcoders can't cope with the EDID mode.
|
2009-05-12 21:20:06 -06:00
|
|
|
*/
|
2013-05-09 17:03:18 -06:00
|
|
|
if (dev_priv->vbt.sdvo_lvds_vbt_mode != NULL) {
|
2009-05-12 21:20:06 -06:00
|
|
|
newmode = drm_mode_duplicate(connector->dev,
|
2013-05-09 17:03:18 -06:00
|
|
|
dev_priv->vbt.sdvo_lvds_vbt_mode);
|
2009-05-12 21:20:06 -06:00
|
|
|
if (newmode != NULL) {
|
|
|
|
/* Guarantee the mode is preferred */
|
|
|
|
newmode->type = (DRM_MODE_TYPE_PREFERRED |
|
|
|
|
DRM_MODE_TYPE_DRIVER);
|
|
|
|
drm_mode_probed_add(connector, newmode);
|
|
|
|
}
|
|
|
|
}
|
2009-06-29 21:35:35 -06:00
|
|
|
|
2013-06-27 04:40:44 -06:00
|
|
|
/*
|
|
|
|
* Attempt to get the mode list from DDC.
|
|
|
|
* Assume that the preferred modes are
|
|
|
|
* arranged in priority order.
|
|
|
|
*/
|
|
|
|
intel_ddc_get_modes(connector, &intel_sdvo->ddc);
|
|
|
|
|
2009-06-29 21:35:35 -06:00
|
|
|
list_for_each_entry(newmode, &connector->probed_modes, head) {
|
|
|
|
if (newmode->type & DRM_MODE_TYPE_PREFERRED) {
|
2010-08-04 06:50:23 -06:00
|
|
|
intel_sdvo->sdvo_lvds_fixed_mode =
|
2009-06-29 21:35:35 -06:00
|
|
|
drm_mode_duplicate(connector->dev, newmode);
|
2010-08-25 03:05:17 -06:00
|
|
|
|
2010-08-08 07:28:23 -06:00
|
|
|
intel_sdvo->is_lvds = true;
|
2009-06-29 21:35:35 -06:00
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2009-05-12 21:20:06 -06:00
|
|
|
}
|
|
|
|
|
2009-02-02 16:11:52 -07:00
|
|
|
static int intel_sdvo_get_modes(struct drm_connector *connector)
|
|
|
|
{
|
2010-08-04 06:50:24 -06:00
|
|
|
struct intel_sdvo_connector *intel_sdvo_connector = to_intel_sdvo_connector(connector);
|
2009-02-02 16:11:52 -07:00
|
|
|
|
2010-08-04 06:50:24 -06:00
|
|
|
if (IS_TV(intel_sdvo_connector))
|
2009-02-02 16:11:52 -07:00
|
|
|
intel_sdvo_get_tv_modes(connector);
|
2010-08-04 06:50:24 -06:00
|
|
|
else if (IS_LVDS(intel_sdvo_connector))
|
2009-05-12 21:20:06 -06:00
|
|
|
intel_sdvo_get_lvds_modes(connector);
|
2009-02-02 16:11:52 -07:00
|
|
|
else
|
|
|
|
intel_sdvo_get_ddc_modes(connector);
|
|
|
|
|
2010-08-04 06:50:25 -06:00
|
|
|
return !list_empty(&connector->probed_modes);
|
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-07 15:24:08 -07:00
|
|
|
}
|
|
|
|
|
2010-08-04 06:50:27 -06:00
|
|
|
static void
|
|
|
|
intel_sdvo_destroy_enhance_property(struct drm_connector *connector)
|
2009-09-10 01:45:46 -06:00
|
|
|
{
|
2010-08-04 06:50:24 -06:00
|
|
|
struct intel_sdvo_connector *intel_sdvo_connector = to_intel_sdvo_connector(connector);
|
2009-09-10 01:45:46 -06:00
|
|
|
struct drm_device *dev = connector->dev;
|
|
|
|
|
2010-08-04 06:50:28 -06:00
|
|
|
if (intel_sdvo_connector->left)
|
|
|
|
drm_property_destroy(dev, intel_sdvo_connector->left);
|
|
|
|
if (intel_sdvo_connector->right)
|
|
|
|
drm_property_destroy(dev, intel_sdvo_connector->right);
|
|
|
|
if (intel_sdvo_connector->top)
|
|
|
|
drm_property_destroy(dev, intel_sdvo_connector->top);
|
|
|
|
if (intel_sdvo_connector->bottom)
|
|
|
|
drm_property_destroy(dev, intel_sdvo_connector->bottom);
|
|
|
|
if (intel_sdvo_connector->hpos)
|
|
|
|
drm_property_destroy(dev, intel_sdvo_connector->hpos);
|
|
|
|
if (intel_sdvo_connector->vpos)
|
|
|
|
drm_property_destroy(dev, intel_sdvo_connector->vpos);
|
|
|
|
if (intel_sdvo_connector->saturation)
|
|
|
|
drm_property_destroy(dev, intel_sdvo_connector->saturation);
|
|
|
|
if (intel_sdvo_connector->contrast)
|
|
|
|
drm_property_destroy(dev, intel_sdvo_connector->contrast);
|
|
|
|
if (intel_sdvo_connector->hue)
|
|
|
|
drm_property_destroy(dev, intel_sdvo_connector->hue);
|
|
|
|
if (intel_sdvo_connector->sharpness)
|
|
|
|
drm_property_destroy(dev, intel_sdvo_connector->sharpness);
|
|
|
|
if (intel_sdvo_connector->flicker_filter)
|
|
|
|
drm_property_destroy(dev, intel_sdvo_connector->flicker_filter);
|
|
|
|
if (intel_sdvo_connector->flicker_filter_2d)
|
|
|
|
drm_property_destroy(dev, intel_sdvo_connector->flicker_filter_2d);
|
|
|
|
if (intel_sdvo_connector->flicker_filter_adaptive)
|
|
|
|
drm_property_destroy(dev, intel_sdvo_connector->flicker_filter_adaptive);
|
|
|
|
if (intel_sdvo_connector->tv_luma_filter)
|
|
|
|
drm_property_destroy(dev, intel_sdvo_connector->tv_luma_filter);
|
|
|
|
if (intel_sdvo_connector->tv_chroma_filter)
|
|
|
|
drm_property_destroy(dev, intel_sdvo_connector->tv_chroma_filter);
|
2010-08-04 06:50:29 -06:00
|
|
|
if (intel_sdvo_connector->dot_crawl)
|
|
|
|
drm_property_destroy(dev, intel_sdvo_connector->dot_crawl);
|
2010-08-04 06:50:28 -06:00
|
|
|
if (intel_sdvo_connector->brightness)
|
|
|
|
drm_property_destroy(dev, intel_sdvo_connector->brightness);
|
2009-09-10 01:45:46 -06: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-07 15:24:08 -07:00
|
|
|
static void intel_sdvo_destroy(struct drm_connector *connector)
|
|
|
|
{
|
2010-08-04 06:50:24 -06:00
|
|
|
struct intel_sdvo_connector *intel_sdvo_connector = to_intel_sdvo_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-07 15:24:08 -07:00
|
|
|
|
2010-08-04 06:50:28 -06:00
|
|
|
if (intel_sdvo_connector->tv_format)
|
2009-08-23 23:50:26 -06:00
|
|
|
drm_property_destroy(connector->dev,
|
2010-08-04 06:50:28 -06:00
|
|
|
intel_sdvo_connector->tv_format);
|
2009-09-10 01:45:46 -06:00
|
|
|
|
2010-03-29 07:22:55 -06:00
|
|
|
intel_sdvo_destroy_enhance_property(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-07 15:24:08 -07:00
|
|
|
drm_sysfs_connector_remove(connector);
|
|
|
|
drm_connector_cleanup(connector);
|
2012-11-12 09:31:36 -07:00
|
|
|
kfree(intel_sdvo_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-07 15:24:08 -07:00
|
|
|
}
|
|
|
|
|
2011-02-09 11:46:58 -07:00
|
|
|
static bool intel_sdvo_detect_hdmi_audio(struct drm_connector *connector)
|
|
|
|
{
|
|
|
|
struct intel_sdvo *intel_sdvo = intel_attached_sdvo(connector);
|
|
|
|
struct edid *edid;
|
|
|
|
bool has_audio = false;
|
|
|
|
|
|
|
|
if (!intel_sdvo->is_hdmi)
|
|
|
|
return false;
|
|
|
|
|
|
|
|
edid = intel_sdvo_get_edid(connector);
|
|
|
|
if (edid != NULL && edid->input & DRM_EDID_INPUT_DIGITAL)
|
|
|
|
has_audio = drm_detect_monitor_audio(edid);
|
2012-08-15 03:32:36 -06:00
|
|
|
kfree(edid);
|
2011-02-09 11:46:58 -07:00
|
|
|
|
|
|
|
return has_audio;
|
|
|
|
}
|
|
|
|
|
2009-08-23 23:50:26 -06:00
|
|
|
static int
|
|
|
|
intel_sdvo_set_property(struct drm_connector *connector,
|
|
|
|
struct drm_property *property,
|
|
|
|
uint64_t val)
|
|
|
|
{
|
2010-09-09 09:20:55 -06:00
|
|
|
struct intel_sdvo *intel_sdvo = intel_attached_sdvo(connector);
|
2010-08-04 06:50:24 -06:00
|
|
|
struct intel_sdvo_connector *intel_sdvo_connector = to_intel_sdvo_connector(connector);
|
2011-02-21 15:23:52 -07:00
|
|
|
struct drm_i915_private *dev_priv = connector->dev->dev_private;
|
2009-09-10 01:45:46 -06:00
|
|
|
uint16_t temp_value;
|
2010-08-04 06:50:25 -06:00
|
|
|
uint8_t cmd;
|
|
|
|
int ret;
|
2009-08-23 23:50:26 -06:00
|
|
|
|
2012-10-11 19:36:04 -06:00
|
|
|
ret = drm_object_property_set_value(&connector->base, property, val);
|
2010-08-04 06:50:25 -06:00
|
|
|
if (ret)
|
|
|
|
return ret;
|
2009-08-23 23:50:26 -06:00
|
|
|
|
2011-05-12 15:17:24 -06:00
|
|
|
if (property == dev_priv->force_audio_property) {
|
2011-02-09 11:46:58 -07:00
|
|
|
int i = val;
|
|
|
|
bool has_audio;
|
|
|
|
|
|
|
|
if (i == intel_sdvo_connector->force_audio)
|
2010-09-19 02:29:33 -06:00
|
|
|
return 0;
|
|
|
|
|
2011-02-09 11:46:58 -07:00
|
|
|
intel_sdvo_connector->force_audio = i;
|
2010-09-19 02:29:33 -06:00
|
|
|
|
2012-02-23 09:14:47 -07:00
|
|
|
if (i == HDMI_AUDIO_AUTO)
|
2011-02-09 11:46:58 -07:00
|
|
|
has_audio = intel_sdvo_detect_hdmi_audio(connector);
|
|
|
|
else
|
2012-02-23 09:14:47 -07:00
|
|
|
has_audio = (i == HDMI_AUDIO_ON);
|
2010-09-19 02:29:33 -06:00
|
|
|
|
2011-02-09 11:46:58 -07:00
|
|
|
if (has_audio == intel_sdvo->has_hdmi_audio)
|
2010-09-19 02:29:33 -06:00
|
|
|
return 0;
|
|
|
|
|
2011-02-09 11:46:58 -07:00
|
|
|
intel_sdvo->has_hdmi_audio = has_audio;
|
2010-09-19 02:29:33 -06:00
|
|
|
goto done;
|
|
|
|
}
|
|
|
|
|
2011-02-21 15:23:52 -07:00
|
|
|
if (property == dev_priv->broadcast_rgb_property) {
|
2013-04-22 09:07:23 -06:00
|
|
|
bool old_auto = intel_sdvo->color_range_auto;
|
|
|
|
uint32_t old_range = intel_sdvo->color_range;
|
|
|
|
|
2013-01-17 07:31:29 -07:00
|
|
|
switch (val) {
|
|
|
|
case INTEL_BROADCAST_RGB_AUTO:
|
|
|
|
intel_sdvo->color_range_auto = true;
|
|
|
|
break;
|
|
|
|
case INTEL_BROADCAST_RGB_FULL:
|
|
|
|
intel_sdvo->color_range_auto = false;
|
|
|
|
intel_sdvo->color_range = 0;
|
|
|
|
break;
|
|
|
|
case INTEL_BROADCAST_RGB_LIMITED:
|
|
|
|
intel_sdvo->color_range_auto = false;
|
2013-02-19 12:21:47 -07:00
|
|
|
/* FIXME: this bit is only valid when using TMDS
|
|
|
|
* encoding and 8 bit per color mode. */
|
|
|
|
intel_sdvo->color_range = HDMI_COLOR_RANGE_16_235;
|
2013-01-17 07:31:29 -07:00
|
|
|
break;
|
|
|
|
default:
|
|
|
|
return -EINVAL;
|
|
|
|
}
|
2013-04-22 09:07:23 -06:00
|
|
|
|
|
|
|
if (old_auto == intel_sdvo->color_range_auto &&
|
|
|
|
old_range == intel_sdvo->color_range)
|
|
|
|
return 0;
|
|
|
|
|
2010-09-19 02:29:33 -06:00
|
|
|
goto done;
|
|
|
|
}
|
|
|
|
|
2010-08-04 06:50:28 -06:00
|
|
|
#define CHECK_PROPERTY(name, NAME) \
|
|
|
|
if (intel_sdvo_connector->name == property) { \
|
|
|
|
if (intel_sdvo_connector->cur_##name == temp_value) return 0; \
|
|
|
|
if (intel_sdvo_connector->max_##name < temp_value) return -EINVAL; \
|
|
|
|
cmd = SDVO_CMD_SET_##NAME; \
|
|
|
|
intel_sdvo_connector->cur_##name = temp_value; \
|
|
|
|
goto set_value; \
|
|
|
|
}
|
|
|
|
|
|
|
|
if (property == intel_sdvo_connector->tv_format) {
|
2010-08-04 06:50:25 -06:00
|
|
|
if (val >= TV_FORMAT_NUM)
|
|
|
|
return -EINVAL;
|
|
|
|
|
2010-08-04 06:50:26 -06:00
|
|
|
if (intel_sdvo->tv_format_index ==
|
2010-08-04 06:50:24 -06:00
|
|
|
intel_sdvo_connector->tv_format_supported[val])
|
2010-08-04 06:50:25 -06:00
|
|
|
return 0;
|
2009-08-23 23:50:26 -06:00
|
|
|
|
2010-08-04 06:50:26 -06:00
|
|
|
intel_sdvo->tv_format_index = intel_sdvo_connector->tv_format_supported[val];
|
2010-08-04 06:50:28 -06:00
|
|
|
goto done;
|
2010-08-04 06:50:25 -06:00
|
|
|
} else if (IS_TV_OR_LVDS(intel_sdvo_connector)) {
|
2009-09-10 01:45:46 -06:00
|
|
|
temp_value = val;
|
2010-08-04 06:50:28 -06:00
|
|
|
if (intel_sdvo_connector->left == property) {
|
2012-10-11 19:36:04 -06:00
|
|
|
drm_object_property_set_value(&connector->base,
|
2010-08-04 06:50:28 -06:00
|
|
|
intel_sdvo_connector->right, val);
|
2010-08-04 06:50:24 -06:00
|
|
|
if (intel_sdvo_connector->left_margin == temp_value)
|
2010-08-04 06:50:25 -06:00
|
|
|
return 0;
|
2009-09-10 01:45:46 -06:00
|
|
|
|
2010-08-04 06:50:24 -06:00
|
|
|
intel_sdvo_connector->left_margin = temp_value;
|
|
|
|
intel_sdvo_connector->right_margin = temp_value;
|
|
|
|
temp_value = intel_sdvo_connector->max_hscan -
|
2010-08-04 06:50:28 -06:00
|
|
|
intel_sdvo_connector->left_margin;
|
2009-09-10 01:45:46 -06:00
|
|
|
cmd = SDVO_CMD_SET_OVERSCAN_H;
|
2010-08-04 06:50:28 -06:00
|
|
|
goto set_value;
|
|
|
|
} else if (intel_sdvo_connector->right == property) {
|
2012-10-11 19:36:04 -06:00
|
|
|
drm_object_property_set_value(&connector->base,
|
2010-08-04 06:50:28 -06:00
|
|
|
intel_sdvo_connector->left, val);
|
2010-08-04 06:50:24 -06:00
|
|
|
if (intel_sdvo_connector->right_margin == temp_value)
|
2010-08-04 06:50:25 -06:00
|
|
|
return 0;
|
2009-09-10 01:45:46 -06:00
|
|
|
|
2010-08-04 06:50:24 -06:00
|
|
|
intel_sdvo_connector->left_margin = temp_value;
|
|
|
|
intel_sdvo_connector->right_margin = temp_value;
|
|
|
|
temp_value = intel_sdvo_connector->max_hscan -
|
|
|
|
intel_sdvo_connector->left_margin;
|
2009-09-10 01:45:46 -06:00
|
|
|
cmd = SDVO_CMD_SET_OVERSCAN_H;
|
2010-08-04 06:50:28 -06:00
|
|
|
goto set_value;
|
|
|
|
} else if (intel_sdvo_connector->top == property) {
|
2012-10-11 19:36:04 -06:00
|
|
|
drm_object_property_set_value(&connector->base,
|
2010-08-04 06:50:28 -06:00
|
|
|
intel_sdvo_connector->bottom, val);
|
2010-08-04 06:50:24 -06:00
|
|
|
if (intel_sdvo_connector->top_margin == temp_value)
|
2010-08-04 06:50:25 -06:00
|
|
|
return 0;
|
2009-09-10 01:45:46 -06:00
|
|
|
|
2010-08-04 06:50:24 -06:00
|
|
|
intel_sdvo_connector->top_margin = temp_value;
|
|
|
|
intel_sdvo_connector->bottom_margin = temp_value;
|
|
|
|
temp_value = intel_sdvo_connector->max_vscan -
|
2010-08-04 06:50:28 -06:00
|
|
|
intel_sdvo_connector->top_margin;
|
2009-09-10 01:45:46 -06:00
|
|
|
cmd = SDVO_CMD_SET_OVERSCAN_V;
|
2010-08-04 06:50:28 -06:00
|
|
|
goto set_value;
|
|
|
|
} else if (intel_sdvo_connector->bottom == property) {
|
2012-10-11 19:36:04 -06:00
|
|
|
drm_object_property_set_value(&connector->base,
|
2010-08-04 06:50:28 -06:00
|
|
|
intel_sdvo_connector->top, val);
|
2010-08-04 06:50:24 -06:00
|
|
|
if (intel_sdvo_connector->bottom_margin == temp_value)
|
2010-08-04 06:50:25 -06:00
|
|
|
return 0;
|
|
|
|
|
2010-08-04 06:50:24 -06:00
|
|
|
intel_sdvo_connector->top_margin = temp_value;
|
|
|
|
intel_sdvo_connector->bottom_margin = temp_value;
|
|
|
|
temp_value = intel_sdvo_connector->max_vscan -
|
2010-08-04 06:50:28 -06:00
|
|
|
intel_sdvo_connector->top_margin;
|
2009-09-10 01:45:46 -06:00
|
|
|
cmd = SDVO_CMD_SET_OVERSCAN_V;
|
2010-08-04 06:50:28 -06:00
|
|
|
goto set_value;
|
|
|
|
}
|
|
|
|
CHECK_PROPERTY(hpos, HPOS)
|
|
|
|
CHECK_PROPERTY(vpos, VPOS)
|
|
|
|
CHECK_PROPERTY(saturation, SATURATION)
|
|
|
|
CHECK_PROPERTY(contrast, CONTRAST)
|
|
|
|
CHECK_PROPERTY(hue, HUE)
|
|
|
|
CHECK_PROPERTY(brightness, BRIGHTNESS)
|
|
|
|
CHECK_PROPERTY(sharpness, SHARPNESS)
|
|
|
|
CHECK_PROPERTY(flicker_filter, FLICKER_FILTER)
|
|
|
|
CHECK_PROPERTY(flicker_filter_2d, FLICKER_FILTER_2D)
|
|
|
|
CHECK_PROPERTY(flicker_filter_adaptive, FLICKER_FILTER_ADAPTIVE)
|
|
|
|
CHECK_PROPERTY(tv_chroma_filter, TV_CHROMA_FILTER)
|
|
|
|
CHECK_PROPERTY(tv_luma_filter, TV_LUMA_FILTER)
|
2010-08-04 06:50:29 -06:00
|
|
|
CHECK_PROPERTY(dot_crawl, DOT_CRAWL)
|
2010-08-04 06:50:28 -06:00
|
|
|
}
|
2009-09-10 01:45:46 -06:00
|
|
|
|
2010-08-04 06:50:28 -06:00
|
|
|
return -EINVAL; /* unknown property */
|
2009-09-10 01:45:46 -06:00
|
|
|
|
2010-08-04 06:50:28 -06:00
|
|
|
set_value:
|
|
|
|
if (!intel_sdvo_set_value(intel_sdvo, cmd, &temp_value, 2))
|
|
|
|
return -EIO;
|
2009-09-10 01:45:46 -06:00
|
|
|
|
|
|
|
|
2010-08-04 06:50:28 -06:00
|
|
|
done:
|
2012-12-19 09:08:43 -07:00
|
|
|
if (intel_sdvo->base.base.crtc)
|
|
|
|
intel_crtc_restore_mode(intel_sdvo->base.base.crtc);
|
2010-08-04 06:50:28 -06:00
|
|
|
|
2010-08-04 06:50:25 -06:00
|
|
|
return 0;
|
2010-08-04 06:50:28 -06:00
|
|
|
#undef CHECK_PROPERTY
|
2009-08-23 23:50:26 -06: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-07 15:24:08 -07:00
|
|
|
static const struct drm_connector_funcs intel_sdvo_connector_funcs = {
|
drm/i915: convert dpms functions of dvo/sdvo/crt
Yeah, big patch but I couldn't come up with a neat idea of how to
split it up further, that wouldn't break dpms on cloned configs
somehow. But the changes in dvo/sdvo/crt are all pretty much
orthonogal, so it's not too bad a patch.
These are the only encoders that support cloning, which requires a few
special changes compared to the previous patches.
- Compute the desired state of the display pipe by walking all
connected encoders and checking whether any has active connectors.
To make this clearer, drop the old mode parameter to the crtc dpms
function and rename it to intel_crtc_update_dpms.
- There's the curious case of intel_crtc->dpms_mode. With the previous
patches to remove the overlay pipe A code and to rework the load
detect pipe code, the big users are gone. We still keep it to avoid
enabling the pipe twice, but we duplicate this logic with
crtc->active, too. Still, leave this for now and just push a fake
dpms mode into it that reflects the state of the display pipe.
Changes in the encoder dpms functions:
- We clamp the dpms state to the supported range right away. This is
escpecially important for the VGA outputs, where only older hw
supports the intermediate states. This (and the crt->adpa_reg patch)
allows us to unify the crt dpms code again between all variants
(gmch, vlv and pch).
- We only enable/disable the output for dvo/sdvo and leave the encoder
running. The encoder will be disabled/enabled when we switch the
state of the entire output pipeline (which will happen right away
for non-cloned setups). This way the duplication is reduced and
strange interaction when disabling output ports at the wrong time
avoided.
The dpms code for all three types of connectors contains a bit of
duplicated logic, but I think keeping these special cases separate is
simpler: CRT is the only one that hanldes intermediate dpms state
(which requires extra logic to enable/disable things in the right
order), and introducing some abstraction just to share the code
between dvo and sdvo smells like overkill. We can do that once someone
bothers to implement cloning for the more modern outputs. But I doubt
that this will ever happen.
v2: s/crtc/crt/_set_dpms, noticed by Paulo Zanoni.
Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-Off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
2012-07-01 14:42:24 -06:00
|
|
|
.dpms = intel_sdvo_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-07 15:24:08 -07:00
|
|
|
.detect = intel_sdvo_detect,
|
|
|
|
.fill_modes = drm_helper_probe_single_connector_modes,
|
2009-08-23 23:50:26 -06:00
|
|
|
.set_property = intel_sdvo_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-07 15:24:08 -07:00
|
|
|
.destroy = intel_sdvo_destroy,
|
|
|
|
};
|
|
|
|
|
|
|
|
static const struct drm_connector_helper_funcs intel_sdvo_connector_helper_funcs = {
|
|
|
|
.get_modes = intel_sdvo_get_modes,
|
|
|
|
.mode_valid = intel_sdvo_mode_valid,
|
2010-09-09 09:20:55 -06: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-07 15:24:08 -07:00
|
|
|
};
|
|
|
|
|
2008-12-18 13:18:47 -07:00
|
|
|
static void intel_sdvo_enc_destroy(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-07 15:24:08 -07:00
|
|
|
{
|
2010-09-14 09:46:59 -06:00
|
|
|
struct intel_sdvo *intel_sdvo = to_intel_sdvo(encoder);
|
2010-03-29 07:22:55 -06:00
|
|
|
|
2010-08-04 06:50:23 -06:00
|
|
|
if (intel_sdvo->sdvo_lvds_fixed_mode != NULL)
|
2010-03-29 07:22:55 -06:00
|
|
|
drm_mode_destroy(encoder->dev,
|
2010-08-04 06:50:23 -06:00
|
|
|
intel_sdvo->sdvo_lvds_fixed_mode);
|
2010-03-29 07:22:55 -06:00
|
|
|
|
2010-09-24 05:52:03 -06:00
|
|
|
i2c_del_adapter(&intel_sdvo->ddc);
|
2010-08-04 06:50:23 -06:00
|
|
|
intel_encoder_destroy(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-07 15:24:08 -07:00
|
|
|
}
|
|
|
|
|
|
|
|
static const struct drm_encoder_funcs intel_sdvo_enc_funcs = {
|
|
|
|
.destroy = intel_sdvo_enc_destroy,
|
|
|
|
};
|
|
|
|
|
2010-08-12 08:26:41 -06:00
|
|
|
static void
|
|
|
|
intel_sdvo_guess_ddc_bus(struct intel_sdvo *sdvo)
|
|
|
|
{
|
|
|
|
uint16_t mask = 0;
|
|
|
|
unsigned int num_bits;
|
|
|
|
|
|
|
|
/* Make a mask of outputs less than or equal to our own priority in the
|
|
|
|
* list.
|
|
|
|
*/
|
|
|
|
switch (sdvo->controlled_output) {
|
|
|
|
case SDVO_OUTPUT_LVDS1:
|
|
|
|
mask |= SDVO_OUTPUT_LVDS1;
|
|
|
|
case SDVO_OUTPUT_LVDS0:
|
|
|
|
mask |= SDVO_OUTPUT_LVDS0;
|
|
|
|
case SDVO_OUTPUT_TMDS1:
|
|
|
|
mask |= SDVO_OUTPUT_TMDS1;
|
|
|
|
case SDVO_OUTPUT_TMDS0:
|
|
|
|
mask |= SDVO_OUTPUT_TMDS0;
|
|
|
|
case SDVO_OUTPUT_RGB1:
|
|
|
|
mask |= SDVO_OUTPUT_RGB1;
|
|
|
|
case SDVO_OUTPUT_RGB0:
|
|
|
|
mask |= SDVO_OUTPUT_RGB0;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Count bits to find what number we are in the priority list. */
|
|
|
|
mask &= sdvo->caps.output_flags;
|
|
|
|
num_bits = hweight16(mask);
|
|
|
|
/* If more than 3 outputs, default to DDC bus 3 for now. */
|
|
|
|
if (num_bits > 3)
|
|
|
|
num_bits = 3;
|
|
|
|
|
|
|
|
/* Corresponds to SDVO_CONTROL_BUS_DDCx */
|
|
|
|
sdvo->ddc_bus = 1 << num_bits;
|
|
|
|
}
|
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-07 15:24:08 -07:00
|
|
|
|
2009-02-02 16:11:52 -07:00
|
|
|
/**
|
|
|
|
* Choose the appropriate DDC bus for control bus switch command for this
|
|
|
|
* SDVO output based on the controlled output.
|
|
|
|
*
|
|
|
|
* DDC bus number assignment is in a priority order of RGB outputs, then TMDS
|
|
|
|
* outputs, then LVDS outputs.
|
|
|
|
*/
|
|
|
|
static void
|
2010-04-23 14:07:40 -06:00
|
|
|
intel_sdvo_select_ddc_bus(struct drm_i915_private *dev_priv,
|
2010-08-04 06:50:23 -06:00
|
|
|
struct intel_sdvo *sdvo, u32 reg)
|
2009-02-02 16:11:52 -07:00
|
|
|
{
|
2010-04-23 14:07:40 -06:00
|
|
|
struct sdvo_device_mapping *mapping;
|
2009-02-02 16:11:52 -07:00
|
|
|
|
2012-03-23 16:43:35 -06:00
|
|
|
if (sdvo->is_sdvob)
|
2010-04-23 14:07:40 -06:00
|
|
|
mapping = &(dev_priv->sdvo_mappings[0]);
|
|
|
|
else
|
|
|
|
mapping = &(dev_priv->sdvo_mappings[1]);
|
2009-02-02 16:11:52 -07:00
|
|
|
|
2010-08-12 08:26:41 -06:00
|
|
|
if (mapping->initialized)
|
|
|
|
sdvo->ddc_bus = 1 << ((mapping->ddc_pin & 0xf0) >> 4);
|
|
|
|
else
|
|
|
|
intel_sdvo_guess_ddc_bus(sdvo);
|
2009-02-02 16:11:52 -07:00
|
|
|
}
|
|
|
|
|
2010-09-24 05:52:03 -06:00
|
|
|
static void
|
|
|
|
intel_sdvo_select_i2c_bus(struct drm_i915_private *dev_priv,
|
|
|
|
struct intel_sdvo *sdvo, u32 reg)
|
|
|
|
{
|
|
|
|
struct sdvo_device_mapping *mapping;
|
2011-06-16 14:36:23 -06:00
|
|
|
u8 pin;
|
2010-09-24 05:52:03 -06:00
|
|
|
|
2012-03-23 16:43:35 -06:00
|
|
|
if (sdvo->is_sdvob)
|
2010-09-24 05:52:03 -06:00
|
|
|
mapping = &dev_priv->sdvo_mappings[0];
|
|
|
|
else
|
|
|
|
mapping = &dev_priv->sdvo_mappings[1];
|
|
|
|
|
2012-10-22 07:12:17 -06:00
|
|
|
if (mapping->initialized && intel_gmbus_is_port_valid(mapping->i2c_pin))
|
2010-09-24 05:52:03 -06:00
|
|
|
pin = mapping->i2c_pin;
|
2012-10-22 07:12:17 -06:00
|
|
|
else
|
|
|
|
pin = GMBUS_PORT_DPB;
|
2010-09-24 05:52:03 -06:00
|
|
|
|
2012-10-22 07:12:17 -06:00
|
|
|
sdvo->i2c = intel_gmbus_get_adapter(dev_priv, pin);
|
|
|
|
|
|
|
|
/* With gmbus we should be able to drive sdvo i2c at 2MHz, but somehow
|
|
|
|
* our code totally fails once we start using gmbus. Hence fall back to
|
|
|
|
* bit banging for now. */
|
|
|
|
intel_gmbus_force_bit(sdvo->i2c, true);
|
2010-09-24 05:52:03 -06:00
|
|
|
}
|
|
|
|
|
2012-10-22 07:12:18 -06:00
|
|
|
/* undo any changes intel_sdvo_select_i2c_bus() did to sdvo->i2c */
|
|
|
|
static void
|
|
|
|
intel_sdvo_unselect_i2c_bus(struct intel_sdvo *sdvo)
|
|
|
|
{
|
|
|
|
intel_gmbus_force_bit(sdvo->i2c, false);
|
2010-09-24 05:52:03 -06:00
|
|
|
}
|
|
|
|
|
2009-02-02 16:11:52 -07:00
|
|
|
static bool
|
2010-10-22 02:15:22 -06:00
|
|
|
intel_sdvo_is_hdmi_connector(struct intel_sdvo *intel_sdvo, int device)
|
2009-02-02 16:11:52 -07:00
|
|
|
{
|
2011-01-04 13:10:52 -07:00
|
|
|
return intel_sdvo_check_supp_encode(intel_sdvo);
|
2009-02-02 16:11:52 -07:00
|
|
|
}
|
|
|
|
|
2009-05-31 03:18:07 -06:00
|
|
|
static u8
|
2012-03-23 16:43:35 -06:00
|
|
|
intel_sdvo_get_slave_addr(struct drm_device *dev, struct intel_sdvo *sdvo)
|
2009-05-31 03:18:07 -06:00
|
|
|
{
|
|
|
|
struct drm_i915_private *dev_priv = dev->dev_private;
|
|
|
|
struct sdvo_device_mapping *my_mapping, *other_mapping;
|
|
|
|
|
2012-03-23 16:43:35 -06:00
|
|
|
if (sdvo->is_sdvob) {
|
2009-05-31 03:18:07 -06:00
|
|
|
my_mapping = &dev_priv->sdvo_mappings[0];
|
|
|
|
other_mapping = &dev_priv->sdvo_mappings[1];
|
|
|
|
} else {
|
|
|
|
my_mapping = &dev_priv->sdvo_mappings[1];
|
|
|
|
other_mapping = &dev_priv->sdvo_mappings[0];
|
|
|
|
}
|
|
|
|
|
|
|
|
/* If the BIOS described our SDVO device, take advantage of it. */
|
|
|
|
if (my_mapping->slave_addr)
|
|
|
|
return my_mapping->slave_addr;
|
|
|
|
|
|
|
|
/* If the BIOS only described a different SDVO device, use the
|
|
|
|
* address that it isn't using.
|
|
|
|
*/
|
|
|
|
if (other_mapping->slave_addr) {
|
|
|
|
if (other_mapping->slave_addr == 0x70)
|
|
|
|
return 0x72;
|
|
|
|
else
|
|
|
|
return 0x70;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* No SDVO device info is found for another DVO port,
|
|
|
|
* so use mapping assumption we had before BIOS parsing.
|
|
|
|
*/
|
2012-03-23 16:43:35 -06:00
|
|
|
if (sdvo->is_sdvob)
|
2009-05-31 03:18:07 -06:00
|
|
|
return 0x70;
|
|
|
|
else
|
|
|
|
return 0x72;
|
|
|
|
}
|
|
|
|
|
2010-03-30 00:06:33 -06:00
|
|
|
static void
|
2010-09-09 09:20:55 -06:00
|
|
|
intel_sdvo_connector_init(struct intel_sdvo_connector *connector,
|
|
|
|
struct intel_sdvo *encoder)
|
2010-03-30 00:06:33 -06:00
|
|
|
{
|
2010-09-09 09:20:55 -06:00
|
|
|
drm_connector_init(encoder->base.base.dev,
|
|
|
|
&connector->base.base,
|
|
|
|
&intel_sdvo_connector_funcs,
|
|
|
|
connector->base.base.connector_type);
|
2010-02-08 06:35:12 -07:00
|
|
|
|
2010-09-09 09:20:55 -06:00
|
|
|
drm_connector_helper_add(&connector->base.base,
|
|
|
|
&intel_sdvo_connector_helper_funcs);
|
2010-03-30 00:06:33 -06:00
|
|
|
|
2012-01-28 06:49:25 -07:00
|
|
|
connector->base.base.interlace_allowed = 1;
|
2010-09-09 09:20:55 -06:00
|
|
|
connector->base.base.doublescan_allowed = 0;
|
|
|
|
connector->base.base.display_info.subpixel_order = SubPixelHorizontalRGB;
|
2012-07-02 06:54:00 -06:00
|
|
|
connector->base.get_hw_state = intel_sdvo_connector_get_hw_state;
|
2010-03-30 00:06:33 -06:00
|
|
|
|
2010-09-09 09:20:55 -06:00
|
|
|
intel_connector_attach_encoder(&connector->base, &encoder->base);
|
|
|
|
drm_sysfs_connector_add(&connector->base.base);
|
2010-03-30 00:06:33 -06:00
|
|
|
}
|
2010-02-08 06:35:12 -07:00
|
|
|
|
2010-09-19 02:29:33 -06:00
|
|
|
static void
|
2013-01-17 07:31:29 -07:00
|
|
|
intel_sdvo_add_hdmi_properties(struct intel_sdvo *intel_sdvo,
|
|
|
|
struct intel_sdvo_connector *connector)
|
2010-09-19 02:29:33 -06:00
|
|
|
{
|
|
|
|
struct drm_device *dev = connector->base.base.dev;
|
|
|
|
|
2011-05-12 15:17:24 -06:00
|
|
|
intel_attach_force_audio_property(&connector->base.base);
|
2013-01-17 07:31:29 -07:00
|
|
|
if (INTEL_INFO(dev)->gen >= 4 && IS_MOBILE(dev)) {
|
2011-02-21 15:23:52 -07:00
|
|
|
intel_attach_broadcast_rgb_property(&connector->base.base);
|
2013-01-17 07:31:29 -07:00
|
|
|
intel_sdvo->color_range_auto = true;
|
|
|
|
}
|
2010-09-19 02:29:33 -06:00
|
|
|
}
|
|
|
|
|
2009-07-23 03:11:34 -06:00
|
|
|
static bool
|
2010-08-04 06:50:23 -06:00
|
|
|
intel_sdvo_dvi_init(struct intel_sdvo *intel_sdvo, int device)
|
2009-07-23 03:11:34 -06:00
|
|
|
{
|
2010-09-09 08:14:28 -06:00
|
|
|
struct drm_encoder *encoder = &intel_sdvo->base.base;
|
2010-03-30 00:06:33 -06:00
|
|
|
struct drm_connector *connector;
|
2011-09-21 10:13:30 -06:00
|
|
|
struct intel_encoder *intel_encoder = to_intel_encoder(encoder);
|
2010-03-30 00:06:33 -06:00
|
|
|
struct intel_connector *intel_connector;
|
2010-08-04 06:50:24 -06:00
|
|
|
struct intel_sdvo_connector *intel_sdvo_connector;
|
2010-03-30 00:06:33 -06:00
|
|
|
|
2010-08-04 06:50:24 -06:00
|
|
|
intel_sdvo_connector = kzalloc(sizeof(struct intel_sdvo_connector), GFP_KERNEL);
|
|
|
|
if (!intel_sdvo_connector)
|
2010-03-30 00:06:33 -06:00
|
|
|
return false;
|
|
|
|
|
|
|
|
if (device == 0) {
|
2010-08-04 06:50:23 -06:00
|
|
|
intel_sdvo->controlled_output |= SDVO_OUTPUT_TMDS0;
|
2010-08-04 06:50:24 -06:00
|
|
|
intel_sdvo_connector->output_flag = SDVO_OUTPUT_TMDS0;
|
2010-03-30 00:06:33 -06:00
|
|
|
} else if (device == 1) {
|
2010-08-04 06:50:23 -06:00
|
|
|
intel_sdvo->controlled_output |= SDVO_OUTPUT_TMDS1;
|
2010-08-04 06:50:24 -06:00
|
|
|
intel_sdvo_connector->output_flag = SDVO_OUTPUT_TMDS1;
|
2010-03-30 00:06:33 -06:00
|
|
|
}
|
|
|
|
|
2010-08-04 06:50:24 -06:00
|
|
|
intel_connector = &intel_sdvo_connector->base;
|
2010-03-30 00:06:33 -06:00
|
|
|
connector = &intel_connector->base;
|
2012-08-29 07:43:58 -06:00
|
|
|
if (intel_sdvo_get_hotplug_support(intel_sdvo) &
|
|
|
|
intel_sdvo_connector->output_flag) {
|
|
|
|
intel_sdvo->hotplug_active |= intel_sdvo_connector->output_flag;
|
2011-09-21 10:13:30 -06:00
|
|
|
/* Some SDVO devices have one-shot hotplug interrupts.
|
|
|
|
* Ensure that they get re-enabled when an interrupt happens.
|
|
|
|
*/
|
|
|
|
intel_encoder->hot_plug = intel_sdvo_enable_hotplug;
|
|
|
|
intel_sdvo_enable_hotplug(intel_encoder);
|
2012-08-29 07:43:58 -06:00
|
|
|
} else {
|
2013-04-16 05:36:55 -06:00
|
|
|
intel_connector->polled = DRM_CONNECTOR_POLL_CONNECT | DRM_CONNECTOR_POLL_DISCONNECT;
|
2012-08-29 07:43:58 -06:00
|
|
|
}
|
2010-03-30 00:06:33 -06:00
|
|
|
encoder->encoder_type = DRM_MODE_ENCODER_TMDS;
|
|
|
|
connector->connector_type = DRM_MODE_CONNECTOR_DVID;
|
|
|
|
|
2010-10-22 02:15:22 -06:00
|
|
|
if (intel_sdvo_is_hdmi_connector(intel_sdvo, device)) {
|
2010-03-30 00:06:33 -06:00
|
|
|
connector->connector_type = DRM_MODE_CONNECTOR_HDMIA;
|
2010-10-22 02:15:22 -06:00
|
|
|
intel_sdvo->is_hdmi = true;
|
2010-03-30 00:06:33 -06:00
|
|
|
}
|
|
|
|
|
2010-09-09 09:20:55 -06:00
|
|
|
intel_sdvo_connector_init(intel_sdvo_connector, intel_sdvo);
|
2010-12-23 02:43:48 -07:00
|
|
|
if (intel_sdvo->is_hdmi)
|
2013-01-17 07:31:29 -07:00
|
|
|
intel_sdvo_add_hdmi_properties(intel_sdvo, intel_sdvo_connector);
|
2010-03-30 00:06:33 -06:00
|
|
|
|
|
|
|
return true;
|
|
|
|
}
|
|
|
|
|
|
|
|
static bool
|
2010-08-04 06:50:23 -06:00
|
|
|
intel_sdvo_tv_init(struct intel_sdvo *intel_sdvo, int type)
|
2010-03-30 00:06:33 -06:00
|
|
|
{
|
2010-09-09 08:14:28 -06:00
|
|
|
struct drm_encoder *encoder = &intel_sdvo->base.base;
|
|
|
|
struct drm_connector *connector;
|
|
|
|
struct intel_connector *intel_connector;
|
|
|
|
struct intel_sdvo_connector *intel_sdvo_connector;
|
2010-03-30 00:06:33 -06:00
|
|
|
|
2010-08-04 06:50:24 -06:00
|
|
|
intel_sdvo_connector = kzalloc(sizeof(struct intel_sdvo_connector), GFP_KERNEL);
|
|
|
|
if (!intel_sdvo_connector)
|
|
|
|
return false;
|
2010-03-30 00:06:33 -06:00
|
|
|
|
2010-08-04 06:50:24 -06:00
|
|
|
intel_connector = &intel_sdvo_connector->base;
|
2010-09-09 08:14:28 -06:00
|
|
|
connector = &intel_connector->base;
|
|
|
|
encoder->encoder_type = DRM_MODE_ENCODER_TVDAC;
|
|
|
|
connector->connector_type = DRM_MODE_CONNECTOR_SVIDEO;
|
2010-03-30 00:06:33 -06:00
|
|
|
|
2010-09-09 08:14:28 -06:00
|
|
|
intel_sdvo->controlled_output |= type;
|
|
|
|
intel_sdvo_connector->output_flag = type;
|
2010-03-30 00:06:33 -06:00
|
|
|
|
2010-09-09 08:14:28 -06:00
|
|
|
intel_sdvo->is_tv = true;
|
2010-03-30 00:06:33 -06:00
|
|
|
|
2010-09-09 09:20:55 -06:00
|
|
|
intel_sdvo_connector_init(intel_sdvo_connector, intel_sdvo);
|
2010-03-30 00:06:33 -06:00
|
|
|
|
2010-09-09 08:14:28 -06:00
|
|
|
if (!intel_sdvo_tv_create_property(intel_sdvo, intel_sdvo_connector, type))
|
2010-08-04 06:50:25 -06:00
|
|
|
goto err;
|
2010-03-30 00:06:33 -06:00
|
|
|
|
2010-09-09 08:14:28 -06:00
|
|
|
if (!intel_sdvo_create_enhance_property(intel_sdvo, intel_sdvo_connector))
|
2010-08-04 06:50:25 -06:00
|
|
|
goto err;
|
2010-03-30 00:06:33 -06:00
|
|
|
|
2010-09-09 08:14:28 -06:00
|
|
|
return true;
|
2010-08-04 06:50:25 -06:00
|
|
|
|
|
|
|
err:
|
2010-09-23 09:15:21 -06:00
|
|
|
intel_sdvo_destroy(connector);
|
2010-08-04 06:50:25 -06:00
|
|
|
return false;
|
2010-03-30 00:06:33 -06:00
|
|
|
}
|
|
|
|
|
|
|
|
static bool
|
2010-08-04 06:50:23 -06:00
|
|
|
intel_sdvo_analog_init(struct intel_sdvo *intel_sdvo, int device)
|
2010-03-30 00:06:33 -06:00
|
|
|
{
|
2010-09-09 08:14:28 -06:00
|
|
|
struct drm_encoder *encoder = &intel_sdvo->base.base;
|
|
|
|
struct drm_connector *connector;
|
|
|
|
struct intel_connector *intel_connector;
|
|
|
|
struct intel_sdvo_connector *intel_sdvo_connector;
|
2010-03-30 00:06:33 -06:00
|
|
|
|
2010-08-04 06:50:24 -06:00
|
|
|
intel_sdvo_connector = kzalloc(sizeof(struct intel_sdvo_connector), GFP_KERNEL);
|
|
|
|
if (!intel_sdvo_connector)
|
|
|
|
return false;
|
2010-03-30 00:06:33 -06:00
|
|
|
|
2010-08-04 06:50:24 -06:00
|
|
|
intel_connector = &intel_sdvo_connector->base;
|
2010-09-09 08:14:28 -06:00
|
|
|
connector = &intel_connector->base;
|
2013-04-16 05:36:55 -06:00
|
|
|
intel_connector->polled = DRM_CONNECTOR_POLL_CONNECT;
|
2010-09-09 08:14:28 -06:00
|
|
|
encoder->encoder_type = DRM_MODE_ENCODER_DAC;
|
|
|
|
connector->connector_type = DRM_MODE_CONNECTOR_VGA;
|
|
|
|
|
|
|
|
if (device == 0) {
|
|
|
|
intel_sdvo->controlled_output |= SDVO_OUTPUT_RGB0;
|
|
|
|
intel_sdvo_connector->output_flag = SDVO_OUTPUT_RGB0;
|
|
|
|
} else if (device == 1) {
|
|
|
|
intel_sdvo->controlled_output |= SDVO_OUTPUT_RGB1;
|
|
|
|
intel_sdvo_connector->output_flag = SDVO_OUTPUT_RGB1;
|
|
|
|
}
|
|
|
|
|
2010-09-09 09:20:55 -06:00
|
|
|
intel_sdvo_connector_init(intel_sdvo_connector,
|
|
|
|
intel_sdvo);
|
2010-09-09 08:14:28 -06:00
|
|
|
return true;
|
2010-03-30 00:06:33 -06:00
|
|
|
}
|
|
|
|
|
|
|
|
static bool
|
2010-08-04 06:50:23 -06:00
|
|
|
intel_sdvo_lvds_init(struct intel_sdvo *intel_sdvo, int device)
|
2010-03-30 00:06:33 -06:00
|
|
|
{
|
2010-09-09 08:14:28 -06:00
|
|
|
struct drm_encoder *encoder = &intel_sdvo->base.base;
|
|
|
|
struct drm_connector *connector;
|
|
|
|
struct intel_connector *intel_connector;
|
|
|
|
struct intel_sdvo_connector *intel_sdvo_connector;
|
2010-03-30 00:06:33 -06:00
|
|
|
|
2010-08-04 06:50:24 -06:00
|
|
|
intel_sdvo_connector = kzalloc(sizeof(struct intel_sdvo_connector), GFP_KERNEL);
|
|
|
|
if (!intel_sdvo_connector)
|
|
|
|
return false;
|
2010-03-30 00:06:33 -06:00
|
|
|
|
2010-08-04 06:50:24 -06:00
|
|
|
intel_connector = &intel_sdvo_connector->base;
|
|
|
|
connector = &intel_connector->base;
|
2010-09-09 08:14:28 -06:00
|
|
|
encoder->encoder_type = DRM_MODE_ENCODER_LVDS;
|
|
|
|
connector->connector_type = DRM_MODE_CONNECTOR_LVDS;
|
|
|
|
|
|
|
|
if (device == 0) {
|
|
|
|
intel_sdvo->controlled_output |= SDVO_OUTPUT_LVDS0;
|
|
|
|
intel_sdvo_connector->output_flag = SDVO_OUTPUT_LVDS0;
|
|
|
|
} else if (device == 1) {
|
|
|
|
intel_sdvo->controlled_output |= SDVO_OUTPUT_LVDS1;
|
|
|
|
intel_sdvo_connector->output_flag = SDVO_OUTPUT_LVDS1;
|
|
|
|
}
|
|
|
|
|
2010-09-09 09:20:55 -06:00
|
|
|
intel_sdvo_connector_init(intel_sdvo_connector, intel_sdvo);
|
2010-09-09 08:14:28 -06:00
|
|
|
if (!intel_sdvo_create_enhance_property(intel_sdvo, intel_sdvo_connector))
|
2010-08-04 06:50:25 -06:00
|
|
|
goto err;
|
|
|
|
|
|
|
|
return true;
|
|
|
|
|
|
|
|
err:
|
2010-09-23 09:15:21 -06:00
|
|
|
intel_sdvo_destroy(connector);
|
2010-08-04 06:50:25 -06:00
|
|
|
return false;
|
2010-03-30 00:06:33 -06:00
|
|
|
}
|
|
|
|
|
|
|
|
static bool
|
2010-08-04 06:50:23 -06:00
|
|
|
intel_sdvo_output_setup(struct intel_sdvo *intel_sdvo, uint16_t flags)
|
2010-03-30 00:06:33 -06:00
|
|
|
{
|
2010-08-04 06:50:23 -06:00
|
|
|
intel_sdvo->is_tv = false;
|
|
|
|
intel_sdvo->is_lvds = false;
|
2009-07-23 03:11:34 -06:00
|
|
|
|
2010-03-30 00:06:33 -06:00
|
|
|
/* SDVO requires XXX1 function may not exist unless it has XXX0 function.*/
|
2009-07-23 03:11:34 -06:00
|
|
|
|
2010-03-30 00:06:33 -06:00
|
|
|
if (flags & SDVO_OUTPUT_TMDS0)
|
2010-08-04 06:50:23 -06:00
|
|
|
if (!intel_sdvo_dvi_init(intel_sdvo, 0))
|
2010-03-30 00:06:33 -06:00
|
|
|
return false;
|
|
|
|
|
|
|
|
if ((flags & SDVO_TMDS_MASK) == SDVO_TMDS_MASK)
|
2010-08-04 06:50:23 -06:00
|
|
|
if (!intel_sdvo_dvi_init(intel_sdvo, 1))
|
2010-03-30 00:06:33 -06:00
|
|
|
return false;
|
|
|
|
|
|
|
|
/* TV has no XXX1 function block */
|
2010-03-29 09:16:13 -06:00
|
|
|
if (flags & SDVO_OUTPUT_SVID0)
|
2010-08-04 06:50:23 -06:00
|
|
|
if (!intel_sdvo_tv_init(intel_sdvo, SDVO_OUTPUT_SVID0))
|
2010-03-30 00:06:33 -06:00
|
|
|
return false;
|
|
|
|
|
|
|
|
if (flags & SDVO_OUTPUT_CVBS0)
|
2010-08-04 06:50:23 -06:00
|
|
|
if (!intel_sdvo_tv_init(intel_sdvo, SDVO_OUTPUT_CVBS0))
|
2010-03-30 00:06:33 -06:00
|
|
|
return false;
|
2009-07-23 03:11:34 -06:00
|
|
|
|
2011-09-30 15:56:41 -06:00
|
|
|
if (flags & SDVO_OUTPUT_YPRPB0)
|
|
|
|
if (!intel_sdvo_tv_init(intel_sdvo, SDVO_OUTPUT_YPRPB0))
|
|
|
|
return false;
|
|
|
|
|
2010-03-30 00:06:33 -06:00
|
|
|
if (flags & SDVO_OUTPUT_RGB0)
|
2010-08-04 06:50:23 -06:00
|
|
|
if (!intel_sdvo_analog_init(intel_sdvo, 0))
|
2010-03-30 00:06:33 -06:00
|
|
|
return false;
|
|
|
|
|
|
|
|
if ((flags & SDVO_RGB_MASK) == SDVO_RGB_MASK)
|
2010-08-04 06:50:23 -06:00
|
|
|
if (!intel_sdvo_analog_init(intel_sdvo, 1))
|
2010-03-30 00:06:33 -06:00
|
|
|
return false;
|
|
|
|
|
|
|
|
if (flags & SDVO_OUTPUT_LVDS0)
|
2010-08-04 06:50:23 -06:00
|
|
|
if (!intel_sdvo_lvds_init(intel_sdvo, 0))
|
2010-03-30 00:06:33 -06:00
|
|
|
return false;
|
|
|
|
|
|
|
|
if ((flags & SDVO_LVDS_MASK) == SDVO_LVDS_MASK)
|
2010-08-04 06:50:23 -06:00
|
|
|
if (!intel_sdvo_lvds_init(intel_sdvo, 1))
|
2010-03-30 00:06:33 -06:00
|
|
|
return false;
|
2009-07-23 03:11:34 -06:00
|
|
|
|
2010-03-30 00:06:33 -06:00
|
|
|
if ((flags & SDVO_OUTPUT_MASK) == 0) {
|
2009-07-23 03:11:34 -06:00
|
|
|
unsigned char bytes[2];
|
|
|
|
|
2010-08-04 06:50:23 -06:00
|
|
|
intel_sdvo->controlled_output = 0;
|
|
|
|
memcpy(bytes, &intel_sdvo->caps.output_flags, 2);
|
2009-08-19 21:38:04 -06:00
|
|
|
DRM_DEBUG_KMS("%s: Unknown SDVO output type (0x%02x%02x)\n",
|
2010-08-04 06:50:23 -06:00
|
|
|
SDVO_NAME(intel_sdvo),
|
2009-08-19 21:38:04 -06:00
|
|
|
bytes[0], bytes[1]);
|
2010-03-30 00:06:33 -06:00
|
|
|
return false;
|
2009-07-23 03:11:34 -06:00
|
|
|
}
|
2011-09-02 13:54:37 -06:00
|
|
|
intel_sdvo->base.crtc_mask = (1 << 0) | (1 << 1) | (1 << 2);
|
2009-07-23 03:11:34 -06:00
|
|
|
|
2010-03-30 00:06:33 -06:00
|
|
|
return true;
|
2009-07-23 03:11:34 -06:00
|
|
|
}
|
|
|
|
|
2012-11-12 09:31:35 -07:00
|
|
|
static void intel_sdvo_output_cleanup(struct intel_sdvo *intel_sdvo)
|
|
|
|
{
|
|
|
|
struct drm_device *dev = intel_sdvo->base.base.dev;
|
|
|
|
struct drm_connector *connector, *tmp;
|
|
|
|
|
|
|
|
list_for_each_entry_safe(connector, tmp,
|
|
|
|
&dev->mode_config.connector_list, head) {
|
|
|
|
if (intel_attached_encoder(connector) == &intel_sdvo->base)
|
|
|
|
intel_sdvo_destroy(connector);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2010-08-04 06:50:25 -06:00
|
|
|
static bool intel_sdvo_tv_create_property(struct intel_sdvo *intel_sdvo,
|
|
|
|
struct intel_sdvo_connector *intel_sdvo_connector,
|
|
|
|
int type)
|
2009-08-23 23:50:26 -06:00
|
|
|
{
|
2010-09-09 08:14:28 -06:00
|
|
|
struct drm_device *dev = intel_sdvo->base.base.dev;
|
2009-08-23 23:50:26 -06:00
|
|
|
struct intel_sdvo_tv_format format;
|
|
|
|
uint32_t format_map, i;
|
|
|
|
|
2010-08-04 06:50:25 -06:00
|
|
|
if (!intel_sdvo_set_target_output(intel_sdvo, type))
|
|
|
|
return false;
|
2009-08-23 23:50:26 -06:00
|
|
|
|
2011-01-25 06:59:37 -07:00
|
|
|
BUILD_BUG_ON(sizeof(format) != 6);
|
2010-08-04 06:50:25 -06:00
|
|
|
if (!intel_sdvo_get_value(intel_sdvo,
|
|
|
|
SDVO_CMD_GET_SUPPORTED_TV_FORMATS,
|
|
|
|
&format, sizeof(format)))
|
|
|
|
return false;
|
2009-08-23 23:50:26 -06:00
|
|
|
|
2010-08-04 06:50:25 -06:00
|
|
|
memcpy(&format_map, &format, min(sizeof(format_map), sizeof(format)));
|
2009-08-23 23:50:26 -06:00
|
|
|
|
|
|
|
if (format_map == 0)
|
2010-08-04 06:50:25 -06:00
|
|
|
return false;
|
2009-08-23 23:50:26 -06:00
|
|
|
|
2010-08-04 06:50:24 -06:00
|
|
|
intel_sdvo_connector->format_supported_num = 0;
|
2009-08-23 23:50:26 -06:00
|
|
|
for (i = 0 ; i < TV_FORMAT_NUM; i++)
|
2010-08-04 06:50:26 -06:00
|
|
|
if (format_map & (1 << i))
|
|
|
|
intel_sdvo_connector->tv_format_supported[intel_sdvo_connector->format_supported_num++] = i;
|
2009-08-23 23:50:26 -06:00
|
|
|
|
|
|
|
|
2010-08-04 06:50:28 -06:00
|
|
|
intel_sdvo_connector->tv_format =
|
2010-08-04 06:50:25 -06:00
|
|
|
drm_property_create(dev, DRM_MODE_PROP_ENUM,
|
|
|
|
"mode", intel_sdvo_connector->format_supported_num);
|
2010-08-04 06:50:28 -06:00
|
|
|
if (!intel_sdvo_connector->tv_format)
|
2010-08-04 06:50:27 -06:00
|
|
|
return false;
|
2009-08-23 23:50:26 -06:00
|
|
|
|
2010-08-04 06:50:24 -06:00
|
|
|
for (i = 0; i < intel_sdvo_connector->format_supported_num; i++)
|
2009-08-23 23:50:26 -06:00
|
|
|
drm_property_add_enum(
|
2010-08-04 06:50:28 -06:00
|
|
|
intel_sdvo_connector->tv_format, i,
|
2010-08-04 06:50:26 -06:00
|
|
|
i, tv_format_names[intel_sdvo_connector->tv_format_supported[i]]);
|
2009-08-23 23:50:26 -06:00
|
|
|
|
2010-08-04 06:50:26 -06:00
|
|
|
intel_sdvo->tv_format_index = intel_sdvo_connector->tv_format_supported[0];
|
2012-10-11 19:36:04 -06:00
|
|
|
drm_object_attach_property(&intel_sdvo_connector->base.base.base,
|
2010-08-04 06:50:28 -06:00
|
|
|
intel_sdvo_connector->tv_format, 0);
|
2010-08-04 06:50:25 -06:00
|
|
|
return true;
|
2009-08-23 23:50:26 -06:00
|
|
|
|
|
|
|
}
|
|
|
|
|
2010-08-04 06:50:28 -06:00
|
|
|
#define ENHANCEMENT(name, NAME) do { \
|
|
|
|
if (enhancements.name) { \
|
|
|
|
if (!intel_sdvo_get_value(intel_sdvo, SDVO_CMD_GET_MAX_##NAME, &data_value, 4) || \
|
|
|
|
!intel_sdvo_get_value(intel_sdvo, SDVO_CMD_GET_##NAME, &response, 2)) \
|
|
|
|
return false; \
|
|
|
|
intel_sdvo_connector->max_##name = data_value[0]; \
|
|
|
|
intel_sdvo_connector->cur_##name = response; \
|
|
|
|
intel_sdvo_connector->name = \
|
2012-02-06 02:58:18 -07:00
|
|
|
drm_property_create_range(dev, 0, #name, 0, data_value[0]); \
|
2010-08-04 06:50:28 -06:00
|
|
|
if (!intel_sdvo_connector->name) return false; \
|
2012-10-11 19:36:04 -06:00
|
|
|
drm_object_attach_property(&connector->base, \
|
2010-08-04 06:50:28 -06:00
|
|
|
intel_sdvo_connector->name, \
|
|
|
|
intel_sdvo_connector->cur_##name); \
|
|
|
|
DRM_DEBUG_KMS(#name ": max %d, default %d, current %d\n", \
|
|
|
|
data_value[0], data_value[1], response); \
|
|
|
|
} \
|
2011-08-16 13:34:10 -06:00
|
|
|
} while (0)
|
2010-08-04 06:50:28 -06:00
|
|
|
|
|
|
|
static bool
|
|
|
|
intel_sdvo_create_enhance_property_tv(struct intel_sdvo *intel_sdvo,
|
|
|
|
struct intel_sdvo_connector *intel_sdvo_connector,
|
|
|
|
struct intel_sdvo_enhancements_reply enhancements)
|
2009-09-10 01:45:46 -06:00
|
|
|
{
|
2010-09-09 08:14:28 -06:00
|
|
|
struct drm_device *dev = intel_sdvo->base.base.dev;
|
2010-08-04 06:50:25 -06:00
|
|
|
struct drm_connector *connector = &intel_sdvo_connector->base.base;
|
2009-09-10 01:45:46 -06:00
|
|
|
uint16_t response, data_value[2];
|
|
|
|
|
2010-08-04 06:50:28 -06:00
|
|
|
/* when horizontal overscan is supported, Add the left/right property */
|
|
|
|
if (enhancements.overscan_h) {
|
|
|
|
if (!intel_sdvo_get_value(intel_sdvo,
|
|
|
|
SDVO_CMD_GET_MAX_OVERSCAN_H,
|
|
|
|
&data_value, 4))
|
|
|
|
return false;
|
2010-08-04 06:50:25 -06:00
|
|
|
|
2010-08-04 06:50:28 -06:00
|
|
|
if (!intel_sdvo_get_value(intel_sdvo,
|
|
|
|
SDVO_CMD_GET_OVERSCAN_H,
|
|
|
|
&response, 2))
|
|
|
|
return false;
|
2010-08-04 06:50:27 -06:00
|
|
|
|
2010-08-04 06:50:28 -06:00
|
|
|
intel_sdvo_connector->max_hscan = data_value[0];
|
|
|
|
intel_sdvo_connector->left_margin = data_value[0] - response;
|
|
|
|
intel_sdvo_connector->right_margin = intel_sdvo_connector->left_margin;
|
|
|
|
intel_sdvo_connector->left =
|
2012-02-06 02:58:18 -07:00
|
|
|
drm_property_create_range(dev, 0, "left_margin", 0, data_value[0]);
|
2010-08-04 06:50:28 -06:00
|
|
|
if (!intel_sdvo_connector->left)
|
|
|
|
return false;
|
2010-08-04 06:50:27 -06:00
|
|
|
|
2012-10-11 19:36:04 -06:00
|
|
|
drm_object_attach_property(&connector->base,
|
2010-08-04 06:50:28 -06:00
|
|
|
intel_sdvo_connector->left,
|
|
|
|
intel_sdvo_connector->left_margin);
|
2010-08-04 06:50:27 -06:00
|
|
|
|
2010-08-04 06:50:28 -06:00
|
|
|
intel_sdvo_connector->right =
|
2012-02-06 02:58:18 -07:00
|
|
|
drm_property_create_range(dev, 0, "right_margin", 0, data_value[0]);
|
2010-08-04 06:50:28 -06:00
|
|
|
if (!intel_sdvo_connector->right)
|
|
|
|
return false;
|
2010-08-04 06:50:25 -06:00
|
|
|
|
2012-10-11 19:36:04 -06:00
|
|
|
drm_object_attach_property(&connector->base,
|
2010-08-04 06:50:28 -06:00
|
|
|
intel_sdvo_connector->right,
|
|
|
|
intel_sdvo_connector->right_margin);
|
|
|
|
DRM_DEBUG_KMS("h_overscan: max %d, "
|
|
|
|
"default %d, current %d\n",
|
|
|
|
data_value[0], data_value[1], response);
|
|
|
|
}
|
2010-08-04 06:50:25 -06:00
|
|
|
|
2010-08-04 06:50:28 -06:00
|
|
|
if (enhancements.overscan_v) {
|
|
|
|
if (!intel_sdvo_get_value(intel_sdvo,
|
|
|
|
SDVO_CMD_GET_MAX_OVERSCAN_V,
|
|
|
|
&data_value, 4))
|
|
|
|
return false;
|
2010-08-04 06:50:27 -06:00
|
|
|
|
2010-08-04 06:50:28 -06:00
|
|
|
if (!intel_sdvo_get_value(intel_sdvo,
|
|
|
|
SDVO_CMD_GET_OVERSCAN_V,
|
|
|
|
&response, 2))
|
|
|
|
return false;
|
2010-08-04 06:50:25 -06:00
|
|
|
|
2010-08-04 06:50:28 -06:00
|
|
|
intel_sdvo_connector->max_vscan = data_value[0];
|
|
|
|
intel_sdvo_connector->top_margin = data_value[0] - response;
|
|
|
|
intel_sdvo_connector->bottom_margin = intel_sdvo_connector->top_margin;
|
|
|
|
intel_sdvo_connector->top =
|
2012-02-06 02:58:18 -07:00
|
|
|
drm_property_create_range(dev, 0,
|
|
|
|
"top_margin", 0, data_value[0]);
|
2010-08-04 06:50:28 -06:00
|
|
|
if (!intel_sdvo_connector->top)
|
|
|
|
return false;
|
2010-08-04 06:50:25 -06:00
|
|
|
|
2012-10-11 19:36:04 -06:00
|
|
|
drm_object_attach_property(&connector->base,
|
2010-08-04 06:50:28 -06:00
|
|
|
intel_sdvo_connector->top,
|
|
|
|
intel_sdvo_connector->top_margin);
|
2010-08-04 06:50:27 -06:00
|
|
|
|
2010-08-04 06:50:28 -06:00
|
|
|
intel_sdvo_connector->bottom =
|
2012-02-06 02:58:18 -07:00
|
|
|
drm_property_create_range(dev, 0,
|
|
|
|
"bottom_margin", 0, data_value[0]);
|
2010-08-04 06:50:28 -06:00
|
|
|
if (!intel_sdvo_connector->bottom)
|
|
|
|
return false;
|
2010-08-04 06:50:25 -06:00
|
|
|
|
2012-10-11 19:36:04 -06:00
|
|
|
drm_object_attach_property(&connector->base,
|
2010-08-04 06:50:28 -06:00
|
|
|
intel_sdvo_connector->bottom,
|
|
|
|
intel_sdvo_connector->bottom_margin);
|
|
|
|
DRM_DEBUG_KMS("v_overscan: max %d, "
|
|
|
|
"default %d, current %d\n",
|
|
|
|
data_value[0], data_value[1], response);
|
|
|
|
}
|
2010-08-04 06:50:25 -06:00
|
|
|
|
2010-08-04 06:50:28 -06:00
|
|
|
ENHANCEMENT(hpos, HPOS);
|
|
|
|
ENHANCEMENT(vpos, VPOS);
|
|
|
|
ENHANCEMENT(saturation, SATURATION);
|
|
|
|
ENHANCEMENT(contrast, CONTRAST);
|
|
|
|
ENHANCEMENT(hue, HUE);
|
|
|
|
ENHANCEMENT(sharpness, SHARPNESS);
|
|
|
|
ENHANCEMENT(brightness, BRIGHTNESS);
|
|
|
|
ENHANCEMENT(flicker_filter, FLICKER_FILTER);
|
|
|
|
ENHANCEMENT(flicker_filter_adaptive, FLICKER_FILTER_ADAPTIVE);
|
|
|
|
ENHANCEMENT(flicker_filter_2d, FLICKER_FILTER_2D);
|
|
|
|
ENHANCEMENT(tv_chroma_filter, TV_CHROMA_FILTER);
|
|
|
|
ENHANCEMENT(tv_luma_filter, TV_LUMA_FILTER);
|
2010-08-04 06:50:27 -06:00
|
|
|
|
2010-08-04 06:50:29 -06:00
|
|
|
if (enhancements.dot_crawl) {
|
|
|
|
if (!intel_sdvo_get_value(intel_sdvo, SDVO_CMD_GET_DOT_CRAWL, &response, 2))
|
|
|
|
return false;
|
|
|
|
|
|
|
|
intel_sdvo_connector->max_dot_crawl = 1;
|
|
|
|
intel_sdvo_connector->cur_dot_crawl = response & 0x1;
|
|
|
|
intel_sdvo_connector->dot_crawl =
|
2012-02-06 02:58:18 -07:00
|
|
|
drm_property_create_range(dev, 0, "dot_crawl", 0, 1);
|
2010-08-04 06:50:29 -06:00
|
|
|
if (!intel_sdvo_connector->dot_crawl)
|
|
|
|
return false;
|
|
|
|
|
2012-10-11 19:36:04 -06:00
|
|
|
drm_object_attach_property(&connector->base,
|
2010-08-04 06:50:29 -06:00
|
|
|
intel_sdvo_connector->dot_crawl,
|
|
|
|
intel_sdvo_connector->cur_dot_crawl);
|
|
|
|
DRM_DEBUG_KMS("dot crawl: current %d\n", response);
|
|
|
|
}
|
|
|
|
|
2010-08-04 06:50:28 -06:00
|
|
|
return true;
|
|
|
|
}
|
2010-08-04 06:50:25 -06:00
|
|
|
|
2010-08-04 06:50:28 -06:00
|
|
|
static bool
|
|
|
|
intel_sdvo_create_enhance_property_lvds(struct intel_sdvo *intel_sdvo,
|
|
|
|
struct intel_sdvo_connector *intel_sdvo_connector,
|
|
|
|
struct intel_sdvo_enhancements_reply enhancements)
|
|
|
|
{
|
2010-09-09 08:14:28 -06:00
|
|
|
struct drm_device *dev = intel_sdvo->base.base.dev;
|
2010-08-04 06:50:28 -06:00
|
|
|
struct drm_connector *connector = &intel_sdvo_connector->base.base;
|
|
|
|
uint16_t response, data_value[2];
|
2010-08-04 06:50:25 -06:00
|
|
|
|
2010-08-04 06:50:28 -06:00
|
|
|
ENHANCEMENT(brightness, BRIGHTNESS);
|
2010-08-04 06:50:27 -06:00
|
|
|
|
2010-08-04 06:50:28 -06:00
|
|
|
return true;
|
|
|
|
}
|
|
|
|
#undef ENHANCEMENT
|
2010-08-04 06:50:25 -06:00
|
|
|
|
2010-08-04 06:50:28 -06:00
|
|
|
static bool intel_sdvo_create_enhance_property(struct intel_sdvo *intel_sdvo,
|
|
|
|
struct intel_sdvo_connector *intel_sdvo_connector)
|
|
|
|
{
|
|
|
|
union {
|
|
|
|
struct intel_sdvo_enhancements_reply reply;
|
|
|
|
uint16_t response;
|
|
|
|
} enhancements;
|
2010-08-04 06:50:25 -06:00
|
|
|
|
2011-01-25 06:59:37 -07:00
|
|
|
BUILD_BUG_ON(sizeof(enhancements) != 2);
|
|
|
|
|
2010-09-23 09:17:33 -06:00
|
|
|
enhancements.response = 0;
|
|
|
|
intel_sdvo_get_value(intel_sdvo,
|
|
|
|
SDVO_CMD_GET_SUPPORTED_ENHANCEMENTS,
|
|
|
|
&enhancements, sizeof(enhancements));
|
2010-08-04 06:50:28 -06:00
|
|
|
if (enhancements.response == 0) {
|
|
|
|
DRM_DEBUG_KMS("No enhancement is supported\n");
|
|
|
|
return true;
|
2009-09-10 01:45:46 -06:00
|
|
|
}
|
2010-08-04 06:50:25 -06:00
|
|
|
|
2010-08-04 06:50:28 -06:00
|
|
|
if (IS_TV(intel_sdvo_connector))
|
|
|
|
return intel_sdvo_create_enhance_property_tv(intel_sdvo, intel_sdvo_connector, enhancements.reply);
|
2011-08-16 13:34:10 -06:00
|
|
|
else if (IS_LVDS(intel_sdvo_connector))
|
2010-08-04 06:50:28 -06:00
|
|
|
return intel_sdvo_create_enhance_property_lvds(intel_sdvo, intel_sdvo_connector, enhancements.reply);
|
|
|
|
else
|
|
|
|
return true;
|
2010-09-24 05:52:03 -06:00
|
|
|
}
|
|
|
|
|
|
|
|
static int intel_sdvo_ddc_proxy_xfer(struct i2c_adapter *adapter,
|
|
|
|
struct i2c_msg *msgs,
|
|
|
|
int num)
|
|
|
|
{
|
|
|
|
struct intel_sdvo *sdvo = adapter->algo_data;
|
2010-08-04 06:50:27 -06:00
|
|
|
|
2010-09-24 05:52:03 -06:00
|
|
|
if (!intel_sdvo_set_control_bus_switch(sdvo, sdvo->ddc_bus))
|
|
|
|
return -EIO;
|
|
|
|
|
|
|
|
return sdvo->i2c->algo->master_xfer(sdvo->i2c, msgs, num);
|
|
|
|
}
|
|
|
|
|
|
|
|
static u32 intel_sdvo_ddc_proxy_func(struct i2c_adapter *adapter)
|
|
|
|
{
|
|
|
|
struct intel_sdvo *sdvo = adapter->algo_data;
|
|
|
|
return sdvo->i2c->algo->functionality(sdvo->i2c);
|
|
|
|
}
|
|
|
|
|
|
|
|
static const struct i2c_algorithm intel_sdvo_ddc_proxy = {
|
|
|
|
.master_xfer = intel_sdvo_ddc_proxy_xfer,
|
|
|
|
.functionality = intel_sdvo_ddc_proxy_func
|
|
|
|
};
|
|
|
|
|
|
|
|
static bool
|
|
|
|
intel_sdvo_init_ddc_proxy(struct intel_sdvo *sdvo,
|
|
|
|
struct drm_device *dev)
|
|
|
|
{
|
|
|
|
sdvo->ddc.owner = THIS_MODULE;
|
|
|
|
sdvo->ddc.class = I2C_CLASS_DDC;
|
|
|
|
snprintf(sdvo->ddc.name, I2C_NAME_SIZE, "SDVO DDC proxy");
|
|
|
|
sdvo->ddc.dev.parent = &dev->pdev->dev;
|
|
|
|
sdvo->ddc.algo_data = sdvo;
|
|
|
|
sdvo->ddc.algo = &intel_sdvo_ddc_proxy;
|
|
|
|
|
|
|
|
return i2c_add_adapter(&sdvo->ddc) == 0;
|
2009-09-10 01:45:46 -06:00
|
|
|
}
|
|
|
|
|
2012-03-23 16:43:35 -06:00
|
|
|
bool intel_sdvo_init(struct drm_device *dev, uint32_t sdvo_reg, bool is_sdvob)
|
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-07 15:24:08 -07:00
|
|
|
{
|
2009-12-11 12:07:17 -07:00
|
|
|
struct drm_i915_private *dev_priv = dev->dev_private;
|
2010-03-25 12:11:14 -06:00
|
|
|
struct intel_encoder *intel_encoder;
|
2010-08-04 06:50:23 -06:00
|
|
|
struct intel_sdvo *intel_sdvo;
|
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-07 15:24:08 -07:00
|
|
|
int i;
|
2010-08-04 06:50:23 -06:00
|
|
|
intel_sdvo = kzalloc(sizeof(struct intel_sdvo), GFP_KERNEL);
|
|
|
|
if (!intel_sdvo)
|
2009-01-02 14:33:00 -07: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-07 15:24:08 -07:00
|
|
|
|
2011-05-17 07:03:50 -06:00
|
|
|
intel_sdvo->sdvo_reg = sdvo_reg;
|
2012-03-23 16:43:35 -06:00
|
|
|
intel_sdvo->is_sdvob = is_sdvob;
|
|
|
|
intel_sdvo->slave_addr = intel_sdvo_get_slave_addr(dev, intel_sdvo) >> 1;
|
2011-05-17 07:03:50 -06:00
|
|
|
intel_sdvo_select_i2c_bus(dev_priv, intel_sdvo, sdvo_reg);
|
2012-10-22 07:12:18 -06:00
|
|
|
if (!intel_sdvo_init_ddc_proxy(intel_sdvo, dev))
|
|
|
|
goto err_i2c_bus;
|
2010-09-24 05:52:03 -06:00
|
|
|
|
2011-05-17 07:03:50 -06:00
|
|
|
/* encoder type will be decided later */
|
2010-08-04 06:50:23 -06:00
|
|
|
intel_encoder = &intel_sdvo->base;
|
2010-03-25 12:11:14 -06:00
|
|
|
intel_encoder->type = INTEL_OUTPUT_SDVO;
|
2010-09-15 05:03:59 -06:00
|
|
|
drm_encoder_init(dev, &intel_encoder->base, &intel_sdvo_enc_funcs, 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-07 15:24:08 -07:00
|
|
|
|
|
|
|
/* Read the regs to test if we can talk to the device */
|
|
|
|
for (i = 0; i < 0x40; i++) {
|
2010-07-20 16:44:45 -06:00
|
|
|
u8 byte;
|
|
|
|
|
|
|
|
if (!intel_sdvo_read_byte(intel_sdvo, i, &byte)) {
|
2012-03-23 16:43:35 -06:00
|
|
|
DRM_DEBUG_KMS("No SDVO device found on %s\n",
|
|
|
|
SDVO_NAME(intel_sdvo));
|
2010-07-20 16:44:45 -06:00
|
|
|
goto err;
|
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-07 15:24:08 -07:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2013-03-26 17:44:53 -06:00
|
|
|
intel_encoder->compute_config = intel_sdvo_compute_config;
|
2012-07-01 07:31:04 -06:00
|
|
|
intel_encoder->disable = intel_disable_sdvo;
|
2013-03-26 17:44:53 -06:00
|
|
|
intel_encoder->mode_set = intel_sdvo_mode_set;
|
2012-07-01 07:31:04 -06:00
|
|
|
intel_encoder->enable = intel_enable_sdvo;
|
2012-07-02 06:54:00 -06:00
|
|
|
intel_encoder->get_hw_state = intel_sdvo_get_hw_state;
|
2013-05-14 18:08:26 -06:00
|
|
|
intel_encoder->get_config = intel_sdvo_get_config;
|
2012-07-01 07:31:04 -06:00
|
|
|
|
tree-wide: fix assorted typos all over the place
That is "success", "unknown", "through", "performance", "[re|un]mapping"
, "access", "default", "reasonable", "[con]currently", "temperature"
, "channel", "[un]used", "application", "example","hierarchy", "therefore"
, "[over|under]flow", "contiguous", "threshold", "enough" and others.
Signed-off-by: André Goddard Rosa <andre.goddard@gmail.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
2009-11-14 08:09:05 -07:00
|
|
|
/* In default case sdvo lvds is false */
|
2010-08-04 06:50:25 -06:00
|
|
|
if (!intel_sdvo_get_capabilities(intel_sdvo, &intel_sdvo->caps))
|
2010-07-20 16:44:45 -06:00
|
|
|
goto err;
|
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-07 15:24:08 -07:00
|
|
|
|
2010-08-04 06:50:23 -06:00
|
|
|
if (intel_sdvo_output_setup(intel_sdvo,
|
|
|
|
intel_sdvo->caps.output_flags) != true) {
|
2012-03-23 16:43:35 -06:00
|
|
|
DRM_DEBUG_KMS("SDVO output failed to setup on %s\n",
|
|
|
|
SDVO_NAME(intel_sdvo));
|
2012-11-12 09:31:35 -07:00
|
|
|
/* Output_setup can leave behind connectors! */
|
|
|
|
goto err_output;
|
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-07 15:24:08 -07:00
|
|
|
}
|
|
|
|
|
2013-06-09 09:02:04 -06:00
|
|
|
/* Only enable the hotplug irq if we need it, to work around noisy
|
|
|
|
* hotplug lines.
|
|
|
|
*/
|
|
|
|
if (intel_sdvo->hotplug_active) {
|
|
|
|
intel_encoder->hpd_pin =
|
|
|
|
intel_sdvo->is_sdvob ? HPD_SDVO_B : HPD_SDVO_C;
|
|
|
|
}
|
|
|
|
|
2012-11-13 09:24:43 -07:00
|
|
|
/*
|
|
|
|
* Cloning SDVO with anything is often impossible, since the SDVO
|
|
|
|
* encoder can request a special input timing mode. And even if that's
|
|
|
|
* not the case we have evidence that cloning a plain unscaled mode with
|
|
|
|
* VGA doesn't really work. Furthermore the cloning flags are way too
|
|
|
|
* simplistic anyway to express such constraints, so just give up on
|
|
|
|
* cloning for SDVO encoders.
|
|
|
|
*/
|
|
|
|
intel_sdvo->base.cloneable = false;
|
|
|
|
|
2010-08-04 06:50:23 -06:00
|
|
|
intel_sdvo_select_ddc_bus(dev_priv, intel_sdvo, sdvo_reg);
|
2009-02-02 16:11:52 -07:00
|
|
|
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-07 15:24:08 -07:00
|
|
|
/* Set the input timing to the screen. Assume always input 0. */
|
2010-08-04 06:50:25 -06:00
|
|
|
if (!intel_sdvo_set_target_input(intel_sdvo))
|
2012-11-12 09:31:35 -07:00
|
|
|
goto err_output;
|
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-07 15:24:08 -07:00
|
|
|
|
2010-08-04 06:50:25 -06:00
|
|
|
if (!intel_sdvo_get_input_pixel_clock_range(intel_sdvo,
|
|
|
|
&intel_sdvo->pixel_clock_min,
|
|
|
|
&intel_sdvo->pixel_clock_max))
|
2012-11-12 09:31:35 -07:00
|
|
|
goto err_output;
|
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-07 15:24:08 -07:00
|
|
|
|
2009-07-19 23:48:04 -06:00
|
|
|
DRM_DEBUG_KMS("%s device VID/DID: %02X:%02X.%02X, "
|
2009-06-02 00:12:00 -06:00
|
|
|
"clock range %dMHz - %dMHz, "
|
|
|
|
"input 1: %c, input 2: %c, "
|
|
|
|
"output 1: %c, output 2: %c\n",
|
2010-08-04 06:50:23 -06:00
|
|
|
SDVO_NAME(intel_sdvo),
|
|
|
|
intel_sdvo->caps.vendor_id, intel_sdvo->caps.device_id,
|
|
|
|
intel_sdvo->caps.device_rev_id,
|
|
|
|
intel_sdvo->pixel_clock_min / 1000,
|
|
|
|
intel_sdvo->pixel_clock_max / 1000,
|
|
|
|
(intel_sdvo->caps.sdvo_inputs_mask & 0x1) ? 'Y' : 'N',
|
|
|
|
(intel_sdvo->caps.sdvo_inputs_mask & 0x2) ? 'Y' : 'N',
|
2009-06-02 00:12:00 -06:00
|
|
|
/* check currently supported outputs */
|
2010-08-04 06:50:23 -06:00
|
|
|
intel_sdvo->caps.output_flags &
|
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-07 15:24:08 -07:00
|
|
|
(SDVO_OUTPUT_TMDS0 | SDVO_OUTPUT_RGB0) ? 'Y' : 'N',
|
2010-08-04 06:50:23 -06:00
|
|
|
intel_sdvo->caps.output_flags &
|
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-07 15:24:08 -07:00
|
|
|
(SDVO_OUTPUT_TMDS1 | SDVO_OUTPUT_RGB1) ? 'Y' : 'N');
|
2009-01-02 14:33:00 -07: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-07 15:24:08 -07:00
|
|
|
|
2012-11-12 09:31:35 -07:00
|
|
|
err_output:
|
|
|
|
intel_sdvo_output_cleanup(intel_sdvo);
|
|
|
|
|
2010-07-20 16:44:45 -06:00
|
|
|
err:
|
2010-09-15 05:03:59 -06:00
|
|
|
drm_encoder_cleanup(&intel_encoder->base);
|
2010-09-24 05:52:03 -06:00
|
|
|
i2c_del_adapter(&intel_sdvo->ddc);
|
2012-10-22 07:12:18 -06:00
|
|
|
err_i2c_bus:
|
|
|
|
intel_sdvo_unselect_i2c_bus(intel_sdvo);
|
2010-08-04 06:50:23 -06:00
|
|
|
kfree(intel_sdvo);
|
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-07 15:24:08 -07:00
|
|
|
|
2009-01-02 14:33:00 -07: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-07 15:24:08 -07:00
|
|
|
}
|