DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 06:24:08 +08:00
|
|
|
/*
|
|
|
|
* Copyright (c) 2006 Dave Airlie <airlied@linux.ie>
|
|
|
|
* Copyright (c) 2007-2008 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.
|
|
|
|
*/
|
|
|
|
#ifndef __INTEL_DRV_H__
|
|
|
|
#define __INTEL_DRV_H__
|
|
|
|
|
|
|
|
#include <linux/i2c.h>
|
2012-10-03 01:01:07 +08:00
|
|
|
#include <drm/i915_drm.h>
|
2009-09-11 06:28:06 +08:00
|
|
|
#include "i915_drv.h"
|
2012-10-03 01:01:07 +08:00
|
|
|
#include <drm/drm_crtc.h>
|
|
|
|
#include <drm/drm_crtc_helper.h>
|
|
|
|
#include <drm/drm_fb_helper.h>
|
Merge branch 'drm-next' of git://people.freedesktop.org/~airlied/linux
Pull drm merge (part 1) from Dave Airlie:
"So first of all my tree and uapi stuff has a conflict mess, its my
fault as the nouveau stuff didn't hit -next as were trying to rebase
regressions out of it before we merged.
Highlights:
- SH mobile modesetting driver and associated helpers
- some DRM core documentation
- i915 modesetting rework, haswell hdmi, haswell and vlv fixes, write
combined pte writing, ilk rc6 support,
- nouveau: major driver rework into a hw core driver, makes features
like SLI a lot saner to implement,
- psb: add eDP/DP support for Cedarview
- radeon: 2 layer page tables, async VM pte updates, better PLL
selection for > 2 screens, better ACPI interactions
The rest is general grab bag of fixes.
So why part 1? well I have the exynos pull req which came in a bit
late but was waiting for me to do something they shouldn't have and it
looks fairly safe, and David Howells has some more header cleanups
he'd like me to pull, that seem like a good idea, but I'd like to get
this merge out of the way so -next dosen't get blocked."
Tons of conflicts mostly due to silly include line changes, but mostly
mindless. A few other small semantic conflicts too, noted from Dave's
pre-merged branch.
* 'drm-next' of git://people.freedesktop.org/~airlied/linux: (447 commits)
drm/nv98/crypt: fix fuc build with latest envyas
drm/nouveau/devinit: fixup various issues with subdev ctor/init ordering
drm/nv41/vm: fix and enable use of "real" pciegart
drm/nv44/vm: fix and enable use of "real" pciegart
drm/nv04/dmaobj: fixup vm target handling in preparation for nv4x pcie
drm/nouveau: store supported dma mask in vmmgr
drm/nvc0/ibus: initial implementation of subdev
drm/nouveau/therm: add support for fan-control modes
drm/nouveau/hwmon: rename pwm0* to pmw1* to follow hwmon's rules
drm/nouveau/therm: calculate the pwm divisor on nv50+
drm/nouveau/fan: rewrite the fan tachometer driver to get more precision, faster
drm/nouveau/therm: move thermal-related functions to the therm subdev
drm/nouveau/bios: parse the pwm divisor from the perf table
drm/nouveau/therm: use the EXTDEV table to detect i2c monitoring devices
drm/nouveau/therm: rework thermal table parsing
drm/nouveau/gpio: expose the PWM/TOGGLE parameter found in the gpio vbios table
drm/nouveau: fix pm initialization order
drm/nouveau/bios: check that fixed tvdac gpio data is valid before using it
drm/nouveau: log channel debug/error messages from client object rather than drm client
drm/nouveau: have drm debugging macros build on top of core macros
...
2012-10-04 14:29:23 +08:00
|
|
|
#include <drm/drm_dp_helper.h>
|
2010-08-07 18:01:35 +08:00
|
|
|
|
2013-03-28 07:03:25 +08:00
|
|
|
/**
|
|
|
|
* _wait_for - magic (register) wait macro
|
|
|
|
*
|
|
|
|
* Does the right thing for modeset paths when run under kdgb or similar atomic
|
|
|
|
* contexts. Note that it's important that we check the condition again after
|
|
|
|
* having timed out, since the timeout could be due to preemption or similar and
|
|
|
|
* we've never had a chance to check the condition before the timeout.
|
|
|
|
*/
|
2010-08-24 00:43:35 +08:00
|
|
|
#define _wait_for(COND, MS, W) ({ \
|
2013-03-28 07:03:25 +08:00
|
|
|
unsigned long timeout__ = jiffies + msecs_to_jiffies(MS) + 1; \
|
2010-08-07 18:01:35 +08:00
|
|
|
int ret__ = 0; \
|
2011-08-17 03:34:10 +08:00
|
|
|
while (!(COND)) { \
|
2010-08-07 18:01:35 +08:00
|
|
|
if (time_after(jiffies, timeout__)) { \
|
2013-03-28 07:03:25 +08:00
|
|
|
if (!(COND)) \
|
|
|
|
ret__ = -ETIMEDOUT; \
|
2010-08-07 18:01:35 +08:00
|
|
|
break; \
|
|
|
|
} \
|
2012-09-02 13:59:48 +08:00
|
|
|
if (W && drm_can_sleep()) { \
|
|
|
|
msleep(W); \
|
|
|
|
} else { \
|
|
|
|
cpu_relax(); \
|
|
|
|
} \
|
2010-08-07 18:01:35 +08:00
|
|
|
} \
|
|
|
|
ret__; \
|
|
|
|
})
|
|
|
|
|
2010-08-24 00:43:35 +08:00
|
|
|
#define wait_for(COND, MS) _wait_for(COND, MS, 1)
|
|
|
|
#define wait_for_atomic(COND, MS) _wait_for(COND, MS, 0)
|
2013-03-28 18:31:04 +08:00
|
|
|
#define wait_for_atomic_us(COND, US) _wait_for((COND), \
|
|
|
|
DIV_ROUND_UP((US), 1000), 0)
|
2010-08-24 00:43:35 +08:00
|
|
|
|
2010-09-08 03:54:59 +08:00
|
|
|
#define KHz(x) (1000*x)
|
|
|
|
#define MHz(x) KHz(1000*x)
|
|
|
|
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 06:24:08 +08:00
|
|
|
/*
|
|
|
|
* Display related stuff
|
|
|
|
*/
|
|
|
|
|
|
|
|
/* store information about an Ixxx DVO */
|
|
|
|
/* The i830->i865 use multiple DVOs with multiple i2cs */
|
|
|
|
/* the i915, i945 have a single sDVO i2c bus - which is different */
|
|
|
|
#define MAX_OUTPUTS 6
|
|
|
|
/* maximum connectors per crtcs in the mode set */
|
|
|
|
#define INTELFB_CONN_LIMIT 4
|
|
|
|
|
|
|
|
#define INTEL_I2C_BUS_DVO 1
|
|
|
|
#define INTEL_I2C_BUS_SDVO 2
|
|
|
|
|
|
|
|
/* these are outputs from the chip - integrated only
|
|
|
|
external chips are via DVO or SDVO output */
|
|
|
|
#define INTEL_OUTPUT_UNUSED 0
|
|
|
|
#define INTEL_OUTPUT_ANALOG 1
|
|
|
|
#define INTEL_OUTPUT_DVO 2
|
|
|
|
#define INTEL_OUTPUT_SDVO 3
|
|
|
|
#define INTEL_OUTPUT_LVDS 4
|
|
|
|
#define INTEL_OUTPUT_TVOUT 5
|
2009-01-03 05:33:00 +08:00
|
|
|
#define INTEL_OUTPUT_HDMI 6
|
2009-04-08 07:16:42 +08:00
|
|
|
#define INTEL_OUTPUT_DISPLAYPORT 7
|
2009-07-24 01:00:32 +08:00
|
|
|
#define INTEL_OUTPUT_EDP 8
|
2012-10-27 05:05:52 +08:00
|
|
|
#define INTEL_OUTPUT_UNKNOWN 9
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 06:24:08 +08:00
|
|
|
|
|
|
|
#define INTEL_DVO_CHIP_NONE 0
|
|
|
|
#define INTEL_DVO_CHIP_LVDS 1
|
|
|
|
#define INTEL_DVO_CHIP_TMDS 2
|
|
|
|
#define INTEL_DVO_CHIP_TVOUT 4
|
|
|
|
|
|
|
|
struct intel_framebuffer {
|
|
|
|
struct drm_framebuffer base;
|
2010-11-09 03:18:58 +08:00
|
|
|
struct drm_i915_gem_object *obj;
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 06:24:08 +08:00
|
|
|
};
|
|
|
|
|
2010-08-26 05:45:57 +08:00
|
|
|
struct intel_fbdev {
|
|
|
|
struct drm_fb_helper helper;
|
|
|
|
struct intel_framebuffer ifb;
|
|
|
|
struct list_head fbdev_list;
|
|
|
|
struct drm_display_mode *our_mode;
|
|
|
|
};
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 06:24:08 +08:00
|
|
|
|
2010-03-26 02:11:14 +08:00
|
|
|
struct intel_encoder {
|
2010-09-09 22:14:28 +08:00
|
|
|
struct drm_encoder base;
|
drm/i915: stage modeset output changes
This is the core of the new modeset logic.
The current code which is based upon the crtc helper code first
updates all the link of the new display pipeline and then calls the
lower-level set_mode function to execute the required callbacks to get
there. The issue with this approach is that for disabling we need to
know the _current_ display pipe state, not the new one.
Hence we need to stage the new state of the display pipe and only
update it once we have disabled the current configuration and before we
start to update the hw registers with the new configuration.
This patch here just prepares the ground by switching the new output
state computation to these staging pointers. To make it clearer,
rename the old update_output_state function to stage_output_state.
A few peculiarities:
- We're also calling the set_mode function at various places to update
properties. Hence after a successfule modeset we need to stage the
current configuration (for otherwise we might fall back again). This
happens automatically because as part of the (successful) modeset we
need to copy the staged state to the real one. But for the hw
readout code we need to make sure that this happens, too.
- Teach the new staged output state computation code the required
smarts to handle the disabling of outputs. The current code handles
this in a special case, but to better handle global modeset changes
covering more than one crtc, we want to do this all in the same
low-level modeset code.
- The actual modeset code is still a bit ugly and wants to know the new
crtc->enabled state a bit early. Follow-on patches will clean that
up, for now we have to apply the staged output configuration early,
outside of the set_mode functions.
- Improve/add comments in stage_output_state.
Essentially all that is left to do now is move the disabling code into
set_mode and then move the staged state update code also into
set_mode, at the right place between disabling things and calling the
mode_set callbacks for the new configuration.
v2: Disabling a crtc works by passing in a NULL mode or fb, userspace
doesn't hand in the list of connectors. We therefore need to detect
this case manually and tear down all the output links.
v3: Properly update the output staging pointers after having read out
the hw state.
v4: Simplify the code, add more DRM_DEBUG_KMS output and check a few
assumptions with WARN_ON. Essentially all things that I've noticed
while debugging issues in other places of the code.
v4: Correctly disable the old set of connectors when enabling an
already enabled crtc on a new set of crtc. Reported by Paulo Zanoni.
Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
2012-07-06 04:34:27 +08:00
|
|
|
/*
|
|
|
|
* The new crtc this encoder will be driven from. Only differs from
|
|
|
|
* base->crtc while a modeset is in progress.
|
|
|
|
*/
|
|
|
|
struct intel_crtc *new_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-08 06:24:08 +08:00
|
|
|
int type;
|
2009-02-03 07:11:52 +08:00
|
|
|
bool needs_tv_clock;
|
2012-07-13 02:08:18 +08:00
|
|
|
/*
|
|
|
|
* Intel hw has only one MUX where encoders could be clone, hence a
|
|
|
|
* simple flag is enough to compute the possible_clones mask.
|
|
|
|
*/
|
|
|
|
bool cloneable;
|
2012-06-30 14:59:56 +08:00
|
|
|
bool connectors_active;
|
2010-03-26 02:11:14 +08:00
|
|
|
void (*hot_plug)(struct intel_encoder *);
|
2013-03-27 07:44:52 +08:00
|
|
|
bool (*compute_config)(struct intel_encoder *,
|
|
|
|
struct intel_crtc_config *);
|
2012-11-27 00:22:07 +08:00
|
|
|
void (*pre_pll_enable)(struct intel_encoder *);
|
2012-09-07 04:15:40 +08:00
|
|
|
void (*pre_enable)(struct intel_encoder *);
|
2012-06-30 04:40:09 +08:00
|
|
|
void (*enable)(struct intel_encoder *);
|
2013-03-27 07:44:53 +08:00
|
|
|
void (*mode_set)(struct intel_encoder *intel_encoder);
|
2012-06-30 04:40:09 +08:00
|
|
|
void (*disable)(struct intel_encoder *);
|
2012-09-07 04:15:40 +08:00
|
|
|
void (*post_disable)(struct intel_encoder *);
|
2012-07-02 19:10:34 +08:00
|
|
|
/* Read out the current hw state of this connector, returning true if
|
|
|
|
* the encoder is active. If the encoder is enabled it also set the pipe
|
|
|
|
* it is connected to in the pipe parameter. */
|
|
|
|
bool (*get_hw_state)(struct intel_encoder *, enum pipe *pipe);
|
2009-08-24 13:50:24 +08:00
|
|
|
int crtc_mask;
|
2013-02-26 01:06:49 +08:00
|
|
|
enum hpd_pin hpd_pin;
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 06:24:08 +08:00
|
|
|
};
|
|
|
|
|
2012-10-19 19:51:49 +08:00
|
|
|
struct intel_panel {
|
2012-10-19 19:51:50 +08:00
|
|
|
struct drm_display_mode *fixed_mode;
|
2012-10-26 17:03:59 +08:00
|
|
|
int fitting_mode;
|
2012-10-19 19:51:49 +08:00
|
|
|
};
|
|
|
|
|
2010-03-30 14:39:28 +08:00
|
|
|
struct intel_connector {
|
|
|
|
struct drm_connector base;
|
drm/i915: stage modeset output changes
This is the core of the new modeset logic.
The current code which is based upon the crtc helper code first
updates all the link of the new display pipeline and then calls the
lower-level set_mode function to execute the required callbacks to get
there. The issue with this approach is that for disabling we need to
know the _current_ display pipe state, not the new one.
Hence we need to stage the new state of the display pipe and only
update it once we have disabled the current configuration and before we
start to update the hw registers with the new configuration.
This patch here just prepares the ground by switching the new output
state computation to these staging pointers. To make it clearer,
rename the old update_output_state function to stage_output_state.
A few peculiarities:
- We're also calling the set_mode function at various places to update
properties. Hence after a successfule modeset we need to stage the
current configuration (for otherwise we might fall back again). This
happens automatically because as part of the (successful) modeset we
need to copy the staged state to the real one. But for the hw
readout code we need to make sure that this happens, too.
- Teach the new staged output state computation code the required
smarts to handle the disabling of outputs. The current code handles
this in a special case, but to better handle global modeset changes
covering more than one crtc, we want to do this all in the same
low-level modeset code.
- The actual modeset code is still a bit ugly and wants to know the new
crtc->enabled state a bit early. Follow-on patches will clean that
up, for now we have to apply the staged output configuration early,
outside of the set_mode functions.
- Improve/add comments in stage_output_state.
Essentially all that is left to do now is move the disabling code into
set_mode and then move the staged state update code also into
set_mode, at the right place between disabling things and calling the
mode_set callbacks for the new configuration.
v2: Disabling a crtc works by passing in a NULL mode or fb, userspace
doesn't hand in the list of connectors. We therefore need to detect
this case manually and tear down all the output links.
v3: Properly update the output staging pointers after having read out
the hw state.
v4: Simplify the code, add more DRM_DEBUG_KMS output and check a few
assumptions with WARN_ON. Essentially all things that I've noticed
while debugging issues in other places of the code.
v4: Correctly disable the old set of connectors when enabling an
already enabled crtc on a new set of crtc. Reported by Paulo Zanoni.
Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
2012-07-06 04:34:27 +08:00
|
|
|
/*
|
|
|
|
* The fixed encoder this connector is connected to.
|
|
|
|
*/
|
2010-09-09 23:20:55 +08:00
|
|
|
struct intel_encoder *encoder;
|
drm/i915: stage modeset output changes
This is the core of the new modeset logic.
The current code which is based upon the crtc helper code first
updates all the link of the new display pipeline and then calls the
lower-level set_mode function to execute the required callbacks to get
there. The issue with this approach is that for disabling we need to
know the _current_ display pipe state, not the new one.
Hence we need to stage the new state of the display pipe and only
update it once we have disabled the current configuration and before we
start to update the hw registers with the new configuration.
This patch here just prepares the ground by switching the new output
state computation to these staging pointers. To make it clearer,
rename the old update_output_state function to stage_output_state.
A few peculiarities:
- We're also calling the set_mode function at various places to update
properties. Hence after a successfule modeset we need to stage the
current configuration (for otherwise we might fall back again). This
happens automatically because as part of the (successful) modeset we
need to copy the staged state to the real one. But for the hw
readout code we need to make sure that this happens, too.
- Teach the new staged output state computation code the required
smarts to handle the disabling of outputs. The current code handles
this in a special case, but to better handle global modeset changes
covering more than one crtc, we want to do this all in the same
low-level modeset code.
- The actual modeset code is still a bit ugly and wants to know the new
crtc->enabled state a bit early. Follow-on patches will clean that
up, for now we have to apply the staged output configuration early,
outside of the set_mode functions.
- Improve/add comments in stage_output_state.
Essentially all that is left to do now is move the disabling code into
set_mode and then move the staged state update code also into
set_mode, at the right place between disabling things and calling the
mode_set callbacks for the new configuration.
v2: Disabling a crtc works by passing in a NULL mode or fb, userspace
doesn't hand in the list of connectors. We therefore need to detect
this case manually and tear down all the output links.
v3: Properly update the output staging pointers after having read out
the hw state.
v4: Simplify the code, add more DRM_DEBUG_KMS output and check a few
assumptions with WARN_ON. Essentially all things that I've noticed
while debugging issues in other places of the code.
v4: Correctly disable the old set of connectors when enabling an
already enabled crtc on a new set of crtc. Reported by Paulo Zanoni.
Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
2012-07-06 04:34:27 +08:00
|
|
|
|
|
|
|
/*
|
|
|
|
* The new encoder this connector will be driven. Only differs from
|
|
|
|
* encoder while a modeset is in progress.
|
|
|
|
*/
|
|
|
|
struct intel_encoder *new_encoder;
|
|
|
|
|
2012-07-02 19:10:34 +08:00
|
|
|
/* Reads out the current hw, returning true if the connector is enabled
|
|
|
|
* and active (i.e. dpms ON state). */
|
|
|
|
bool (*get_hw_state)(struct intel_connector *);
|
2012-10-19 19:51:49 +08:00
|
|
|
|
|
|
|
/* Panel info for eDP and LVDS */
|
|
|
|
struct intel_panel panel;
|
2012-10-19 19:51:52 +08:00
|
|
|
|
|
|
|
/* Cached EDID for eDP and LVDS. May hold ERR_PTR for invalid EDID. */
|
|
|
|
struct edid *edid;
|
2010-03-30 14:39:28 +08:00
|
|
|
};
|
|
|
|
|
2013-03-27 07:44:50 +08:00
|
|
|
struct intel_crtc_config {
|
|
|
|
struct drm_display_mode requested_mode;
|
|
|
|
struct drm_display_mode adjusted_mode;
|
2013-03-27 07:44:52 +08:00
|
|
|
/* This flag must be set by the encoder's compute_config callback if it
|
|
|
|
* changes the crtc timings in the mode to prevent the crtc fixup from
|
|
|
|
* overwriting them. Currently only lvds needs that. */
|
|
|
|
bool timings_set;
|
2013-03-27 07:44:55 +08:00
|
|
|
/* Whether to set up the PCH/FDI. Note that we never allow sharing
|
|
|
|
* between pch encoders and cpu encoders. */
|
|
|
|
bool has_pch_encoder;
|
2013-03-27 07:44:56 +08:00
|
|
|
|
|
|
|
/*
|
|
|
|
* Use reduced/limited/broadcast rbg range, compressing from the full
|
|
|
|
* range fed into the crtcs.
|
|
|
|
*/
|
|
|
|
bool limited_color_range;
|
|
|
|
|
2013-04-03 05:42:31 +08:00
|
|
|
/* DP has a bunch of special case unfortunately, so mark the pipe
|
|
|
|
* accordingly. */
|
|
|
|
bool has_dp_encoder;
|
2013-03-27 07:44:57 +08:00
|
|
|
bool dither;
|
2013-03-28 17:42:02 +08:00
|
|
|
|
|
|
|
/* Controls for the clock computation, to override various stages. */
|
|
|
|
bool clock_set;
|
|
|
|
|
|
|
|
/* Settings for the intel dpll used on pretty much everything but
|
|
|
|
* haswell. */
|
|
|
|
struct dpll {
|
|
|
|
unsigned n;
|
|
|
|
unsigned m1, m2;
|
|
|
|
unsigned p1, p2;
|
|
|
|
} dpll;
|
|
|
|
|
2013-03-27 07:44:57 +08:00
|
|
|
int pipe_bpp;
|
drm/i915: clear up the fdi/dp set_m_n confusion
There's a rather decent confusion going on around transcoder m_n
values. So let's clarify:
- All dp encoders need this, either on the pch transcoder if it's a
pch port, or on the cpu transcoder/pipe if it's a cpu port.
- fdi links need to have the right m_n values for the fdi link set in
the cpu transcoder.
To handle the pch vs transcoder stuff a bit better, extract transcoder
set_m_n helpers. To make them simpler, set intel_crtc->cpu_transcoder
als in ironlake_crtc_mode_set, so that gen5+ (where the cpu m_n
registers are all at the same offset) can use it.
Haswell modeset is decently confused about dp vs. edp vs. fdi. dp vs.
edp works exactly the same as dp (since there's no pch dp any more),
so use that as a check. And only set up the fdi m_n values if we
really have a pch encoder present (which means we have a VGA encoder).
On ilk+ we've called ironlake_set_m_n both for cpu_edp and for pch
encoders. Now that dp_set_m_n handles all dp links (thanks to the
pch encoder check), we can ditch the cpu_edp stuff from the
fdi_set_m_n function.
Since the dp_m_n values are not readily available, we need to
carefully coax the edp values out of the encoder. Hence we can't (yet)
kill this superflous complexity.
v2: Rebase on top of the ivb fdi B/C check patch - we need to properly
clear intel_crtc->fdi_lane, otherwise those checks will misfire.
v3: Rebased on top of a s/IS_HASWELL/HAS_DDI/ patch from Paulo Zanoni.
v4: Drop the addition of has_dp_encoder, it's in the wrong patch (Jesse).
Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
2013-04-03 05:38:10 +08:00
|
|
|
struct intel_link_m_n dp_m_n;
|
2013-03-28 17:41:58 +08:00
|
|
|
/**
|
|
|
|
* This is currently used by DP and HDMI encoders since those can have a
|
|
|
|
* target pixel clock != the port link clock (which is currently stored
|
|
|
|
* in adjusted_mode->clock).
|
|
|
|
*/
|
|
|
|
int pixel_target_clock;
|
2013-03-27 07:44:53 +08:00
|
|
|
/* Used by SDVO (and if we ever fix it, HDMI). */
|
|
|
|
unsigned pixel_multiplier;
|
2013-03-27 07:44:50 +08:00
|
|
|
};
|
|
|
|
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 06:24:08 +08:00
|
|
|
struct intel_crtc {
|
|
|
|
struct drm_crtc base;
|
2009-09-11 06:28:06 +08:00
|
|
|
enum pipe pipe;
|
|
|
|
enum plane plane;
|
drm/i915: add TRANSCODER_EDP
Before Haswell we used to have the CPU pipes and the PCH transcoders.
We had the same amount of pipes and transcoders, and there was a 1:1
mapping between them. After Haswell what we used to call CPU pipe was
split into CPU pipe and CPU transcoder. So now we have 3 CPU pipes (A,
B and C), 4 CPU transcoders (A, B, C and EDP) and 1 PCH transcoder
(only used for VGA).
For all the outputs except for EDP we have an 1:1 mapping on the CPU
pipes and CPU transcoders, so if you're using CPU pipe A you have to
use CPU transcoder A. When have an eDP output you have to use
transcoder EDP and you can attach this CPU transcoder to any of the 3
CPU pipes. When using VGA you need to select a pair of matching CPU
pipes/transcoders (A/A, B/B, C/C) and you also need to enable/use the
PCH transcoder.
For now we're just creating the cpu_transcoder definitions and setting
cpu_transcoder to TRANSCODER_EDP on DDI eDP code, but none of the
registers was ported to use transcoder instead of pipe. The goal is to
keep the code backwards-compatible since on all cases except when
using eDP we must have pipe == cpu_transcoder.
V2: Comment the haswell_crtc_off chunk, suggested by Damien Lespiau
and Daniel Vetter.
We currently need the haswell_crtc_off chunk because TRANSCODER_EDP
can be used by any CRTC, so when you stop using it you have to stop
saying you're using it, otherwise you may have at some point 2 CRTCs
claiming they're using TRANSCODER_EDP (a disabled CRTC and an enabled
one), then the HW state readout code will get completely confused.
In other words:
Imagine the following case:
xrandr --output eDP1 --auto --crtc 0
xrandr --output eDP1 --off
xrandr --output eDP1 --auto --crtc 2
After the last command you could get a "pipe A assertion failure
(expected off, current on)" because CRTC 0 still claims it's using
TRANSCODER_EDP, so the HW state readout function will read it
(through PIPECONF) and expect it to be off, when it's actually on
because it's being used by CRTC 2.
So when we make "intel_crtc->cpu_transcoder = intel_crtc->pipe" we
make sure we're pointing to our own original CRTC which is certainly
not used by any other CRTC.
Signed-off-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
Reviewed-by: Damien Lespiau <damien.lespiau@intel.com>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
2012-10-25 01:59:34 +08:00
|
|
|
enum transcoder cpu_transcoder;
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 06:24:08 +08:00
|
|
|
u8 lut_r[256], lut_g[256], lut_b[256];
|
2012-07-02 17:43:47 +08:00
|
|
|
/*
|
|
|
|
* Whether the crtc and the connected output pipeline is active. Implies
|
|
|
|
* that crtc->enabled is set, i.e. the current mode configuration has
|
|
|
|
* some outputs connected to this crtc.
|
|
|
|
*/
|
|
|
|
bool active;
|
2013-01-22 23:25:25 +08:00
|
|
|
bool eld_vld;
|
2012-06-14 00:36:55 +08:00
|
|
|
bool primary_disabled; /* is the crtc obscured by a plane? */
|
2009-08-18 04:31:43 +08:00
|
|
|
bool lowfreq_avail;
|
2009-09-16 04:57:34 +08:00
|
|
|
struct intel_overlay *overlay;
|
2009-11-19 00:25:18 +08:00
|
|
|
struct intel_unpin_work *unpin_work;
|
2010-04-12 23:38:44 +08:00
|
|
|
int fdi_lanes;
|
2010-07-09 15:45:04 +08:00
|
|
|
|
2012-11-01 17:26:26 +08:00
|
|
|
atomic_t unpin_work_count;
|
|
|
|
|
2012-07-05 18:17:29 +08:00
|
|
|
/* Display surface base address adjustement for pageflips. Note that on
|
|
|
|
* gen4+ this only adjusts up to a tile, offsets within a tile are
|
|
|
|
* handled in the hw itself (with the TILEOFF register). */
|
|
|
|
unsigned long dspaddr_offset;
|
|
|
|
|
2010-11-09 03:18:58 +08:00
|
|
|
struct drm_i915_gem_object *cursor_bo;
|
2010-07-09 15:45:04 +08:00
|
|
|
uint32_t cursor_addr;
|
|
|
|
int16_t cursor_x, cursor_y;
|
|
|
|
int16_t cursor_width, cursor_height;
|
2010-09-13 20:54:26 +08:00
|
|
|
bool cursor_visible;
|
2011-10-13 00:51:31 +08:00
|
|
|
|
2013-03-27 07:44:50 +08:00
|
|
|
struct intel_crtc_config config;
|
|
|
|
|
2012-04-21 00:11:53 +08:00
|
|
|
/* We can share PLLs across outputs if the timings match */
|
|
|
|
struct intel_pch_pll *pch_pll;
|
2012-10-05 23:05:58 +08:00
|
|
|
uint32_t ddi_pll_sel;
|
2013-01-30 00:13:34 +08:00
|
|
|
|
|
|
|
/* reset counter value when the last flip was submitted */
|
|
|
|
unsigned int reset_counter;
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 06:24:08 +08:00
|
|
|
};
|
|
|
|
|
2011-12-14 05:19:38 +08:00
|
|
|
struct intel_plane {
|
|
|
|
struct drm_plane base;
|
2013-04-03 02:22:20 +08:00
|
|
|
int plane;
|
2011-12-14 05:19:38 +08:00
|
|
|
enum pipe pipe;
|
|
|
|
struct drm_i915_gem_object *obj;
|
2012-10-23 01:19:27 +08:00
|
|
|
bool can_scale;
|
2011-12-14 05:19:38 +08:00
|
|
|
int max_downscale;
|
|
|
|
u32 lut_r[1024], lut_g[1024], lut_b[1024];
|
2013-03-27 00:25:43 +08:00
|
|
|
int crtc_x, crtc_y;
|
|
|
|
unsigned int crtc_w, crtc_h;
|
|
|
|
uint32_t src_x, src_y;
|
|
|
|
uint32_t src_w, src_h;
|
2011-12-14 05:19:38 +08:00
|
|
|
void (*update_plane)(struct drm_plane *plane,
|
|
|
|
struct drm_framebuffer *fb,
|
|
|
|
struct drm_i915_gem_object *obj,
|
|
|
|
int crtc_x, int crtc_y,
|
|
|
|
unsigned int crtc_w, unsigned int crtc_h,
|
|
|
|
uint32_t x, uint32_t y,
|
|
|
|
uint32_t src_w, uint32_t src_h);
|
|
|
|
void (*disable_plane)(struct drm_plane *plane);
|
2012-01-04 00:05:39 +08:00
|
|
|
int (*update_colorkey)(struct drm_plane *plane,
|
|
|
|
struct drm_intel_sprite_colorkey *key);
|
|
|
|
void (*get_colorkey)(struct drm_plane *plane,
|
|
|
|
struct drm_intel_sprite_colorkey *key);
|
2011-12-14 05:19:38 +08:00
|
|
|
};
|
|
|
|
|
2012-04-17 09:20:35 +08:00
|
|
|
struct intel_watermark_params {
|
|
|
|
unsigned long fifo_size;
|
|
|
|
unsigned long max_wm;
|
|
|
|
unsigned long default_wm;
|
|
|
|
unsigned long guard_size;
|
|
|
|
unsigned long cacheline_size;
|
|
|
|
};
|
|
|
|
|
|
|
|
struct cxsr_latency {
|
|
|
|
int is_desktop;
|
|
|
|
int is_ddr3;
|
|
|
|
unsigned long fsb_freq;
|
|
|
|
unsigned long mem_freq;
|
|
|
|
unsigned long display_sr;
|
|
|
|
unsigned long display_hpll_disable;
|
|
|
|
unsigned long cursor_sr;
|
|
|
|
unsigned long cursor_hpll_disable;
|
|
|
|
};
|
|
|
|
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 06:24:08 +08:00
|
|
|
#define to_intel_crtc(x) container_of(x, struct intel_crtc, base)
|
2010-03-30 14:39:28 +08:00
|
|
|
#define to_intel_connector(x) container_of(x, struct intel_connector, base)
|
2010-09-09 22:14:28 +08:00
|
|
|
#define to_intel_encoder(x) container_of(x, struct intel_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-08 06:24:08 +08:00
|
|
|
#define to_intel_framebuffer(x) container_of(x, struct intel_framebuffer, base)
|
2011-12-14 05:19:38 +08:00
|
|
|
#define to_intel_plane(x) container_of(x, struct intel_plane, base)
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 06:24:08 +08:00
|
|
|
|
2011-08-04 00:22:55 +08:00
|
|
|
#define DIP_HEADER_SIZE 5
|
|
|
|
|
2010-09-25 03:44:32 +08:00
|
|
|
#define DIP_TYPE_AVI 0x82
|
|
|
|
#define DIP_VERSION_AVI 0x2
|
|
|
|
#define DIP_LEN_AVI 13
|
2012-04-14 03:31:41 +08:00
|
|
|
#define DIP_AVI_PR_1 0
|
|
|
|
#define DIP_AVI_PR_2 1
|
2013-01-17 22:31:31 +08:00
|
|
|
#define DIP_AVI_RGB_QUANT_RANGE_DEFAULT (0 << 2)
|
|
|
|
#define DIP_AVI_RGB_QUANT_RANGE_LIMITED (1 << 2)
|
|
|
|
#define DIP_AVI_RGB_QUANT_RANGE_FULL (2 << 2)
|
2010-09-25 03:44:32 +08:00
|
|
|
|
2011-09-22 13:46:01 +08:00
|
|
|
#define DIP_TYPE_SPD 0x83
|
2011-08-04 00:22:56 +08:00
|
|
|
#define DIP_VERSION_SPD 0x1
|
|
|
|
#define DIP_LEN_SPD 25
|
|
|
|
#define DIP_SPD_UNKNOWN 0
|
|
|
|
#define DIP_SPD_DSTB 0x1
|
|
|
|
#define DIP_SPD_DVDP 0x2
|
|
|
|
#define DIP_SPD_DVHS 0x3
|
|
|
|
#define DIP_SPD_HDDVR 0x4
|
|
|
|
#define DIP_SPD_DVC 0x5
|
|
|
|
#define DIP_SPD_DSC 0x6
|
|
|
|
#define DIP_SPD_VCD 0x7
|
|
|
|
#define DIP_SPD_GAME 0x8
|
|
|
|
#define DIP_SPD_PC 0x9
|
|
|
|
#define DIP_SPD_BD 0xa
|
|
|
|
#define DIP_SPD_SCD 0xb
|
|
|
|
|
2010-09-25 03:44:32 +08:00
|
|
|
struct dip_infoframe {
|
|
|
|
uint8_t type; /* HB0 */
|
|
|
|
uint8_t ver; /* HB1 */
|
|
|
|
uint8_t len; /* HB2 - body len, not including checksum */
|
|
|
|
uint8_t ecc; /* Header ECC */
|
|
|
|
uint8_t checksum; /* PB0 */
|
|
|
|
union {
|
|
|
|
struct {
|
|
|
|
/* PB1 - Y 6:5, A 4:4, B 3:2, S 1:0 */
|
|
|
|
uint8_t Y_A_B_S;
|
|
|
|
/* PB2 - C 7:6, M 5:4, R 3:0 */
|
|
|
|
uint8_t C_M_R;
|
|
|
|
/* PB3 - ITC 7:7, EC 6:4, Q 3:2, SC 1:0 */
|
|
|
|
uint8_t ITC_EC_Q_SC;
|
|
|
|
/* PB4 - VIC 6:0 */
|
|
|
|
uint8_t VIC;
|
2012-04-14 03:31:40 +08:00
|
|
|
/* PB5 - YQ 7:6, CN 5:4, PR 3:0 */
|
|
|
|
uint8_t YQ_CN_PR;
|
2010-09-25 03:44:32 +08:00
|
|
|
/* PB6 to PB13 */
|
|
|
|
uint16_t top_bar_end;
|
|
|
|
uint16_t bottom_bar_start;
|
|
|
|
uint16_t left_bar_end;
|
|
|
|
uint16_t right_bar_start;
|
2012-05-13 02:22:00 +08:00
|
|
|
} __attribute__ ((packed)) avi;
|
2011-08-04 00:22:56 +08:00
|
|
|
struct {
|
|
|
|
uint8_t vn[8];
|
|
|
|
uint8_t pd[16];
|
|
|
|
uint8_t sdi;
|
2012-05-13 02:22:00 +08:00
|
|
|
} __attribute__ ((packed)) spd;
|
2010-09-25 03:44:32 +08:00
|
|
|
uint8_t payload[27];
|
|
|
|
} __attribute__ ((packed)) body;
|
|
|
|
} __attribute__((packed));
|
|
|
|
|
2012-05-10 02:37:30 +08:00
|
|
|
struct intel_hdmi {
|
2013-02-19 06:00:26 +08:00
|
|
|
u32 hdmi_reg;
|
2012-05-10 02:37:30 +08:00
|
|
|
int ddc_bus;
|
|
|
|
uint32_t color_range;
|
2013-01-17 22:31:29 +08:00
|
|
|
bool color_range_auto;
|
2012-05-10 02:37:30 +08:00
|
|
|
bool has_hdmi_sink;
|
|
|
|
bool has_audio;
|
|
|
|
enum hdmi_force_audio force_audio;
|
2013-01-17 22:31:31 +08:00
|
|
|
bool rgb_quant_range_selectable;
|
2012-05-10 02:37:30 +08:00
|
|
|
void (*write_infoframe)(struct drm_encoder *encoder,
|
|
|
|
struct dip_infoframe *frame);
|
2012-05-29 03:42:48 +08:00
|
|
|
void (*set_infoframes)(struct drm_encoder *encoder,
|
|
|
|
struct drm_display_mode *adjusted_mode);
|
2012-05-10 02:37:30 +08:00
|
|
|
};
|
|
|
|
|
2012-09-18 22:58:49 +08:00
|
|
|
#define DP_MAX_DOWNSTREAM_PORTS 0x10
|
2012-06-30 03:03:35 +08:00
|
|
|
#define DP_LINK_CONFIGURATION_SIZE 9
|
|
|
|
|
|
|
|
struct intel_dp {
|
|
|
|
uint32_t output_reg;
|
2013-02-19 06:00:25 +08:00
|
|
|
uint32_t aux_ch_ctl_reg;
|
2012-06-30 03:03:35 +08:00
|
|
|
uint32_t DP;
|
|
|
|
uint8_t link_configuration[DP_LINK_CONFIGURATION_SIZE];
|
|
|
|
bool has_audio;
|
|
|
|
enum hdmi_force_audio force_audio;
|
|
|
|
uint32_t color_range;
|
2013-01-17 22:31:29 +08:00
|
|
|
bool color_range_auto;
|
2012-06-30 03:03:35 +08:00
|
|
|
uint8_t link_bw;
|
|
|
|
uint8_t lane_count;
|
|
|
|
uint8_t dpcd[DP_RECEIVER_CAP_SIZE];
|
2012-09-18 22:58:49 +08:00
|
|
|
uint8_t downstream_ports[DP_MAX_DOWNSTREAM_PORTS];
|
2012-06-30 03:03:35 +08:00
|
|
|
struct i2c_adapter adapter;
|
|
|
|
struct i2c_algo_dp_aux_data algo;
|
|
|
|
bool is_pch_edp;
|
|
|
|
uint8_t train_set[4];
|
|
|
|
int panel_power_up_delay;
|
|
|
|
int panel_power_down_delay;
|
|
|
|
int panel_power_cycle_delay;
|
|
|
|
int backlight_on_delay;
|
|
|
|
int backlight_off_delay;
|
|
|
|
struct delayed_work panel_vdd_work;
|
|
|
|
bool want_panel_vdd;
|
2012-10-19 19:51:50 +08:00
|
|
|
struct intel_connector *attached_connector;
|
2012-06-30 03:03:35 +08:00
|
|
|
};
|
|
|
|
|
2012-10-27 05:05:46 +08:00
|
|
|
struct intel_digital_port {
|
|
|
|
struct intel_encoder base;
|
2012-10-27 05:05:50 +08:00
|
|
|
enum port port;
|
2012-12-12 02:48:30 +08:00
|
|
|
u32 port_reversal;
|
2012-10-27 05:05:46 +08:00
|
|
|
struct intel_dp dp;
|
|
|
|
struct intel_hdmi hdmi;
|
|
|
|
};
|
|
|
|
|
2010-09-09 22:44:14 +08:00
|
|
|
static inline struct drm_crtc *
|
|
|
|
intel_get_crtc_for_pipe(struct drm_device *dev, int pipe)
|
|
|
|
{
|
|
|
|
struct drm_i915_private *dev_priv = dev->dev_private;
|
|
|
|
return dev_priv->pipe_to_crtc_mapping[pipe];
|
|
|
|
}
|
|
|
|
|
2011-01-19 23:04:42 +08:00
|
|
|
static inline struct drm_crtc *
|
|
|
|
intel_get_crtc_for_plane(struct drm_device *dev, int plane)
|
|
|
|
{
|
|
|
|
struct drm_i915_private *dev_priv = dev->dev_private;
|
|
|
|
return dev_priv->plane_to_crtc_mapping[plane];
|
|
|
|
}
|
|
|
|
|
2010-09-02 00:47:52 +08:00
|
|
|
struct intel_unpin_work {
|
|
|
|
struct work_struct work;
|
2012-11-01 17:26:26 +08:00
|
|
|
struct drm_crtc *crtc;
|
2010-11-09 03:18:58 +08:00
|
|
|
struct drm_i915_gem_object *old_fb_obj;
|
|
|
|
struct drm_i915_gem_object *pending_flip_obj;
|
2010-09-02 00:47:52 +08:00
|
|
|
struct drm_pending_vblank_event *event;
|
2012-12-03 19:36:30 +08:00
|
|
|
atomic_t pending;
|
|
|
|
#define INTEL_FLIP_INACTIVE 0
|
|
|
|
#define INTEL_FLIP_PENDING 1
|
|
|
|
#define INTEL_FLIP_COMPLETE 2
|
2010-09-02 00:47:52 +08:00
|
|
|
bool enable_stall_check;
|
|
|
|
};
|
|
|
|
|
2011-07-08 19:22:42 +08:00
|
|
|
struct intel_fbc_work {
|
|
|
|
struct delayed_work work;
|
|
|
|
struct drm_crtc *crtc;
|
|
|
|
struct drm_framebuffer *fb;
|
|
|
|
int interval;
|
|
|
|
};
|
|
|
|
|
2012-10-21 02:57:43 +08:00
|
|
|
int intel_pch_rawclk(struct drm_device *dev);
|
|
|
|
|
2012-08-13 18:22:34 +08:00
|
|
|
int intel_connector_update_modes(struct drm_connector *connector,
|
|
|
|
struct edid *edid);
|
2010-03-30 14:39:31 +08:00
|
|
|
int intel_ddc_get_modes(struct drm_connector *c, struct i2c_adapter *adapter);
|
2009-12-02 03:56:30 +08:00
|
|
|
|
2011-05-13 05:17:24 +08:00
|
|
|
extern void intel_attach_force_audio_property(struct drm_connector *connector);
|
2011-02-22 06:23:52 +08:00
|
|
|
extern void intel_attach_broadcast_rgb_property(struct drm_connector *connector);
|
|
|
|
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 06:24:08 +08:00
|
|
|
extern void intel_crt_init(struct drm_device *dev);
|
2012-07-13 02:19:59 +08:00
|
|
|
extern void intel_hdmi_init(struct drm_device *dev,
|
2013-02-19 06:00:26 +08:00
|
|
|
int hdmi_reg, enum port port);
|
2012-10-27 05:05:52 +08:00
|
|
|
extern void intel_hdmi_init_connector(struct intel_digital_port *intel_dig_port,
|
|
|
|
struct intel_connector *intel_connector);
|
2012-05-10 02:37:30 +08:00
|
|
|
extern struct intel_hdmi *enc_to_intel_hdmi(struct drm_encoder *encoder);
|
2013-03-27 07:44:55 +08:00
|
|
|
extern bool intel_hdmi_compute_config(struct intel_encoder *encoder,
|
|
|
|
struct intel_crtc_config *pipe_config);
|
2012-05-10 02:37:30 +08:00
|
|
|
extern void intel_dip_infoframe_csum(struct dip_infoframe *avi_if);
|
2012-03-24 06:43:35 +08:00
|
|
|
extern 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-08 06:24:08 +08:00
|
|
|
extern void intel_dvo_init(struct drm_device *dev);
|
|
|
|
extern void intel_tv_init(struct drm_device *dev);
|
2012-07-21 19:31:41 +08:00
|
|
|
extern void intel_mark_busy(struct drm_device *dev);
|
|
|
|
extern void intel_mark_fb_busy(struct drm_i915_gem_object *obj);
|
2013-01-08 19:02:57 +08:00
|
|
|
extern void intel_mark_idle(struct drm_device *dev);
|
2010-11-30 02:00:23 +08:00
|
|
|
extern bool intel_lvds_init(struct drm_device *dev);
|
2012-11-27 00:22:09 +08:00
|
|
|
extern bool intel_is_dual_link_lvds(struct drm_device *dev);
|
2012-07-18 04:53:45 +08:00
|
|
|
extern void intel_dp_init(struct drm_device *dev, int output_reg,
|
|
|
|
enum port port);
|
2012-10-27 05:05:52 +08:00
|
|
|
extern void intel_dp_init_connector(struct intel_digital_port *intel_dig_port,
|
|
|
|
struct intel_connector *intel_connector);
|
2012-10-16 02:51:33 +08:00
|
|
|
extern void intel_dp_init_link_config(struct intel_dp *intel_dp);
|
2012-10-16 02:51:41 +08:00
|
|
|
extern void intel_dp_start_link_train(struct intel_dp *intel_dp);
|
|
|
|
extern void intel_dp_complete_link_train(struct intel_dp *intel_dp);
|
|
|
|
extern void intel_dp_sink_dpms(struct intel_dp *intel_dp, int mode);
|
2012-10-27 05:05:52 +08:00
|
|
|
extern void intel_dp_encoder_destroy(struct drm_encoder *encoder);
|
|
|
|
extern void intel_dp_check_link_status(struct intel_dp *intel_dp);
|
2013-03-27 07:44:55 +08:00
|
|
|
extern bool intel_dp_compute_config(struct intel_encoder *encoder,
|
|
|
|
struct intel_crtc_config *pipe_config);
|
2010-07-17 02:46:29 +08:00
|
|
|
extern bool intel_dpd_is_edp(struct drm_device *dev);
|
2012-10-24 04:30:06 +08:00
|
|
|
extern void ironlake_edp_backlight_on(struct intel_dp *intel_dp);
|
|
|
|
extern void ironlake_edp_backlight_off(struct intel_dp *intel_dp);
|
2012-10-24 04:30:07 +08:00
|
|
|
extern void ironlake_edp_panel_on(struct intel_dp *intel_dp);
|
|
|
|
extern void ironlake_edp_panel_off(struct intel_dp *intel_dp);
|
|
|
|
extern void ironlake_edp_panel_vdd_on(struct intel_dp *intel_dp);
|
|
|
|
extern void ironlake_edp_panel_vdd_off(struct intel_dp *intel_dp, bool sync);
|
2010-10-08 07:01:09 +08:00
|
|
|
extern bool intel_encoder_is_pch_edp(struct drm_encoder *encoder);
|
2013-04-03 02:22:20 +08:00
|
|
|
extern int intel_plane_init(struct drm_device *dev, enum pipe pipe, int plane);
|
2012-04-19 02:29:25 +08:00
|
|
|
extern void intel_flush_display_plane(struct drm_i915_private *dev_priv,
|
|
|
|
enum plane plane);
|
2009-07-24 01:00:32 +08:00
|
|
|
|
2010-08-22 20:18:16 +08:00
|
|
|
/* intel_panel.c */
|
2012-10-19 19:51:50 +08:00
|
|
|
extern int intel_panel_init(struct intel_panel *panel,
|
|
|
|
struct drm_display_mode *fixed_mode);
|
2012-10-19 19:51:49 +08:00
|
|
|
extern void intel_panel_fini(struct intel_panel *panel);
|
|
|
|
|
2010-08-07 18:01:28 +08:00
|
|
|
extern void intel_fixed_panel_mode(struct drm_display_mode *fixed_mode,
|
|
|
|
struct drm_display_mode *adjusted_mode);
|
|
|
|
extern void intel_pch_panel_fitting(struct drm_device *dev,
|
|
|
|
int fitting_mode,
|
2012-06-05 00:39:21 +08:00
|
|
|
const struct drm_display_mode *mode,
|
2010-08-07 18:01:28 +08:00
|
|
|
struct drm_display_mode *adjusted_mode);
|
2010-08-22 20:18:16 +08:00
|
|
|
extern u32 intel_panel_get_max_backlight(struct drm_device *dev);
|
|
|
|
extern void intel_panel_set_backlight(struct drm_device *dev, u32 level);
|
2012-10-19 19:51:46 +08:00
|
|
|
extern int intel_panel_setup_backlight(struct drm_connector *connector);
|
2012-06-05 18:14:54 +08:00
|
|
|
extern void intel_panel_enable_backlight(struct drm_device *dev,
|
|
|
|
enum pipe pipe);
|
2011-01-12 01:06:04 +08:00
|
|
|
extern void intel_panel_disable_backlight(struct drm_device *dev);
|
2011-08-12 18:11:33 +08:00
|
|
|
extern void intel_panel_destroy_backlight(struct drm_device *dev);
|
2011-02-12 18:29:38 +08:00
|
|
|
extern enum drm_connector_status intel_panel_detect(struct drm_device *dev);
|
2010-08-07 18:01:28 +08:00
|
|
|
|
2012-07-05 04:16:09 +08:00
|
|
|
struct intel_set_config {
|
2012-07-05 22:20:48 +08:00
|
|
|
struct drm_encoder **save_connector_encoders;
|
|
|
|
struct drm_crtc **save_encoder_crtcs;
|
2012-07-05 04:41:29 +08:00
|
|
|
|
|
|
|
bool fb_changed;
|
|
|
|
bool mode_changed;
|
2012-07-05 04:16:09 +08:00
|
|
|
};
|
|
|
|
|
2012-12-20 00:08:43 +08:00
|
|
|
extern int intel_set_mode(struct drm_crtc *crtc, struct drm_display_mode *mode,
|
|
|
|
int x, int y, struct drm_framebuffer *old_fb);
|
2012-07-27 01:21:47 +08:00
|
|
|
extern void intel_modeset_disable(struct drm_device *dev);
|
2012-12-20 00:08:43 +08:00
|
|
|
extern void intel_crtc_restore_mode(struct drm_crtc *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-08 06:24:08 +08:00
|
|
|
extern void intel_crtc_load_lut(struct drm_crtc *crtc);
|
drm/i915: convert dpms functions of dvo/sdvo/crt
Yeah, big patch but I couldn't come up with a neat idea of how to
split it up further, that wouldn't break dpms on cloned configs
somehow. But the changes in dvo/sdvo/crt are all pretty much
orthonogal, so it's not too bad a patch.
These are the only encoders that support cloning, which requires a few
special changes compared to the previous patches.
- Compute the desired state of the display pipe by walking all
connected encoders and checking whether any has active connectors.
To make this clearer, drop the old mode parameter to the crtc dpms
function and rename it to intel_crtc_update_dpms.
- There's the curious case of intel_crtc->dpms_mode. With the previous
patches to remove the overlay pipe A code and to rework the load
detect pipe code, the big users are gone. We still keep it to avoid
enabling the pipe twice, but we duplicate this logic with
crtc->active, too. Still, leave this for now and just push a fake
dpms mode into it that reflects the state of the display pipe.
Changes in the encoder dpms functions:
- We clamp the dpms state to the supported range right away. This is
escpecially important for the VGA outputs, where only older hw
supports the intermediate states. This (and the crt->adpa_reg patch)
allows us to unify the crt dpms code again between all variants
(gmch, vlv and pch).
- We only enable/disable the output for dvo/sdvo and leave the encoder
running. The encoder will be disabled/enabled when we switch the
state of the entire output pipeline (which will happen right away
for non-cloned setups). This way the duplication is reduced and
strange interaction when disabling output ports at the wrong time
avoided.
The dpms code for all three types of connectors contains a bit of
duplicated logic, but I think keeping these special cases separate is
simpler: CRT is the only one that hanldes intermediate dpms state
(which requires extra logic to enable/disable things in the right
order), and introducing some abstraction just to share the code
between dvo and sdvo smells like overkill. We can do that once someone
bothers to implement cloning for the more modern outputs. But I doubt
that this will ever happen.
v2: s/crtc/crt/_set_dpms, noticed by Paulo Zanoni.
Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-Off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
2012-07-02 04:42:24 +08:00
|
|
|
extern void intel_crtc_update_dpms(struct drm_crtc *crtc);
|
2010-08-04 20:50:23 +08:00
|
|
|
extern void intel_encoder_destroy(struct drm_encoder *encoder);
|
2012-06-30 14:59:56 +08:00
|
|
|
extern void intel_encoder_dpms(struct intel_encoder *encoder, int mode);
|
2012-07-09 01:41:43 +08:00
|
|
|
extern bool intel_encoder_check_is_cloned(struct intel_encoder *encoder);
|
2012-06-30 14:59:56 +08:00
|
|
|
extern void intel_connector_dpms(struct drm_connector *, int mode);
|
2012-07-02 19:10:34 +08:00
|
|
|
extern bool intel_connector_get_hw_state(struct intel_connector *connector);
|
2012-08-31 23:37:33 +08:00
|
|
|
extern void intel_modeset_check_state(struct drm_device *dev);
|
2013-03-27 00:25:43 +08:00
|
|
|
extern void intel_plane_restore(struct drm_plane *plane);
|
2012-08-31 23:37:33 +08:00
|
|
|
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 06:24:08 +08:00
|
|
|
|
2010-09-09 23:20:55 +08:00
|
|
|
static inline struct intel_encoder *intel_attached_encoder(struct drm_connector *connector)
|
|
|
|
{
|
|
|
|
return to_intel_connector(connector)->encoder;
|
|
|
|
}
|
|
|
|
|
2012-10-16 02:51:29 +08:00
|
|
|
static inline struct intel_dp *enc_to_intel_dp(struct drm_encoder *encoder)
|
|
|
|
{
|
2012-10-27 05:05:46 +08:00
|
|
|
struct intel_digital_port *intel_dig_port =
|
|
|
|
container_of(encoder, struct intel_digital_port, base.base);
|
|
|
|
return &intel_dig_port->dp;
|
|
|
|
}
|
|
|
|
|
|
|
|
static inline struct intel_digital_port *
|
|
|
|
enc_to_dig_port(struct drm_encoder *encoder)
|
|
|
|
{
|
|
|
|
return container_of(encoder, struct intel_digital_port, base.base);
|
|
|
|
}
|
|
|
|
|
|
|
|
static inline struct intel_digital_port *
|
|
|
|
dp_to_dig_port(struct intel_dp *intel_dp)
|
|
|
|
{
|
|
|
|
return container_of(intel_dp, struct intel_digital_port, dp);
|
|
|
|
}
|
|
|
|
|
|
|
|
static inline struct intel_digital_port *
|
|
|
|
hdmi_to_dig_port(struct intel_hdmi *intel_hdmi)
|
|
|
|
{
|
|
|
|
return container_of(intel_hdmi, struct intel_digital_port, hdmi);
|
2012-10-16 02:51:29 +08:00
|
|
|
}
|
|
|
|
|
2012-12-14 00:09:00 +08:00
|
|
|
bool ibx_digital_port_connected(struct drm_i915_private *dev_priv,
|
|
|
|
struct intel_digital_port *port);
|
|
|
|
|
2010-09-09 23:20:55 +08:00
|
|
|
extern void intel_connector_attach_encoder(struct intel_connector *connector,
|
|
|
|
struct intel_encoder *encoder);
|
|
|
|
extern struct drm_encoder *intel_best_encoder(struct drm_connector *connector);
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 06:24:08 +08:00
|
|
|
|
|
|
|
extern struct drm_display_mode *intel_crtc_mode_get(struct drm_device *dev,
|
|
|
|
struct drm_crtc *crtc);
|
2009-04-30 05:43:54 +08:00
|
|
|
int intel_get_pipe_from_crtc_id(struct drm_device *dev, void *data,
|
|
|
|
struct drm_file *file_priv);
|
drm/i915: add TRANSCODER_EDP
Before Haswell we used to have the CPU pipes and the PCH transcoders.
We had the same amount of pipes and transcoders, and there was a 1:1
mapping between them. After Haswell what we used to call CPU pipe was
split into CPU pipe and CPU transcoder. So now we have 3 CPU pipes (A,
B and C), 4 CPU transcoders (A, B, C and EDP) and 1 PCH transcoder
(only used for VGA).
For all the outputs except for EDP we have an 1:1 mapping on the CPU
pipes and CPU transcoders, so if you're using CPU pipe A you have to
use CPU transcoder A. When have an eDP output you have to use
transcoder EDP and you can attach this CPU transcoder to any of the 3
CPU pipes. When using VGA you need to select a pair of matching CPU
pipes/transcoders (A/A, B/B, C/C) and you also need to enable/use the
PCH transcoder.
For now we're just creating the cpu_transcoder definitions and setting
cpu_transcoder to TRANSCODER_EDP on DDI eDP code, but none of the
registers was ported to use transcoder instead of pipe. The goal is to
keep the code backwards-compatible since on all cases except when
using eDP we must have pipe == cpu_transcoder.
V2: Comment the haswell_crtc_off chunk, suggested by Damien Lespiau
and Daniel Vetter.
We currently need the haswell_crtc_off chunk because TRANSCODER_EDP
can be used by any CRTC, so when you stop using it you have to stop
saying you're using it, otherwise you may have at some point 2 CRTCs
claiming they're using TRANSCODER_EDP (a disabled CRTC and an enabled
one), then the HW state readout code will get completely confused.
In other words:
Imagine the following case:
xrandr --output eDP1 --auto --crtc 0
xrandr --output eDP1 --off
xrandr --output eDP1 --auto --crtc 2
After the last command you could get a "pipe A assertion failure
(expected off, current on)" because CRTC 0 still claims it's using
TRANSCODER_EDP, so the HW state readout function will read it
(through PIPECONF) and expect it to be off, when it's actually on
because it's being used by CRTC 2.
So when we make "intel_crtc->cpu_transcoder = intel_crtc->pipe" we
make sure we're pointing to our own original CRTC which is certainly
not used by any other CRTC.
Signed-off-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
Reviewed-by: Damien Lespiau <damien.lespiau@intel.com>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
2012-10-25 01:59:34 +08:00
|
|
|
extern enum transcoder
|
|
|
|
intel_pipe_to_cpu_transcoder(struct drm_i915_private *dev_priv,
|
|
|
|
enum pipe pipe);
|
2010-08-19 04:20:54 +08:00
|
|
|
extern void intel_wait_for_vblank(struct drm_device *dev, int pipe);
|
2010-10-03 17:56:11 +08:00
|
|
|
extern void intel_wait_for_pipe_off(struct drm_device *dev, int pipe);
|
2012-11-29 21:29:32 +08:00
|
|
|
extern int ironlake_get_lanes_required(int target_clock, int link_bw, int bpp);
|
2011-04-20 06:18:09 +08:00
|
|
|
|
|
|
|
struct intel_load_detect_pipe {
|
2011-04-19 15:36:26 +08:00
|
|
|
struct drm_framebuffer *release_fb;
|
2011-04-20 06:18:09 +08:00
|
|
|
bool load_detect_temp;
|
|
|
|
int dpms_mode;
|
|
|
|
};
|
2012-08-13 03:20:10 +08:00
|
|
|
extern bool intel_get_load_detect_pipe(struct drm_connector *connector,
|
2011-04-20 06:10:58 +08:00
|
|
|
struct drm_display_mode *mode,
|
2011-04-20 06:18:09 +08:00
|
|
|
struct intel_load_detect_pipe *old);
|
2012-08-13 03:20:10 +08:00
|
|
|
extern void intel_release_load_detect_pipe(struct drm_connector *connector,
|
2011-04-20 06:18:09 +08:00
|
|
|
struct intel_load_detect_pipe *old);
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 06:24:08 +08:00
|
|
|
|
|
|
|
extern void intelfb_restore(void);
|
|
|
|
extern void intel_crtc_fb_gamma_set(struct drm_crtc *crtc, u16 red, u16 green,
|
|
|
|
u16 blue, int regno);
|
2009-10-06 11:54:01 +08:00
|
|
|
extern void intel_crtc_fb_gamma_get(struct drm_crtc *crtc, u16 *red, u16 *green,
|
|
|
|
u16 *blue, int regno);
|
2010-12-06 01:27:06 +08:00
|
|
|
extern void intel_enable_clock_gating(struct drm_device *dev);
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 06:24:08 +08:00
|
|
|
|
2010-07-24 06:32:05 +08:00
|
|
|
extern int intel_pin_and_fence_fb_obj(struct drm_device *dev,
|
2010-11-09 03:18:58 +08:00
|
|
|
struct drm_i915_gem_object *obj,
|
2010-11-12 21:42:53 +08:00
|
|
|
struct intel_ring_buffer *pipelined);
|
2011-12-14 20:57:08 +08:00
|
|
|
extern void intel_unpin_fb_obj(struct drm_i915_gem_object *obj);
|
2010-07-24 06:32:05 +08:00
|
|
|
|
2010-03-30 13:34:13 +08:00
|
|
|
extern int intel_framebuffer_init(struct drm_device *dev,
|
|
|
|
struct intel_framebuffer *ifb,
|
2011-11-15 06:51:28 +08:00
|
|
|
struct drm_mode_fb_cmd2 *mode_cmd,
|
2010-11-09 03:18:58 +08:00
|
|
|
struct drm_i915_gem_object *obj);
|
2010-03-30 13:34:13 +08:00
|
|
|
extern int intel_fbdev_init(struct drm_device *dev);
|
2012-12-11 21:05:07 +08:00
|
|
|
extern void intel_fbdev_initial_config(struct drm_device *dev);
|
2010-03-30 13:34:13 +08:00
|
|
|
extern void intel_fbdev_fini(struct drm_device *dev);
|
2012-03-28 17:48:49 +08:00
|
|
|
extern void intel_fbdev_set_suspend(struct drm_device *dev, int state);
|
2009-11-19 00:25:18 +08:00
|
|
|
extern void intel_prepare_page_flip(struct drm_device *dev, int plane);
|
|
|
|
extern void intel_finish_page_flip(struct drm_device *dev, int pipe);
|
2010-03-27 01:35:20 +08:00
|
|
|
extern void intel_finish_page_flip_plane(struct drm_device *dev, int plane);
|
2009-11-19 00:25:18 +08:00
|
|
|
|
2009-09-16 04:57:34 +08:00
|
|
|
extern void intel_setup_overlay(struct drm_device *dev);
|
|
|
|
extern void intel_cleanup_overlay(struct drm_device *dev);
|
2011-02-21 22:43:56 +08:00
|
|
|
extern int intel_overlay_switch_off(struct intel_overlay *overlay);
|
2009-09-16 04:57:34 +08:00
|
|
|
extern int intel_overlay_put_image(struct drm_device *dev, void *data,
|
|
|
|
struct drm_file *file_priv);
|
|
|
|
extern int intel_overlay_attrs(struct drm_device *dev, void *data,
|
|
|
|
struct drm_file *file_priv);
|
2010-03-30 13:34:18 +08:00
|
|
|
|
2010-05-07 14:42:51 +08:00
|
|
|
extern void intel_fb_output_poll_changed(struct drm_device *dev);
|
2011-04-22 05:18:32 +08:00
|
|
|
extern void intel_fb_restore_mode(struct drm_device *dev);
|
2011-05-12 00:49:31 +08:00
|
|
|
|
2011-12-14 05:19:38 +08:00
|
|
|
extern void assert_pipe(struct drm_i915_private *dev_priv, enum pipe pipe,
|
|
|
|
bool state);
|
|
|
|
#define assert_pipe_enabled(d, p) assert_pipe(d, p, true)
|
|
|
|
#define assert_pipe_disabled(d, p) assert_pipe(d, p, false)
|
|
|
|
|
2011-05-12 00:49:31 +08:00
|
|
|
extern void intel_init_clock_gating(struct drm_device *dev);
|
drm/i915: pass ELD to HDMI/DP audio driver
Add ELD support for Intel Eaglelake, IbexPeak/Ironlake,
SandyBridge/CougarPoint and IvyBridge/PantherPoint chips.
ELD (EDID-Like Data) describes to the HDMI/DP audio driver the audio
capabilities of the plugged monitor. It's built and passed to audio
driver in 2 steps:
(1) at get_modes time, parse EDID and save ELD to drm_connector.eld[]
(2) at mode_set time, write drm_connector.eld[] to the Transcoder's hw
ELD buffer and set the ELD_valid bit to inform HDMI/DP audio driver
This patch is tested OK on G45/HDMI, IbexPeak/HDMI and IvyBridge/HDMI+DP.
Test scheme: plug in the HDMI/DP monitor, and run
cat /proc/asound/card0/eld*
to check if the monitor name, HDMI/DP type, etc. show up correctly.
Minor imperfection: the GEN5_AUD_CNTL_ST/DIP_Port_Select field always
reads 0 (reserved). Without knowing the port number, I worked it around
by setting the ELD_valid bit for ALL the three ports. It's tested to not
be a problem, because the audio driver will find invalid ELD data and
hence rightfully abort, even when it sees the ELD_valid indicator.
Thanks to Zhenyu and Pierre-Louis for a lot of valuable help and testing.
CC: Zhao Yakui <yakui.zhao@intel.com>
CC: Wang Zhenyu <zhenyu.z.wang@intel.com>
CC: Jeremy Bush <contractfrombelow@gmail.com>
CC: Christopher White <c.white@pulseforce.com>
CC: Pierre-Louis Bossart <pierre-louis.bossart@intel.com>
CC: Paul Menzel <paulepanter@users.sourceforge.net>
Signed-off-by: Wu Fengguang <fengguang.wu@intel.com>
Signed-off-by: Keith Packard <keithp@keithp.com>
2011-09-05 14:25:34 +08:00
|
|
|
extern void intel_write_eld(struct drm_encoder *encoder,
|
|
|
|
struct drm_display_mode *mode);
|
2011-10-12 01:43:02 +08:00
|
|
|
extern void intel_cpt_verify_modeset(struct drm_device *dev, int pipe);
|
drm/i915: clear up the fdi/dp set_m_n confusion
There's a rather decent confusion going on around transcoder m_n
values. So let's clarify:
- All dp encoders need this, either on the pch transcoder if it's a
pch port, or on the cpu transcoder/pipe if it's a cpu port.
- fdi links need to have the right m_n values for the fdi link set in
the cpu transcoder.
To handle the pch vs transcoder stuff a bit better, extract transcoder
set_m_n helpers. To make them simpler, set intel_crtc->cpu_transcoder
als in ironlake_crtc_mode_set, so that gen5+ (where the cpu m_n
registers are all at the same offset) can use it.
Haswell modeset is decently confused about dp vs. edp vs. fdi. dp vs.
edp works exactly the same as dp (since there's no pch dp any more),
so use that as a check. And only set up the fdi m_n values if we
really have a pch encoder present (which means we have a VGA encoder).
On ilk+ we've called ironlake_set_m_n both for cpu_edp and for pch
encoders. Now that dp_set_m_n handles all dp links (thanks to the
pch encoder check), we can ditch the cpu_edp stuff from the
fdi_set_m_n function.
Since the dp_m_n values are not readily available, we need to
carefully coax the edp values out of the encoder. Hence we can't (yet)
kill this superflous complexity.
v2: Rebase on top of the ivb fdi B/C check patch - we need to properly
clear intel_crtc->fdi_lane, otherwise those checks will misfire.
v3: Rebased on top of a s/IS_HASWELL/HAS_DDI/ patch from Paulo Zanoni.
v4: Drop the addition of has_dp_encoder, it's in the wrong patch (Jesse).
Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
2013-04-03 05:38:10 +08:00
|
|
|
extern void intel_cpu_transcoder_set_m_n(struct intel_crtc *crtc,
|
|
|
|
struct intel_link_m_n *m_n);
|
|
|
|
extern void intel_pch_transcoder_set_m_n(struct intel_crtc *crtc,
|
|
|
|
struct intel_link_m_n *m_n);
|
2012-05-10 02:37:20 +08:00
|
|
|
extern void intel_prepare_ddi(struct drm_device *dev);
|
2012-05-10 02:37:21 +08:00
|
|
|
extern void hsw_fdi_link_train(struct drm_crtc *crtc);
|
2012-05-10 02:37:27 +08:00
|
|
|
extern void intel_ddi_init(struct drm_device *dev, enum port port);
|
2011-10-12 01:43:02 +08:00
|
|
|
|
2011-12-14 05:19:38 +08:00
|
|
|
/* For use by IVB LP watermark workaround in intel_sprite.c */
|
2012-04-15 04:56:08 +08:00
|
|
|
extern void intel_update_watermarks(struct drm_device *dev);
|
2011-12-14 05:19:38 +08:00
|
|
|
extern void intel_update_sprite_watermarks(struct drm_device *dev, int pipe,
|
|
|
|
uint32_t sprite_width,
|
|
|
|
int pixel_size);
|
2012-05-10 02:37:24 +08:00
|
|
|
extern void intel_update_linetime_watermarks(struct drm_device *dev, int pipe,
|
|
|
|
struct drm_display_mode *mode);
|
2012-01-04 00:05:39 +08:00
|
|
|
|
2013-02-22 04:04:31 +08:00
|
|
|
extern unsigned long intel_gen4_compute_page_offset(int *x, int *y,
|
|
|
|
unsigned int tiling_mode,
|
|
|
|
unsigned int bpp,
|
|
|
|
unsigned int pitch);
|
2012-10-27 01:20:12 +08:00
|
|
|
|
2012-01-04 00:05:39 +08:00
|
|
|
extern int intel_sprite_set_colorkey(struct drm_device *dev, void *data,
|
|
|
|
struct drm_file *file_priv);
|
|
|
|
extern int intel_sprite_get_colorkey(struct drm_device *dev, void *data,
|
|
|
|
struct drm_file *file_priv);
|
|
|
|
|
2012-03-29 04:39:25 +08:00
|
|
|
extern u32 intel_dpio_read(struct drm_i915_private *dev_priv, int reg);
|
|
|
|
|
2012-04-17 09:20:34 +08:00
|
|
|
/* Power-related functions, located in intel_pm.c */
|
2012-04-19 02:29:26 +08:00
|
|
|
extern void intel_init_pm(struct drm_device *dev);
|
2012-04-17 09:20:34 +08:00
|
|
|
/* FBC */
|
|
|
|
extern bool intel_fbc_enabled(struct drm_device *dev);
|
|
|
|
extern void intel_enable_fbc(struct drm_crtc *crtc, unsigned long interval);
|
|
|
|
extern void intel_update_fbc(struct drm_device *dev);
|
2012-04-27 05:28:12 +08:00
|
|
|
/* IPS */
|
|
|
|
extern void intel_gpu_ips_init(struct drm_i915_private *dev_priv);
|
|
|
|
extern void intel_gpu_ips_teardown(void);
|
2012-04-17 09:20:34 +08:00
|
|
|
|
2013-03-23 01:14:13 +08:00
|
|
|
extern bool intel_using_power_well(struct drm_device *dev);
|
drm/i915: fix intel_init_power_wells
The current code was wrong in many different ways, so this is a full
rewrite. We don't have "different power wells for different parts of
the GPU", we have a single power well, but we have multiple registers
that can be used to request enabling/disabling the power well. So
let's be a good citizen and only use the register we're suppose to
use, except when we're loading the driver, where we clear the request
made by the BIOS.
If any of the registers is requesting the power well to be enabled, it
will be enabled. If none of the registers is requesting the power well
to be enabled, it will be disabled.
For now we're just forcing the power well to be enabled, but in the
next commits we'll change this.
V2:
- Remove debug messages that could be misleading due to possible
race conditions with KVMr, Debug and BIOS.
- Don't wait on disabling: after a conversaion with a hardware
engineer we discovered that the "restriction" on bit 31 is just
for the "enable" case, and we don't even need to wait on the
"disable" case.
Signed-off-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
2013-01-26 02:59:11 +08:00
|
|
|
extern void intel_init_power_well(struct drm_device *dev);
|
2013-01-26 02:59:15 +08:00
|
|
|
extern void intel_set_power_well(struct drm_device *dev, bool enable);
|
2012-06-24 22:42:32 +08:00
|
|
|
extern void intel_enable_gt_powersave(struct drm_device *dev);
|
|
|
|
extern void intel_disable_gt_powersave(struct drm_device *dev);
|
2012-07-02 22:51:11 +08:00
|
|
|
extern void gen6_gt_check_fifodbg(struct drm_i915_private *dev_priv);
|
2012-06-30 05:32:16 +08:00
|
|
|
extern void ironlake_teardown_rc6(struct drm_device *dev);
|
2012-04-27 05:28:13 +08:00
|
|
|
|
2012-07-02 19:27:29 +08:00
|
|
|
extern bool intel_ddi_get_hw_state(struct intel_encoder *encoder,
|
|
|
|
enum pipe *pipe);
|
2012-10-24 04:30:05 +08:00
|
|
|
extern int intel_ddi_get_cdclk_freq(struct drm_i915_private *dev_priv);
|
2012-10-05 23:05:52 +08:00
|
|
|
extern void intel_ddi_pll_init(struct drm_device *dev);
|
2013-03-07 23:30:27 +08:00
|
|
|
extern void intel_ddi_enable_transcoder_func(struct drm_crtc *crtc);
|
2012-10-25 02:06:19 +08:00
|
|
|
extern void intel_ddi_disable_transcoder_func(struct drm_i915_private *dev_priv,
|
|
|
|
enum transcoder cpu_transcoder);
|
2012-10-05 23:05:54 +08:00
|
|
|
extern void intel_ddi_enable_pipe_clock(struct intel_crtc *intel_crtc);
|
|
|
|
extern void intel_ddi_disable_pipe_clock(struct intel_crtc *intel_crtc);
|
2012-10-05 23:05:58 +08:00
|
|
|
extern void intel_ddi_setup_hw_pll_state(struct drm_device *dev);
|
|
|
|
extern bool intel_ddi_pll_mode_set(struct drm_crtc *crtc, int clock);
|
|
|
|
extern void intel_ddi_put_crtc_pll(struct drm_crtc *crtc);
|
2012-10-16 02:51:30 +08:00
|
|
|
extern void intel_ddi_set_pipe_settings(struct drm_crtc *crtc);
|
2012-10-16 02:51:41 +08:00
|
|
|
extern void intel_ddi_prepare_link_retrain(struct drm_encoder *encoder);
|
2012-11-02 07:05:05 +08:00
|
|
|
extern bool
|
|
|
|
intel_ddi_connector_get_hw_state(struct intel_connector *intel_connector);
|
|
|
|
extern void intel_ddi_fdi_disable(struct drm_crtc *crtc);
|
2012-05-10 02:37:31 +08:00
|
|
|
|
2013-02-19 01:08:49 +08:00
|
|
|
extern void intel_display_handle_reset(struct drm_device *dev);
|
|
|
|
|
DRM: i915: add mode setting support
This commit adds i915 driver support for the DRM mode setting APIs.
Currently, VGA, LVDS, SDVO DVI & VGA, TV and DVO LVDS outputs are
supported. HDMI, DisplayPort and additional SDVO output support will
follow.
Support for the mode setting code is controlled by the new 'modeset'
module option. A new config option, CONFIG_DRM_I915_KMS controls the
default behavior, and whether a PCI ID list is built into the module for
use by user level module utilities.
Note that if mode setting is enabled, user level drivers that access
display registers directly or that don't use the kernel graphics memory
manager will likely corrupt kernel graphics memory, disrupt output
configuration (possibly leading to hangs and/or blank displays), and
prevent panic/oops messages from appearing. So use caution when
enabling this code; be sure your user level code supports the new
interfaces.
A new SysRq key, 'g', provides emergency support for switching back to
the kernel's framebuffer console; which is useful for testing.
Co-authors: Dave Airlie <airlied@linux.ie>, Hong Liu <hong.liu@intel.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2008-11-08 06:24:08 +08:00
|
|
|
#endif /* __INTEL_DRV_H__ */
|