Haswell v4
Subsystems (3)
cover Haswell v4
Hi,
This patch aims at addressing all the bikesheds I had for the past ones, and re-structure the patches in a more logical way.
The major changes are the introduction of the intel_ddi.c module, cleanup of the debugging patches, and addition of functions to simplify digital outputs handling for DDI connections.
As major areas that will still receive attention in the next patches are: the iCLKIP / WRPLL table rework into a function, proper Haswell DIP support, DP support and digital outputs detection on hotplug (e.g., detection of DP and HDMI according to what's on the other end of the DDI port). But as most of those features are being worked in parallel, I thought on sending this patch bomb so it could be used as base for others.
So please, bikeshed and comment :).
Eugeni Dodonov (24):
drm/i915: add Haswell DIP controls registers drm/i915: support infoframes on Haswell
drm/i915: add support for SBI ops
drm/i915: calculate same watermarks on Haswell as on Ivy Bridge drm/i915: reuse Ivybridge interrupts code for Haswell drm/i915: properly check for pipe count
drm/i915: show unknown sdvox registers on hdmi init drm/i915: do not use fdi_normal_train on haswell drm/i915: detect PCH encoders on Haswell
drm/i915: enable power wells on haswell init drm/i915: program WM_LINETIME on Haswell
drm/i915: add LPT PCH checks
drm/i915: handle DDI-related assertions
drm/i915: account for only one PCH receiver on Haswell drm/i915: initialize DDI buffer translations drm/i915: support DDI training in FDI mode
drm/i915: disable pipe DDI function when disabling pipe drm/i915: program iCLKIP on Lynx Point
drm/i915: detect digital outputs on Haswell
drm/i915: add support for DDI-controlled digital outputs drm/i915: add WR PLL programming table
drm/i915: move HDMI structs to shared location drm/i915: prepare HDMI link for Haswell
drm/i915: hook Haswell devices in place
drivers/char/agp/intel-agp.c | 4 + drivers/gpu/drm/i915/Makefile | 1 + drivers/gpu/drm/i915/i915_drv.c | 7 + drivers/gpu/drm/i915/i915_irq.c | 7 +- drivers/gpu/drm/i915/i915_reg.h | 16 + drivers/gpu/drm/i915/intel_ddi.c | 765 ++++++++++++++++++++++++++++++++++ drivers/gpu/drm/i915/intel_display.c | 524 +++++++++++++++++++++-- drivers/gpu/drm/i915/intel_drv.h | 26 +- drivers/gpu/drm/i915/intel_hdmi.c | 85 +++- drivers/gpu/drm/i915/intel_pm.c | 50 ++- 10 files changed, 1432 insertions(+), 53 deletions(-) create mode 100644 drivers/gpu/drm/i915/intel_ddi.c
Signature · 1 line
1.7.10
PATCH 1/24 drm/i915: add Haswell DIP controls registers
Haswell has different DIP control registers and offsets.
--- drivers/gpu/drm/i915/i915_reg.h | 16 ++++++++++++++++ 1 file changed, 16 insertions(+)
drivers/gpu/drm/i915/i915_reg.h +16 -0
@@ -3518,6 +3518,22 @@#define VLV_TVIDEO_DIP_GCP (pipe) \ _PIPE(pipe, VLV_VIDEO_DIP_GDCP_PAYLOAD_A, VLV_VIDEO_DIP_GDCP_PAYLOAD_B) +/* Haswell DIP controls */ +#define HSW_VIDEO_DIP_CTL_A 0x60200 +#define HSW_VIDEO_DIP_AVI_DATA_A 0x60220 +#define HSW_VIDEO_DIP_GCP_A 0x60210 + +#define HSW_VIDEO_DIP_CTL_B 0x61200 +#define HSW_VIDEO_DIP_AVI_DATA_B 0x61220 +#define HSW_VIDEO_DIP_GCP_B 0x61210 + +#define HSW_TVIDEO_DIP_CTL (pipe) \ + _PIPE(pipe, HSW_VIDEO_DIP_CTL_A, HSW_VIDEO_DIP_CTL_B) +#define HSW_TVIDEO_DIP_AVI_DATA (pipe) \ + _PIPE(pipe, HSW_VIDEO_DIP_AVI_DATA_A, HSW_VIDEO_DIP_AVI_DATA_B) +#define HSW_TVIDEO_DIP_GCP (pipe) \ + _PIPE(pipe, HSW_VIDEO_DIP_GCP_A, HSW_VIDEO_DIP_GCP_B) +#define _TRANS_HTOTAL_B 0xe1000#define _TRANS_HBLANK_B 0xe1004#define _TRANS_HSYNC_B 0xe1008
Signature · 1 line
1.7.10
Re: [PATCH 01/24] drm/i915: add Haswell DIP controls registers
Quoted 3 lines · Eugeni Dodonov
Haswell has different DIP control registers and offsets.
Signed-off-by Eugeni Dodonov <[email protected]>
Afaict hsw has a dip reg for every type of info frame, whereas older machines have one dip reg and a switch in the control reg. Can you please the definitions for the other regs here, too, and a big yelling FIXME comment in the second patch saying that this is a hack and Paulo needs to fix things up?
-Daniel
Quoted 38 lines
--- drivers/gpu/drm/i915/i915_reg.h | 16 ++++++++++++++++ 1 file changed, 16 insertions(+)drivers/gpu/drm/i915/i915_reg.h +16
-0@@ -3518,6 +3518,22 @@#define VLV_TVIDEO_DIP_GCP (pipe) \ _PIPE(pipe, VLV_VIDEO_DIP_GDCP_PAYLOAD_A, VLV_VIDEO_DIP_GDCP_PAYLOAD_B) +/* Haswell DIP controls */ +#define HSW_VIDEO_DIP_CTL_A 0x60200 +#define HSW_VIDEO_DIP_AVI_DATA_A 0x60220 +#define HSW_VIDEO_DIP_GCP_A 0x60210 + +#define HSW_VIDEO_DIP_CTL_B 0x61200 +#define HSW_VIDEO_DIP_AVI_DATA_B 0x61220 +#define HSW_VIDEO_DIP_GCP_B 0x61210 + +#define HSW_TVIDEO_DIP_CTL (pipe) \ + _PIPE(pipe, HSW_VIDEO_DIP_CTL_A, HSW_VIDEO_DIP_CTL_B) +#define HSW_TVIDEO_DIP_AVI_DATA (pipe) \ + _PIPE(pipe, HSW_VIDEO_DIP_AVI_DATA_A, HSW_VIDEO_DIP_AVI_DATA_B) +#define HSW_TVIDEO_DIP_GCP (pipe) \ + _PIPE(pipe, HSW_VIDEO_DIP_GCP_A, HSW_VIDEO_DIP_GCP_B) +#define _TRANS_HTOTAL_B 0xe1000#define _TRANS_HBLANK_B 0xe1004#define _TRANS_HSYNC_B 0xe1008Signature · 6 lines
1.7.10 _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Signature · 3 lines
Daniel Vetter Mail: [email protected] Mobile: +41 (0)79 365 57 48
Re: [PATCH 01/24] drm/i915: add Haswell DIP controls registers
Quoted 36 lines · On Thu, 26 Apr 2012 21:18:52 +0200 Daniel Vetter <[email protected]> wrote:
Quoted 3 lines · Eugeni Dodonov
Haswell has different DIP control registers and offsets.
Signed-off-by Eugeni Dodonov <[email protected]>Afaict hsw has a dip reg for every type of info frame, whereas older machines have one dip reg and a switch in the control reg. Can you please the definitions for the other regs here, too, and a big yelling FIXME comment in the second patch saying that this is a hack and Paulo needs to fix things up?
-DanielQuoted 25 lines
--- drivers/gpu/drm/i915/i915_reg.h | 16 ++++++++++++++++ 1 file changed, 16 insertions(+)drivers/gpu/drm/i915/i915_reg.h +13
-0@@ -3518,6 +3518,22 @@#define VLV_TVIDEO_DIP_GCP (pipe) \ _PIPE(pipe, VLV_VIDEO_DIP_GDCP_PAYLOAD_A, VLV_VIDEO_DIP_GDCP_PAYLOAD_B) +/* Haswell DIP controls */ +#define HSW_VIDEO_DIP_CTL_A 0x60200 +#define HSW_VIDEO_DIP_AVI_DATA_A 0x60220 +#define HSW_VIDEO_DIP_GCP_A 0x60210 + +#define HSW_VIDEO_DIP_CTL_B 0x61200 +#define HSW_VIDEO_DIP_AVI_DATA_B 0x61220 +#define HSW_VIDEO_DIP_GCP_B 0x61210 + +#define HSW_TVIDEO_DIP_CTL (pipe) \ + _PIPE(pipe, HSW_VIDEO_DIP_CTL_A, HSW_VIDEO_DIP_CTL_B) +#define HSW_TVIDEO_DIP_AVI_DATA (pipe) \ + _PIPE(pipe, HSW_VIDEO_DIP_AVI_DATA_A, HSW_VIDEO_DIP_AVI_DATA_B)
Quoted 8 lines
Quoted 8 lines
drivers/gpu/drm/i915/i915_reg.h +3
-0+#define HSW_TVIDEO_DIP_GCP (pipe) \ + _PIPE(pipe, HSW_VIDEO_DIP_GCP_A, HSW_VIDEO_DIP_GCP_B) +#define _TRANS_HTOTAL_B 0xe1000#define _TRANS_HBLANK_B 0xe1004#define _TRANS_HSYNC_B 0xe1008Signature · 1 line
1.7.10
I'd just roll this patch into the patch that adds the HSW specific infoframe functions...
Signature · 1 line
Jesse Barnes, Intel Open Source Technology Center
PATCH 1/24 drm/i915: add Haswell DIP controls registers
In reply to Eugeni DodonovHaswell has different DIP control registers and offsets.
v2: also add the new DIP frame registers, as suggested by Daniel Vetter.
--- drivers/gpu/drm/i915/i915_reg.h | 34 ++++++++++++++++++++++++++++++++++ 1 file changed, 34 insertions(+)
drivers/gpu/drm/i915/i915_reg.h +34 -0
@@ -3518,6 +3518,40 @@#define VLV_TVIDEO_DIP_GCP (pipe) \ _PIPE(pipe, VLV_VIDEO_DIP_GDCP_PAYLOAD_A, VLV_VIDEO_DIP_GDCP_PAYLOAD_B) +/* Haswell DIP controls */ +#define HSW_VIDEO_DIP_CTL_A 0x60200 +#define HSW_VIDEO_DIP_AVI_DATA_A 0x60220 +#define HSW_VIDEO_DIP_VS_DATA_A 0x60260 +#define HSW_VIDEO_DIP_SPD_DATA_A 0x602A0 +#define HSW_VIDEO_DIP_GMP_DATA_A 0x602E0 +#define HSW_VIDEO_DIP_VSC_DATA_A 0x60320 +#define HSW_VIDEO_DIP_AVI_ECC_A 0x60240 +#define HSW_VIDEO_DIP_VS_ECC_A 0x60280 +#define HSW_VIDEO_DIP_SPD_ECC_A 0x602C0 +#define HSW_VIDEO_DIP_GMP_ECC_A 0x60300 +#define HSW_VIDEO_DIP_VSC_ECC_A 0x60344 +#define HSW_VIDEO_DIP_GCP_A 0x60210 + +#define HSW_VIDEO_DIP_CTL_B 0x61200 +#define HSW_VIDEO_DIP_AVI_DATA_B 0x61220 +#define HSW_VIDEO_DIP_VS_DATA_A 0x61260 +#define HSW_VIDEO_DIP_SPD_DATA_B 0x612A0 +#define HSW_VIDEO_DIP_GMP_DATA_B 0x612E0 +#define HSW_VIDEO_DIP_VSC_DATA_B 0x61320 +#define HSW_VIDEO_DIP_BVI_ECC_B 0x61240 +#define HSW_VIDEO_DIP_VS_ECC_B 0x61280 +#define HSW_VIDEO_DIP_SPD_ECC_B 0x612C0 +#define HSW_VIDEO_DIP_GMP_ECC_B 0x61300 +#define HSW_VIDEO_DIP_VSC_ECC_B 0x61344 +#define HSW_VIDEO_DIP_GCP_B 0x61210 + +#define HSW_TVIDEO_DIP_CTL (pipe) \ + _PIPE(pipe, HSW_VIDEO_DIP_CTL_A, HSW_VIDEO_DIP_CTL_B) +#define HSW_TVIDEO_DIP_AVI_DATA (pipe) \ + _PIPE(pipe, HSW_VIDEO_DIP_AVI_DATA_A, HSW_VIDEO_DIP_AVI_DATA_B) +#define HSW_TVIDEO_DIP_GCP (pipe) \ + _PIPE(pipe, HSW_VIDEO_DIP_GCP_A, HSW_VIDEO_DIP_GCP_B) +#define _TRANS_HTOTAL_B 0xe1000#define _TRANS_HBLANK_B 0xe1004#define _TRANS_HSYNC_B 0xe1008
Signature · 1 line
1.7.10
PATCH 2/24 drm/i915: support infoframes on Haswell
Haswell has different DIP registers which we need to use for infoframes, so add proper infrastructure to address that.
v2: add a comment to indicate that full DIP frames support is still not there, as suggested by Daniel Vetter.
--- drivers/gpu/drm/i915/intel_hdmi.c | 37 +++++++++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+)
drivers/gpu/drm/i915/intel_hdmi.c +37 -0
@@ -208,6 +208,36 @@ static void vlv_write_infoframe(struct drm_encoder *encoder,I915_WRITE (reg,VIDEO_DIP_ENABLE | val | flags); } +static void hsw_write_infoframe (struct drm_encoder *encoder, +struct dip_infoframe *frame) +{ +uint32_t *data = (uint32_t *)frame; +struct drm_device *dev = encoder->dev; +struct drm_i915_private *dev_priv = dev->dev_private; +struct drm_crtc *crtc = encoder->crtc; +struct intel_crtc *intel_crtc =to_intel_crtc (crtc); +int reg =HSW_TVIDEO_DIP_CTL (intel_crtc->pipe); +unsigned i, len =DIP_HEADER_SIZE + frame->len; +u32 flags, val =I915_READ (reg); + +intel_wait_for_vblank (dev, intel_crtc->pipe); + + flags =intel_infoframe_index (frame); + + val &= ~(VIDEO_DIP_SELECT_MASK |0xf );/* clear DIP data offset */ + +I915_WRITE (reg,VIDEO_DIP_ENABLE | val | flags); + +for (i =0 ; i < len; i +=4 ) { +I915_WRITE (HSW_TVIDEO_DIP_AVI_DATA (intel_crtc->pipe), *data); + data++; + } + + flags |=intel_infoframe_flags (frame); + +I915_WRITE (reg,VIDEO_DIP_ENABLE | val | flags); +} +static void intel_set_infoframe (struct drm_encoder *encoder,struct dip_infoframe *frame) {
@@ -587,6 +617,13 @@ void intel_hdmi_init(struct drm_device *dev, int sdvox_reg) intel_hdmi->write_infoframe = vlv_write_infoframe;for_each_pipe (i)I915_WRITE (VLV_TVIDEO_DIP_CTL (i),0 ); + }else if (IS_HASWELL (dev)) { +/* FIXME: Haswell has a new set of DIP frame registers, but we are +* just doing the minimal required for HDMI to work at this stage. +*/ + intel_hdmi->write_infoframe = hsw_write_infoframe; +for_each_pipe (i) +I915_WRITE (HSW_TVIDEO_DIP_CTL (i),0 ); }else { intel_hdmi->write_infoframe = ironlake_write_infoframe;for_each_pipe (i)
Signature · 1 line
1.7.10
PATCH 1/24 drm/i915: add Haswell DIP controls registers
Haswell has different DIP control registers and offsets.
v2: also add the new DIP frame registers, as suggested by Daniel Vetter. v2.1: fix a typo in HSW_VIDEO_DIP_VS_DATA name for 2nd register.
--- drivers/gpu/drm/i915/i915_reg.h | 34 ++++++++++++++++++++++++++++++++++ 1 file changed, 34 insertions(+)
drivers/gpu/drm/i915/i915_reg.h +34 -0
@@ -3518,6 +3518,40 @@#define VLV_TVIDEO_DIP_GCP (pipe) \ _PIPE(pipe, VLV_VIDEO_DIP_GDCP_PAYLOAD_A, VLV_VIDEO_DIP_GDCP_PAYLOAD_B) +/* Haswell DIP controls */ +#define HSW_VIDEO_DIP_CTL_A 0x60200 +#define HSW_VIDEO_DIP_AVI_DATA_A 0x60220 +#define HSW_VIDEO_DIP_VS_DATA_A 0x60260 +#define HSW_VIDEO_DIP_SPD_DATA_A 0x602A0 +#define HSW_VIDEO_DIP_GMP_DATA_A 0x602E0 +#define HSW_VIDEO_DIP_VSC_DATA_A 0x60320 +#define HSW_VIDEO_DIP_AVI_ECC_A 0x60240 +#define HSW_VIDEO_DIP_VS_ECC_A 0x60280 +#define HSW_VIDEO_DIP_SPD_ECC_A 0x602C0 +#define HSW_VIDEO_DIP_GMP_ECC_A 0x60300 +#define HSW_VIDEO_DIP_VSC_ECC_A 0x60344 +#define HSW_VIDEO_DIP_GCP_A 0x60210 + +#define HSW_VIDEO_DIP_CTL_B 0x61200 +#define HSW_VIDEO_DIP_AVI_DATA_B 0x61220 +#define HSW_VIDEO_DIP_VS_DATA_B 0x61260 +#define HSW_VIDEO_DIP_SPD_DATA_B 0x612A0 +#define HSW_VIDEO_DIP_GMP_DATA_B 0x612E0 +#define HSW_VIDEO_DIP_VSC_DATA_B 0x61320 +#define HSW_VIDEO_DIP_BVI_ECC_B 0x61240 +#define HSW_VIDEO_DIP_VS_ECC_B 0x61280 +#define HSW_VIDEO_DIP_SPD_ECC_B 0x612C0 +#define HSW_VIDEO_DIP_GMP_ECC_B 0x61300 +#define HSW_VIDEO_DIP_VSC_ECC_B 0x61344 +#define HSW_VIDEO_DIP_GCP_B 0x61210 + +#define HSW_TVIDEO_DIP_CTL (pipe) \ + _PIPE(pipe, HSW_VIDEO_DIP_CTL_A, HSW_VIDEO_DIP_CTL_B) +#define HSW_TVIDEO_DIP_AVI_DATA (pipe) \ + _PIPE(pipe, HSW_VIDEO_DIP_AVI_DATA_A, HSW_VIDEO_DIP_AVI_DATA_B) +#define HSW_TVIDEO_DIP_GCP (pipe) \ + _PIPE(pipe, HSW_VIDEO_DIP_GCP_A, HSW_VIDEO_DIP_GCP_B) +#define _TRANS_HTOTAL_B 0xe1000#define _TRANS_HBLANK_B 0xe1004#define _TRANS_HSYNC_B 0xe1008
Signature · 1 line
1.7.10
Re: [PATCH 01/24] drm/i915: add Haswell DIP controls registers
Quoted 45 lines · On Thu, 26 Apr 2012 16:42:46 -0300 Eugeni Dodonov <[email protected]>…
Haswell has different DIP control registers and offsets.
v2: also add the new DIP frame registers, as suggested by Daniel Vetter. v2.1: fix a typo in
HSW_VIDEO_DIP_VS_DATAname for 2nd register.Signed-off-by Eugeni Dodonov <[email protected]>--- drivers/gpu/drm/i915/i915_reg.h | 34 ++++++++++++++++++++++++++++++++++ 1 file changed, 34 insertions(+)drivers/gpu/drm/i915/i915_reg.h +27
-0@@ -3518,6 +3518,40 @@#define VLV_TVIDEO_DIP_GCP (pipe) \ _PIPE(pipe, VLV_VIDEO_DIP_GDCP_PAYLOAD_A, VLV_VIDEO_DIP_GDCP_PAYLOAD_B) +/* Haswell DIP controls */ +#define HSW_VIDEO_DIP_CTL_A 0x60200 +#define HSW_VIDEO_DIP_AVI_DATA_A 0x60220 +#define HSW_VIDEO_DIP_VS_DATA_A 0x60260 +#define HSW_VIDEO_DIP_SPD_DATA_A 0x602A0 +#define HSW_VIDEO_DIP_GMP_DATA_A 0x602E0 +#define HSW_VIDEO_DIP_VSC_DATA_A 0x60320 +#define HSW_VIDEO_DIP_AVI_ECC_A 0x60240 +#define HSW_VIDEO_DIP_VS_ECC_A 0x60280 +#define HSW_VIDEO_DIP_SPD_ECC_A 0x602C0 +#define HSW_VIDEO_DIP_GMP_ECC_A 0x60300 +#define HSW_VIDEO_DIP_VSC_ECC_A 0x60344 +#define HSW_VIDEO_DIP_GCP_A 0x60210 + +#define HSW_VIDEO_DIP_CTL_B 0x61200 +#define HSW_VIDEO_DIP_AVI_DATA_B 0x61220 +#define HSW_VIDEO_DIP_VS_DATA_B 0x61260 +#define HSW_VIDEO_DIP_SPD_DATA_B 0x612A0 +#define HSW_VIDEO_DIP_GMP_DATA_B 0x612E0 +#define HSW_VIDEO_DIP_VSC_DATA_B 0x61320 +#define HSW_VIDEO_DIP_BVI_ECC_B 0x61240 +#define HSW_VIDEO_DIP_VS_ECC_B 0x61280 +#define HSW_VIDEO_DIP_SPD_ECC_B 0x612C0 +#define HSW_VIDEO_DIP_GMP_ECC_B 0x61300 +#define HSW_VIDEO_DIP_VSC_ECC_B 0x61344 +#define HSW_VIDEO_DIP_GCP_B 0x61210 +
drivers/gpu/drm/i915/i915_reg.h line 3557
Quoted 10 lines
drivers/gpu/drm/i915/i915_reg.h +7
-0+#define HSW_TVIDEO_DIP_CTL (pipe) \ + _PIPE(pipe, HSW_VIDEO_DIP_CTL_A, HSW_VIDEO_DIP_CTL_B) +#define HSW_TVIDEO_DIP_AVI_DATA (pipe) \ + _PIPE(pipe, HSW_VIDEO_DIP_AVI_DATA_A, HSW_VIDEO_DIP_AVI_DATA_B) +#define HSW_TVIDEO_DIP_GCP (pipe) \ + _PIPE(pipe, HSW_VIDEO_DIP_GCP_A, HSW_VIDEO_DIP_GCP_B) +#define _TRANS_HTOTAL_B 0xe1000#define _TRANS_HBLANK_B 0xe1004#define _TRANS_HSYNC_B 0xe1008
Offsets look good, I'd just add a switch statement to the infoframe write function so we write the correct data regs...
Signature · 1 line
Jesse Barnes, Intel Open Source Technology Center
PATCH 2/24 drm/i915: support infoframes on Haswell
In reply to Eugeni DodonovHaswell has different DIP registers which we need to use for infoframes, so add proper infrastructure to address that.
--- drivers/gpu/drm/i915/intel_hdmi.c | 34 ++++++++++++++++++++++++++++++++++ 1 file changed, 34 insertions(+)
drivers/gpu/drm/i915/intel_hdmi.c +34 -0
@@ -208,6 +208,36 @@ static void vlv_write_infoframe(struct drm_encoder *encoder,I915_WRITE (reg,VIDEO_DIP_ENABLE | val | flags); } +static void hsw_write_infoframe (struct drm_encoder *encoder, +struct dip_infoframe *frame) +{ +uint32_t *data = (uint32_t *)frame; +struct drm_device *dev = encoder->dev; +struct drm_i915_private *dev_priv = dev->dev_private; +struct drm_crtc *crtc = encoder->crtc; +struct intel_crtc *intel_crtc =to_intel_crtc (crtc); +int reg =HSW_TVIDEO_DIP_CTL (intel_crtc->pipe); +unsigned i, len =DIP_HEADER_SIZE + frame->len; +u32 flags, val =I915_READ (reg); + +intel_wait_for_vblank (dev, intel_crtc->pipe); + + flags =intel_infoframe_index (frame); + + val &= ~(VIDEO_DIP_SELECT_MASK |0xf );/* clear DIP data offset */ + +I915_WRITE (reg,VIDEO_DIP_ENABLE | val | flags); + +for (i =0 ; i < len; i +=4 ) { +I915_WRITE (HSW_TVIDEO_DIP_AVI_DATA (intel_crtc->pipe), *data); + data++; + } + + flags |=intel_infoframe_flags (frame); + +I915_WRITE (reg,VIDEO_DIP_ENABLE | val | flags); +} +static void intel_set_infoframe (struct drm_encoder *encoder,struct dip_infoframe *frame) {
@@ -587,6 +617,10 @@ void intel_hdmi_init(struct drm_device *dev, int sdvox_reg) intel_hdmi->write_infoframe = vlv_write_infoframe;for_each_pipe (i)I915_WRITE (VLV_TVIDEO_DIP_CTL (i),0 ); + }else if (IS_HASWELL (dev)) { + intel_hdmi->write_infoframe = hsw_write_infoframe; +for_each_pipe (i) +I915_WRITE (HSW_TVIDEO_DIP_CTL (i),0 ); }else { intel_hdmi->write_infoframe = ironlake_write_infoframe;for_each_pipe (i)
Signature · 1 line
1.7.10
PATCH 3/24 drm/i915: add support for SBI ops
In reply to Eugeni DodonovWith Lynx Point, we need to use SBI to communicate with the display clock control. This commit adds helper functions to access the registers via SBI.
v2: de-inline the function and address changes in bits names
v3: protect operations with dpio_lock, increase timeout to 100 for paranoia sake.
v4: decrease paranoia a bit, as noticed by Chris Wilson
v1 Reviewed-by: Rodrigo Vivi <[email protected]>
--- drivers/gpu/drm/i915/intel_display.c | 63 ++++++++++++++++++++++++++++++++++ 1 file changed, 63 insertions(+)
drivers/gpu/drm/i915/intel_display.c +63 -0
@@ -1300,6 +1300,69 @@ static void intel_disable_pll(struct drm_i915_private *dev_priv, enum pipe pipe)POSTING_READ (reg); } +/* SBI access */ +static void +intel_sbi_write (struct drm_i915_private *dev_priv,u16 reg,u32 value) +{ +unsigned long flags; + +spin_lock_irqsave (&dev_priv->dpio_lock, flags); +if (wait_for ((I915_READ (SBI_CTL_STAT ) &SBI_READY ) ==0 , +100 )) { +DRM_ERROR ("timeout waiting for SBI to become ready\n" ); + goto out_unlock; + } + +I915_WRITE (SBI_ADDR , + (reg <<16 )); +I915_WRITE (SBI_DATA , + value); +I915_WRITE (SBI_CTL_STAT , +SBI_BUSY | +SBI_CTL_OP_CRWR ); + +if (wait_for ((I915_READ (SBI_CTL_STAT ) & (SBI_READY |SBI_RESPONSE_SUCCESS )) ==0 , +100 )) { +DRM_ERROR ("timeout waiting for SBI to complete write transaction\n" ); + goto out_unlock; + } + +out_unlock: +spin_unlock_irqrestore (&dev_priv->dpio_lock, flags); +} + +static u32 +intel_sbi_read (struct drm_i915_private *dev_priv,u16 reg) +{ +unsigned long flags; +u32 value; + +spin_lock_irqsave (&dev_priv->dpio_lock, flags); +if (wait_for ((I915_READ (SBI_CTL_STAT ) &SBI_READY ) ==0 , +100 )) { +DRM_ERROR ("timeout waiting for SBI to become ready\n" ); + goto out_unlock; + } + +I915_WRITE (SBI_ADDR , + (reg <<16 )); +I915_WRITE (SBI_CTL_STAT , +SBI_BUSY | +SBI_CTL_OP_CRRD ); + +if (wait_for ((I915_READ (SBI_CTL_STAT ) & (SBI_READY |SBI_RESPONSE_SUCCESS )) ==0 , +100 )) { +DRM_ERROR ("timeout waiting for SBI to complete read transaction\n" ); + goto out_unlock; + } + + value =I915_READ (SBI_DATA ); + +out_unlock: +spin_unlock_irqrestore (&dev_priv->dpio_lock, flags); +return value; +} +/** * intel_enable_pch_pll - enable PCH PLL * @dev_priv: i915 private structure
Signature · 1 line
1.7.10
Re: [PATCH 03/24] drm/i915: add support for SBI ops
Quoted 82 lines · On Thu, 26 Apr 2012 15:20:58 -0300 Eugeni Dodonov <[email protected]>…
With Lynx Point, we need to use SBI to communicate with the display clock control. This commit adds helper functions to access the registers via SBI.
v2: de-inline the function and address changes in bits names
v3: protect operations with
dpio_lock, increase timeout to 100 for paranoia sake.v4: decrease paranoia a bit, as noticed by Chris Wilson
v1 Reviewed-by: Rodrigo Vivi <[email protected]>
Signed-off-by Eugeni Dodonov <[email protected]>--- drivers/gpu/drm/i915/intel_display.c | 63 ++++++++++++++++++++++++++++++++++ 1 file changed, 63 insertions(+)drivers/gpu/drm/i915/intel_display.c +56
-0@@ -1300,6 +1300,69 @@ static void intel_disable_pll(struct drm_i915_private *dev_priv, enum pipe pipe)POSTING_READ (reg); } +/* SBI access */ +static void +intel_sbi_write (struct drm_i915_private *dev_priv,u16 reg,u32 value) +{ +unsigned long flags; + +spin_lock_irqsave (&dev_priv->dpio_lock, flags); +if (wait_for ((I915_READ (SBI_CTL_STAT ) &SBI_READY ) ==0 , +100 )) { +DRM_ERROR ("timeout waiting for SBI to become ready\n" ); + goto out_unlock; + } + +I915_WRITE (SBI_ADDR , + (reg <<16 )); +I915_WRITE (SBI_DATA , + value); +I915_WRITE (SBI_CTL_STAT , +SBI_BUSY | +SBI_CTL_OP_CRWR ); + +if (wait_for ((I915_READ (SBI_CTL_STAT ) & (SBI_READY |SBI_RESPONSE_SUCCESS )) ==0 , +100 )) { +DRM_ERROR ("timeout waiting for SBI to complete write transaction\n" ); + goto out_unlock; + } + +out_unlock: +spin_unlock_irqrestore (&dev_priv->dpio_lock, flags); +} + +static u32 +intel_sbi_read (struct drm_i915_private *dev_priv,u16 reg) +{ +unsigned long flags; +u32 value; + +spin_lock_irqsave (&dev_priv->dpio_lock, flags); +if (wait_for ((I915_READ (SBI_CTL_STAT ) &SBI_READY ) ==0 , +100 )) { +DRM_ERROR ("timeout waiting for SBI to become ready\n" ); + goto out_unlock; + } + +I915_WRITE (SBI_ADDR , + (reg <<16 )); +I915_WRITE (SBI_CTL_STAT , +SBI_BUSY | +SBI_CTL_OP_CRRD ); + +if (wait_for ((I915_READ (SBI_CTL_STAT ) & (SBI_READY |SBI_RESPONSE_SUCCESS )) ==0 , +100 )) { +DRM_ERROR ("timeout waiting for SBI to complete read transaction\n" ); + goto out_unlock; + } +
drivers/gpu/drm/i915/intel_display.c static void intel_disable_pll(struct drm_i915_private *dev_priv, enum pipe pipe) · line 1368
Quoted 10 lines
drivers/gpu/drm/i915/intel_display.c +7
-0+ value =I915_READ (SBI_DATA ); + +out_unlock: +spin_unlock_irqrestore (&dev_priv->dpio_lock, flags); +return value; +} +/** * intel_enable_pch_pll - enable PCH PLL * @dev_priv: i915 private structure
Hey these look familiar. :) I guess growing side bands is the new cool thing.
Signature · 1 line
Jesse Barnes, Intel Open Source Technology Center
PATCH 4/24 drm/i915: calculate same watermarks on Haswell as on Ivy Bridge
In reply to Eugeni Dodonov--- drivers/gpu/drm/i915/intel_pm.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/gpu/drm/i915/intel_pm.c +2 -2
@@ -1694,8 +1694,8 @@ static void sandybridge_update_wm(struct drm_device *dev) enabled |=2 ; } -/* IVB has 3 pipes */ -if (IS_IVYBRIDGE (dev) && +/* Only IVB and Haswell has 3 pipes support so far */ +if ((IS_IVYBRIDGE (dev) ||IS_HASWELL (dev)) && g4x_compute_wm0(dev, 2, &sandybridge_display_wm_info, latency, &sandybridge_cursor_wm_info, latency,
Signature · 1 line
1.7.10
Re: [PATCH 04/24] drm/i915: calculate same watermarks on Haswell as on Ivy Bridge
Quoted 10 lines · On Thu, 26 Apr 2012 15:20:59 -0300 Eugeni Dodonov <[email protected]>…
Signed-off-by Eugeni Dodonov <[email protected]>--- drivers/gpu/drm/i915/intel_pm.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)(quoted diff) +0
-0
b/drivers/gpu/drm/i915/intel_pm.cindex 0552058..06f38ec 100644
drivers/gpu/drm/i915/intel_pm.c static void sandybridge_update_wm(struct · line 1701
Quoted 10 lines
drivers/gpu/drm/i915/intel_pm.c +2
-2@@ -1694,8 +1694,8 @@ static void sandybridge_update_wm(struct drm_device *dev) enabled |= 2; } -/* IVB has 3 pipes */ -if (IS_IVYBRIDGE (dev) && +/* Only IVB and Haswell has 3 pipes support so far */ +if ((IS_IVYBRIDGE (dev) ||IS_HASWELL (dev)) && g4x_compute_wm0(dev, 2, &sandybridge_display_wm_info, latency, &sandybridge_cursor_wm_info, latency,
This could probably just check num_pipes instead.
Jesse
PATCH 4/24 drm/i915: calculate same watermarks on Haswell as on Ivy Bridge
v2: check for num_pipe instead, as suggested by Jesse
--- drivers/gpu/drm/i915/intel_pm.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
drivers/gpu/drm/i915/intel_pm.c +1 -2
@@ -1694,8 +1694,7 @@ static void sandybridge_update_wm(struct drm_device *dev) enabled |=2 ; } -/* IVB has 3 pipes */ -if (IS_IVYBRIDGE (dev) && +if ((dev_priv->num_pipe ==2 ) && g4x_compute_wm0(dev, 2, &sandybridge_display_wm_info, latency, &sandybridge_cursor_wm_info, latency,
Signature · 1 line
1.7.10
Re: [PATCH 04/24] drm/i915: calculate same watermarks on Haswell as on Ivy Bridge
Quoted 13 lines · On Thu, 26 Apr 2012 15:51:44 -0300 Eugeni Dodonov <[email protected]>…
v2: check for
num_pipeinstead, as suggested by JesseCC Jesse Barnes <[email protected]>Signed-off-by Eugeni Dodonov <[email protected]>--- drivers/gpu/drm/i915/intel_pm.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)drivers/gpu/drm/i915/intel_pm.c +0
-0
drivers/gpu/drm/i915/intel_pm.c static void sandybridge_update_wm(struct drm_device *dev) · line 1700
Quoted 9 lines
drivers/gpu/drm/i915/intel_pm.c +1
-2@@ -1694,8 +1694,7 @@ static void sandybridge_update_wm(struct drm_device *dev) enabled |=2 ; } -/* IVB has 3 pipes */ -if (IS_IVYBRIDGE (dev) && +if ((dev_priv->num_pipe ==2 ) && g4x_compute_wm0(dev, 2, &sandybridge_display_wm_info, latency, &sandybridge_cursor_wm_info, latency,
As noted on IRC, a cleanup (one of many for the WM code) would be to use a loop for calculating the per-pipe watermarks.
But that can be done on top.
Signature · 1 line
Jesse Barnes, Intel Open Source Technology Center
PATCH 5/24 drm/i915: reuse Ivybridge interrupts code for Haswell
In reply to Eugeni Dodonovv2: prevent possible conflicts with VLV.
v3: simplify IRQ handling for Gen5+ onwards.
v1 Reviewed-by: Rodrigo Vivi <[email protected]>
--- drivers/gpu/drm/i915/i915_irq.c | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-)
drivers/gpu/drm/i915/i915_irq.c +3 -4
@@ -2006,7 +2006,7 @@ static void ironlake_irq_preinstall(struct drm_device *dev)INIT_WORK (&dev_priv->hotplug_work, i915_hotplug_work_func);INIT_WORK (&dev_priv->error_work, i915_error_work_func); -if (IS_GEN6 (dev) ||IS_IVYBRIDGE (dev)) +if (IS_GEN6 (dev) ||IS_IVYBRIDGE (dev) ||IS_HASWELL (dev))INIT_WORK (&dev_priv->rps_work, gen6_pm_rps_work);I915_WRITE (HWSTAM ,0xeffe );
@@ -2627,8 +2627,7 @@ void intel_irq_init(struct drm_device *dev) { dev->driver->get_vblank_counter = i915_get_vblank_counter; dev->max_vblank_count =0xffffff ;/* only 24 bits of frame count */ -if (IS_G4X (dev) ||IS_GEN5 (dev) ||IS_GEN6 (dev) ||IS_IVYBRIDGE (dev) || -IS_VALLEYVIEW (dev)) { +if (IS_G4X (dev) ||INTEL_INFO (dev)->gen >=5 ) { dev->max_vblank_count =0xffffffff ;/* full 32 bit counter */ dev->driver->get_vblank_counter = gm45_get_vblank_counter; }
@@ -2646,7 +2645,7 @@ void intel_irq_init(struct drm_device *dev) dev->driver->irq_uninstall = valleyview_irq_uninstall; dev->driver->enable_vblank = valleyview_enable_vblank; dev->driver->disable_vblank = valleyview_disable_vblank; - }else if (IS_IVYBRIDGE (dev)) { + }else if (IS_IVYBRIDGE (dev) ||IS_HASWELL (dev)) {/* Share pre & uninstall handlers with ILK/SNB */ dev->driver->irq_handler = ivybridge_irq_handler; dev->driver->irq_preinstall = ironlake_irq_preinstall;
Signature · 1 line
1.7.10
Re: [PATCH 05/24] drm/i915: reuse Ivybridge interrupts code for Haswell
Quoted 34 lines · On Thu, 26 Apr 2012 15:21:00 -0300 Eugeni Dodonov <[email protected]>…
v2: prevent possible conflicts with VLV.
v3: simplify IRQ handling for Gen5+ onwards.
v1 Reviewed-by: Rodrigo Vivi <[email protected]>
Signed-off-by Eugeni Dodonov <[email protected]>--- drivers/gpu/drm/i915/i915_irq.c | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-)drivers/gpu/drm/i915/i915_irq.c +2
-3@@ -2006,7 +2006,7 @@ static void ironlake_irq_preinstall(struct drm_device *dev)INIT_WORK (&dev_priv->hotplug_work, i915_hotplug_work_func);INIT_WORK (&dev_priv->error_work, i915_error_work_func); -if (IS_GEN6 (dev) ||IS_IVYBRIDGE (dev)) +if (IS_GEN6 (dev) ||IS_IVYBRIDGE (dev) ||IS_HASWELL (dev))INIT_WORK (&dev_priv->rps_work, gen6_pm_rps_work);I915_WRITE (HWSTAM ,0xeffe );@@ -2627,8 +2627,7 @@ void intel_irq_init(struct drm_device *dev) { dev->driver->get_vblank_counter = i915_get_vblank_counter; dev->max_vblank_count =0xffffff ;/* only 24 bits of frame count */ -if (IS_G4X (dev) ||IS_GEN5 (dev) ||IS_GEN6 (dev) ||IS_IVYBRIDGE (dev) || -IS_VALLEYVIEW (dev)) { +if (IS_G4X (dev) ||INTEL_INFO (dev)->gen >=5 ) { dev->max_vblank_count =0xffffffff ;/* full 32 bit counter */ dev->driver->get_vblank_counter = gm45_get_vblank_counter; }
drivers/gpu/drm/i915/i915_irq.c void intel_irq_init(struct drm_device *dev) · line 2651
Quoted 8 lines
drivers/gpu/drm/i915/i915_irq.c +1
-1@@ -2646,7 +2645,7 @@ void intel_irq_init(struct drm_device *dev) dev->driver->irq_uninstall = valleyview_irq_uninstall; dev->driver->enable_vblank = valleyview_enable_vblank; dev->driver->disable_vblank = valleyview_disable_vblank; - }else if (IS_IVYBRIDGE (dev)) { + }else if (IS_IVYBRIDGE (dev) ||IS_HASWELL (dev)) {/* Share pre & uninstall handlers with ILK/SNB */ dev->driver->irq_handler = ivybridge_irq_handler; dev->driver->irq_preinstall = ironlake_irq_preinstall;
Needs to be rebased on top of Chris's recent cleanups. Should make things a little nicer.
Signature · 1 line
Jesse Barnes, Intel Open Source Technology Center
PATCH 6/24 drm/i915: properly check for pipe count
In reply to Eugeni DodonovAs suggested by Chris Wilson and Daniel Vetter, this chunk of code can be simplified with a more simple check.
--- drivers/gpu/drm/i915/intel_display.c | 14 ++++---------- 1 file changed, 4 insertions(+), 10 deletions(-)
drivers/gpu/drm/i915/intel_display.c +4 -10
@@ -1981,16 +1981,10 @@ intel_pipe_set_base(struct drm_crtc *crtc, int x, int y,return 0 ; } -switch (intel_crtc->plane) { -case 0 : -case 1 : -break ; -case 2 : -if (IS_IVYBRIDGE (dev)) -break ; -/* fall through otherwise */ -default : -DRM_ERROR ("no plane for crtc\n" ); +if (intel_crtc->plane > dev_priv->num_pipe) { +DRM_ERROR ("no plane for crtc: plane %d, num_pipes %d\n" , + intel_crtc->plane, + dev_priv->num_pipe);return -EINVAL ; }
Signature · 1 line
1.7.10
Re: [PATCH 06/24] drm/i915: properly check for pipe count
Quoted 25 lines · On Thu, 26 Apr 2012 15:21:01 -0300 Eugeni Dodonov <[email protected]>…
As suggested by Chris Wilson and Daniel Vetter, this chunk of code can be simplified with a more simple check.
CC Daniel Vetter <[email protected]>CC Chris Wilson <[email protected]>Signed-off-by Eugeni Dodonov <[email protected]>--- drivers/gpu/drm/i915/intel_display.c | 14 ++++---------- 1 file changed, 4 insertions(+), 10 deletions(-)drivers/gpu/drm/i915/intel_display.c +0
-7@@ -1981,16 +1981,10 @@ intel_pipe_set_base(struct drm_crtc *crtc, int x, int y,return 0 ; } -switch (intel_crtc->plane) { -case 0 : -case 1 : -break ; -case 2 : -if (IS_IVYBRIDGE (dev)) -break ;
drivers/gpu/drm/i915/intel_display.c intel_pipe_set_base(struct drm_crtc *crtc, int x, int y, · line 1990
Quoted 10 lines
drivers/gpu/drm/i915/intel_display.c +4
-3-/* fall through otherwise */ -default : -DRM_ERROR ("no plane for crtc\n" ); +if (intel_crtc->plane > dev_priv->num_pipe) { +DRM_ERROR ("no plane for crtc: plane %d, num_pipes %d\n" , + intel_crtc->plane, + dev_priv->num_pipe);return -EINVAL ; }
plane is an enum and num_pipe is an int, so we could be more paranoid here about signs and < 0.
But meh. These are purely driver internal, so we don't have to validate them too hard.
Signature · 1 line
Jesse Barnes, Intel Open Source Technology Center
PATCH 7/24 drm/i915: show unknown sdvox registers on hdmi init
In reply to Eugeni DodonovThis will throw a DRM_ERROR message when an unknown sdvox register is given to intel_hdmi_init. When this happens, things could going to be pretty much broken afterwards, so we better detect this as soon as possible.
--- drivers/gpu/drm/i915/intel_hdmi.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/gpu/drm/i915/intel_hdmi.c +2 -0
@@ -606,6 +606,8 @@ void intel_hdmi_init(struct drm_device *dev, int sdvox_reg) intel_encoder->clone_mask = (1 <<INTEL_HDMIF_CLONE_BIT ); intel_hdmi->ddc_bus =GMBUS_PORT_DPD ; dev_priv->hotplug_supported_mask |=HDMID_HOTPLUG_INT_STATUS ; + }else { +DRM_ERROR ("Unknown sdvox register on HDMI init: %x\n" , sdvox_reg); } intel_hdmi->sdvox_reg = sdvox_reg;
Signature · 1 line
1.7.10
Re: [PATCH 07/24] drm/i915: show unknown sdvox registers on hdmi init
Quoted 14 lines · On Thu, 26 Apr 2012 15:21:02 -0300 Eugeni Dodonov <[email protected]>…
This will throw a
DRM_ERRORmessage when an unknown sdvox register is given tointel_hdmi_init. When this happens, things could going to be pretty much broken afterwards, so we better detect this as soon as possible.Signed-off-by Eugeni Dodonov <[email protected]>--- drivers/gpu/drm/i915/intel_hdmi.c | 2 ++ 1 file changed, 2 insertions(+)drivers/gpu/drm/i915/intel_hdmi.c +0
-0
drivers/gpu/drm/i915/intel_hdmi.c void intel_hdmi_init(struct drm_device *dev, int sdvox_reg) · line 613
Quoted 8 lines
drivers/gpu/drm/i915/intel_hdmi.c +2
-0@@ -606,6 +606,8 @@ void intel_hdmi_init(struct drm_device *dev, int sdvox_reg) intel_encoder->clone_mask = (1 <<INTEL_HDMIF_CLONE_BIT ); intel_hdmi->ddc_bus =GMBUS_PORT_DPD ; dev_priv->hotplug_supported_mask |=HDMID_HOTPLUG_INT_STATUS ; + }else { +DRM_ERROR ("Unknown sdvox register on HDMI init: %x\n" , sdvox_reg); } intel_hdmi->sdvox_reg = sdvox_reg;
BUG_ON then? At least if this is purely a driver sanity check...
Signature · 1 line
Jesse Barnes, Intel Open Source Technology Center
PATCH 8/24 drm/i915: do not use fdi_normal_train on haswell
In reply to Eugeni DodonovThis should be already configured when FDI auto-negotiation is done.
--- drivers/gpu/drm/i915/intel_display.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/gpu/drm/i915/intel_display.c +2 -1
@@ -2700,7 +2700,8 @@ static void ironlake_pch_enable(struct drm_crtc *crtc)I915_WRITE (TRANS_VSYNC (pipe),I915_READ (VSYNC (pipe)));I915_WRITE (TRANS_VSYNCSHIFT (pipe),I915_READ (VSYNCSHIFT (pipe))); -intel_fdi_normal_train (crtc); +if (!IS_HASWELL (dev)) +intel_fdi_normal_train (crtc);/* For PCH DP, enable TRANS_DP_CTL */ if (HAS_PCH_CPT(dev) &&
Signature · 1 line
1.7.10
Re: [PATCH 08/24] drm/i915: do not use fdi_normal_train on haswell
Quoted 13 lines · On Thu, 26 Apr 2012 15:21:03 -0300 Eugeni Dodonov <[email protected]>…
This should be already configured when FDI auto-negotiation is done.
Reviewed-by Rodrigo Vivi <[email protected]>Signed-off-by Eugeni Dodonov <[email protected]>--- drivers/gpu/drm/i915/intel_display.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)drivers/gpu/drm/i915/intel_display.c +0
-0
drivers/gpu/drm/i915/intel_display.c static void ironlake_pch_enable(struct drm_crtc *crtc) · line 2707
Quoted 9 lines
drivers/gpu/drm/i915/intel_display.c +2
-1@@ -2700,7 +2700,8 @@ static void ironlake_pch_enable(struct drm_crtc *crtc)I915_WRITE (TRANS_VSYNC (pipe),I915_READ (VSYNC (pipe)));I915_WRITE (TRANS_VSYNCSHIFT (pipe),I915_READ (VSYNCSHIFT (pipe))); -intel_fdi_normal_train (crtc); +if (!IS_HASWELL (dev)) +intel_fdi_normal_train (crtc);/* For PCH DP, enable TRANS_DP_CTL */ if (HAS_PCH_CPT(dev) &&
We could probably try autotraining on IVB too, just for fun.
But until then, the HSW check is fine.
Signature · 1 line
Jesse Barnes, Intel Open Source Technology Center
PATCH 9/24 drm/i915: detect PCH encoders on Haswell
In reply to Eugeni DodonovOn Haswell, the recommended PCH-connected output is the one driven by DDI E in FDI mode, used for VGA connection. All the others are handled by the CPU.
Note that this does not accounts for Haswell/PPT combination yet.
--- drivers/gpu/drm/i915/intel_display.c | 12 ++++++++++++ 1 file changed, 12 insertions(+)
drivers/gpu/drm/i915/intel_display.c +12 -0
@@ -2631,6 +2631,18 @@ static bool intel_crtc_driving_pch(struct drm_crtc *crtc)if (encoder->base.crtc != crtc)continue ; +/* On Haswell, LPT PCH handles the VGA connection via FDI, and Haswell +* CPU handles all others */ +if (IS_HASWELL (dev)) { +if (HAS_PCH_LPT (dev) && (encoder->type ==DRM_MODE_ENCODER_DAC )) +return true; +else { +DRM_DEBUG_KMS ("Haswell detected encoder %d, assuming is CPU\n" , + encoder->type); +return false; + } + } +switch (encoder->type) {case INTEL_OUTPUT_EDP :if (!intel_encoder_is_pch_edp (&encoder->base))
Signature · 1 line
1.7.10
Re: [PATCH 09/24] drm/i915: detect PCH encoders on Haswell
Quoted 24 lines · On Thu, 26 Apr 2012 15:21:04 -0300 Eugeni Dodonov <[email protected]>…
On Haswell, the recommended PCH-connected output is the one driven by DDI E in FDI mode, used for VGA connection. All the others are handled by the CPU.
Note that this does not accounts for Haswell/PPT combination yet.
Signed-off-by Eugeni Dodonov <[email protected]>--- drivers/gpu/drm/i915/intel_display.c | 12 ++++++++++++ 1 file changed, 12 insertions(+)drivers/gpu/drm/i915/intel_display.c +5
-0@@ -2631,6 +2631,18 @@ static bool intel_crtc_driving_pch(struct drm_crtc *crtc)if (encoder->base.crtc != crtc)continue ; +/* On Haswell, LPT PCH handles the VGA connection via FDI, and Haswell +* CPU handles all others */ +if (IS_HASWELL (dev)) { +if (HAS_PCH_LPT (dev) && (encoder->type ==DRM_MODE_ENCODER_DAC )) +return true;
drivers/gpu/drm/i915/intel_display.c static bool intel_crtc_driving_pch(struct drm_crtc *crtc) · line 2648
Quoted 10 lines
drivers/gpu/drm/i915/intel_display.c +7
-0+else { +DRM_DEBUG_KMS ("Haswell detected encoder %d, assuming is CPU\n" , + encoder->type); +return false; + } + } +switch (encoder->type) {case INTEL_OUTPUT_EDP :if (!intel_encoder_is_pch_edp (&encoder->base))
Do HSW/PPT combinations exist? If so, we should probably note that with an error or something loud so that people won't think it should work...
Signature · 1 line
Jesse Barnes, Intel Open Source Technology Center
PATCH 10/24 drm/i915: enable power wells on haswell init
In reply to Eugeni DodonovThis attempts to enable all the available power wells during the initialization.
Those power wells can be enabled in parallel or on-demand, and disabled when no longer needed, but this is out of scope of this initial enablement. Proper tracking of who uses which power well will require a considerable rework of our display handling, so we just leave them all enabled when the driver is loaded for now.
v2: use more generic and future-proof code
--- drivers/gpu/drm/i915/intel_pm.c | 36 ++++++++++++++++++++++++++++++++++++ 1 file changed, 36 insertions(+)
drivers/gpu/drm/i915/intel_pm.c +36 -0
@@ -2937,6 +2937,37 @@ void intel_init_clock_gating(struct drm_device *dev) dev_priv->display.init_pch_clock_gating (dev); } +/* Starting with Haswell, we have different power wells for +* different parts of the GPU. This attempts to enable them all. +*/ +void intel_init_power_wells (struct drm_device *dev) +{ +struct drm_i915_private *dev_priv = dev->dev_private; +unsigned long power_wells[] = { +HSW_PWR_WELL_CTL1 , +HSW_PWR_WELL_CTL2 , +HSW_PWR_WELL_CTL4 + }; +int i; + +if (!IS_HASWELL (dev)) +return ; + +mutex_lock (&dev->struct_mutex); + +for (i =0 ; i <ARRAY_SIZE (power_wells); i++) { +int well =I915_READ (power_wells[i]); + +if ((well &HSW_PWR_WELL_STATE ) ==0 ) { +I915_WRITE (power_wells[i], well &HSW_PWR_WELL_ENABLE ); +if (wait_for (I915_READ (power_wells[i] &HSW_PWR_WELL_STATE ),20 )) +DRM_ERROR ("Error enabling power well %lx\n" , power_wells[i]); + } + } + +mutex_unlock (&dev->struct_mutex); +} +/* Set up chip specific power management-related functions */ void intel_init_pm (struct drm_device *dev) {
@@ -3077,5 +3108,10 @@ void intel_init_pm(struct drm_device *dev)else dev_priv->display.get_fifo_size = i830_get_fifo_size; } + +/* We attempt to init the necessary power wells early in the initialization +* time, so the subsystems that expect power to be enabled can work. +*/ +intel_init_power_wells (dev); }
Signature · 1 line
1.7.10
Re: [PATCH 10/24] drm/i915: enable power wells on haswell init
Quoted 59 lines · On Thu, 26 Apr 2012 15:21:05 -0300 Eugeni Dodonov <[email protected]>…
This attempts to enable all the available power wells during the initialization.
Those power wells can be enabled in parallel or on-demand, and disabled when no longer needed, but this is out of scope of this initial enablement. Proper tracking of who uses which power well will require a considerable rework of our display handling, so we just leave them all enabled when the driver is loaded for now.
v2: use more generic and future-proof code
Signed-off-by Eugeni Dodonov <[email protected]>--- drivers/gpu/drm/i915/intel_pm.c | 36 ++++++++++++++++++++++++++++++++++++ 1 file changed, 36 insertions(+)drivers/gpu/drm/i915/intel_pm.c +31
-0@@ -2937,6 +2937,37 @@ void intel_init_clock_gating(struct drm_device *dev) dev_priv->display.init_pch_clock_gating (dev); } +/* Starting with Haswell, we have different power wells for +* different parts of the GPU. This attempts to enable them all. +*/ +void intel_init_power_wells (struct drm_device *dev) +{ +struct drm_i915_private *dev_priv = dev->dev_private; +unsigned long power_wells[] = { +HSW_PWR_WELL_CTL1 , +HSW_PWR_WELL_CTL2 , +HSW_PWR_WELL_CTL4 + }; +int i; + +if (!IS_HASWELL (dev)) +return ; + +mutex_lock (&dev->struct_mutex); + +for (i =0 ; i <ARRAY_SIZE (power_wells); i++) { +int well =I915_READ (power_wells[i]); + +if ((well &HSW_PWR_WELL_STATE ) ==0 ) { +I915_WRITE (power_wells[i], well &HSW_PWR_WELL_ENABLE ); +if (wait_for (I915_READ (power_wells[i] &HSW_PWR_WELL_STATE ),20 )) +DRM_ERROR ("Error enabling power well %lx\n" , power_wells[i]); + } + } + +mutex_unlock (&dev->struct_mutex); +} +/* Set up chip specific power management-related functions */ void intel_init_pm (struct drm_device *dev) {
drivers/gpu/drm/i915/intel_pm.c void intel_init_pm(struct drm_device *dev) · line 3117
Quoted 10 lines
drivers/gpu/drm/i915/intel_pm.c +5
-0@@ -3077,5 +3108,10 @@ void intel_init_pm(struct drm_device *dev)else dev_priv->display.get_fifo_size = i830_get_fifo_size; } + +/* We attempt to init the necessary power wells early in the initialization +* time, so the subsystems that expect power to be enabled can work. +*/ +intel_init_power_wells (dev); }
Note that many of the regs are controls like we have in the IVB MT forcewake path rather than separate power planes in the GPU (i.e. one of many agents can wake up the GPU for whatever reason: BIOS, driver, KVMr, etc). At least that's what it looks like to me, maybe you have more up-to-date info.
That said, it's important for us to clear the driver and debug power well bits when we shut down the display since it should save us a lot of power.
Signature · 1 line
Jesse Barnes, Intel Open Source Technology Center
PATCH 11/24 drm/i915: program WM_LINETIME on Haswell
In reply to Eugeni DodonovThe line time can be programmed according to the number of horizontal pixels vs effective pixel rate ratio.
v2: improve comment as per Chris Wilson suggestion
v3: incorporate latest changes in specs.
--- drivers/gpu/drm/i915/intel_display.c | 13 +++++++++++++ 1 file changed, 13 insertions(+)
drivers/gpu/drm/i915/intel_display.c +13 -0
@@ -4555,6 +4555,19 @@ static int ironlake_crtc_mode_set(struct drm_crtc *crtc, (adjusted_mode->crtc_vsync_start -1 ) | ((adjusted_mode->crtc_vsync_end - 1) << 16)); +if (IS_HASWELL (dev)) { + temp =I915_READ (PIPE_WM_LINETIME (pipe)); + temp &= ~PIPE_WM_LINETIME_MASK ; + +/* The WM are computed with base on how long it takes to fill a single +* row at the given clock rate, multiplied by 8. +* */ + temp |=PIPE_WM_LINETIME_TIME ( + ((adjusted_mode->crtc_hdisplay *1000 ) / adjusted_mode->clock) *8 ); + +I915_WRITE (PIPE_WM_LINETIME (pipe), temp); + } +/* pipesrc controls the size that is scaled from, which should * always be the user's requested size. */
Signature · 1 line
1.7.10
Re: [PATCH 11/24] drm/i915: program WM_LINETIME on Haswell
Quoted 26 lines · On Thu, 26 Apr 2012 15:21:06 -0300 Eugeni Dodonov <[email protected]>…
The line time can be programmed according to the number of horizontal pixels vs effective pixel rate ratio.
v2: improve comment as per Chris Wilson suggestion
v3: incorporate latest changes in specs.
Signed-off-by Eugeni Dodonov <[email protected]>--- drivers/gpu/drm/i915/intel_display.c | 13 +++++++++++++ 1 file changed, 13 insertions(+)drivers/gpu/drm/i915/intel_display.c +6
-0@@ -4555,6 +4555,19 @@ static int ironlake_crtc_mode_set(struct drm_crtc *crtc, (adjusted_mode->crtc_vsync_start -1 ) | ((adjusted_mode->crtc_vsync_end - 1) << 16)); +if (IS_HASWELL (dev)) { + temp =I915_READ (PIPE_WM_LINETIME (pipe)); + temp &= ~PIPE_WM_LINETIME_MASK ; + +/* The WM are computed with base on how long it takes to fill a single +* row at the given clock rate, multiplied by 8.
drivers/gpu/drm/i915/intel_display.c static int ironlake_crtc_mode_set(struct drm_crtc *crtc, · line 4573
Quoted 10 lines
drivers/gpu/drm/i915/intel_display.c +7
-0+* */ + temp |=PIPE_WM_LINETIME_TIME ( + ((adjusted_mode->crtc_hdisplay *1000 ) / adjusted_mode->clock) *8 ); + +I915_WRITE (PIPE_WM_LINETIME (pipe), temp); + } +/* pipesrc controls the size that is scaled from, which should * always be the user's requested size. */
We need to set the IPS line time as well, and can we do it in the WM functions instead?
Signature · 1 line
Jesse Barnes, Intel Open Source Technology Center
PATCH 12/24 drm/i915: add LPT PCH checks
In reply to Eugeni DodonovAvoid bogus asserts on Lynx Point.
--- drivers/gpu/drm/i915/intel_display.c | 10 ++++++++++ 1 file changed, 10 insertions(+)
drivers/gpu/drm/i915/intel_display.c +10 -0
@@ -917,6 +917,11 @@ static void assert_pch_pll(struct drm_i915_private *dev_priv,u32 val;bool cur_state; +if (HAS_PCH_LPT (dev_priv->dev)) { +DRM_DEBUG_DRIVER ("LPT detected: skipping PCH PLL test\n" ); +return ; + } +if (!intel_crtc->pch_pll) {WARN (1 ,"asserting PCH PLL enabled with no PLL\n" );return ;
@@ -1102,6 +1107,11 @@ static void assert_pch_refclk_enabled(struct drm_i915_private *dev_priv)u32 val;bool enabled; +if (HAS_PCH_LPT (dev_priv->dev)) { +DRM_DEBUG_DRIVER ("LPT does not has PCH refclk, skipping check\n" ); +return ; + } + val =I915_READ (PCH_DREF_CONTROL ); enabled = !!(val & (DREF_SSC_SOURCE_MASK |DREF_NONSPREAD_SOURCE_MASK |DREF_SUPERSPREAD_SOURCE_MASK ));
Signature · 1 line
1.7.10
Re: [PATCH 12/24] drm/i915: add LPT PCH checks
Quoted 25 lines · On Thu, 26 Apr 2012 15:21:07 -0300 Eugeni Dodonov <[email protected]>…
Avoid bogus asserts on Lynx Point.
Signed-off-by Eugeni Dodonov <[email protected]>--- drivers/gpu/drm/i915/intel_display.c | 10 ++++++++++ 1 file changed, 10 insertions(+)drivers/gpu/drm/i915/intel_display.c +5
-0@@ -917,6 +917,11 @@ static void assert_pch_pll(struct drm_i915_private *dev_priv,u32 val;bool cur_state; +if (HAS_PCH_LPT (dev_priv->dev)) { +DRM_DEBUG_DRIVER ("LPT detected: skipping PCH PLL test\n" ); +return ; + } +if (!intel_crtc->pch_pll) {WARN (1 ,"asserting PCH PLL enabled with no PLL\n" );return ;@@ -1102,6 +1107,11 @@ static void assert_pch_refclk_enabled(struct drm_i915_private *dev_priv)u32 val;
drivers/gpu/drm/i915/intel_display.c static void assert_pch_refclk_enabled(struct drm_i915_private *dev_priv) · line 1117
Quoted 10 lines
drivers/gpu/drm/i915/intel_display.c +5
-0bool enabled; +if (HAS_PCH_LPT (dev_priv->dev)) { +DRM_DEBUG_DRIVER ("LPT does not has PCH refclk, skipping check\n" ); +return ; + } + val =I915_READ (PCH_DREF_CONTROL ); enabled = !!(val & (DREF_SSC_SOURCE_MASK |DREF_NONSPREAD_SOURCE_MASK |DREF_SUPERSPREAD_SOURCE_MASK ));
Hm this makes me think we might want separate crtc enable/disable functions for HSW instead, when combined with a couple of the other checks.
Up to you...
Signature · 1 line
Jesse Barnes, Intel Open Source Technology Center
PATCH 13/24 drm/i915: handle DDI-related assertions
In reply to Eugeni DodonovPrevent bogus asserts on DDI-related paths.
--- drivers/gpu/drm/i915/intel_display.c | 35 ++++++++++++++++++++++++---------- 1 file changed, 25 insertions(+), 10 deletions(-)
drivers/gpu/drm/i915/intel_display.c +25 -10
@@ -954,9 +954,16 @@ static void assert_fdi_tx(struct drm_i915_private *dev_priv,u32 val;bool cur_state; - reg =FDI_TX_CTL (pipe); - val =I915_READ (reg); - cur_state = !!(val &FDI_TX_ENABLE ); +if (IS_HASWELL (dev_priv->dev)) { +/* On Haswell, DDI is used instead of FDI_TX_CTL */ + reg =DDI_FUNC_CTL (pipe); + val =I915_READ (reg); + cur_state = !!(val &PIPE_DDI_FUNC_ENABLE ); + }else { + reg =FDI_TX_CTL (pipe); + val =I915_READ (reg); + cur_state = !!(val &FDI_TX_ENABLE ); + }WARN (cur_state != state,"FDI TX state assertion failure (expected %s, current %s)\n" ,state_string (state),state_string (cur_state));
@@ -991,6 +998,10 @@ static void assert_fdi_tx_pll_enabled(struct drm_i915_private *dev_priv,if (dev_priv->info->gen ==5 )return ; +/* On Haswell, DDI ports are responsible for the FDI PLL setup */ +if (IS_HASWELL (dev_priv->dev)) +return ; + reg =FDI_TX_CTL (pipe); val =I915_READ (reg);WARN (!(val &FDI_TX_PLL_ENABLE ),"FDI TX PLL assertion failure, should be active but is disabled\n" );
@@ -2515,14 +2526,18 @@ static void ironlake_fdi_pll_enable(struct drm_crtc *crtc)POSTING_READ (reg);udelay (200 ); -/* Enable CPU FDI TX PLL, always on for Ironlake */ - reg =FDI_TX_CTL (pipe); - temp =I915_READ (reg); -if ((temp &FDI_TX_PLL_ENABLE ) ==0 ) { -I915_WRITE (reg, temp |FDI_TX_PLL_ENABLE ); +/* On Haswell, the PLL configuration for ports and pipes is handled +* separately, as part of DDI setup */ +if (!IS_HASWELL (dev)) { +/* Enable CPU FDI TX PLL, always on for Ironlake */ + reg =FDI_TX_CTL (pipe); + temp =I915_READ (reg); +if ((temp &FDI_TX_PLL_ENABLE ) ==0 ) { +I915_WRITE (reg, temp |FDI_TX_PLL_ENABLE ); -POSTING_READ (reg); -udelay (100 ); +POSTING_READ (reg); +udelay (100 ); + } } }
Signature · 1 line
1.7.10
Re: [PATCH 13/24] drm/i915: handle DDI-related assertions
Quoted 58 lines · On Thu, 26 Apr 2012 15:21:08 -0300 Eugeni Dodonov <[email protected]>…
Prevent bogus asserts on DDI-related paths.
Signed-off-by Eugeni Dodonov <[email protected]>--- drivers/gpu/drm/i915/intel_display.c | 35 ++++++++++++++++++++++++---------- 1 file changed, 25 insertions(+), 10 deletions(-)drivers/gpu/drm/i915/intel_display.c +21
-8@@ -954,9 +954,16 @@ static void assert_fdi_tx(struct drm_i915_private *dev_priv,u32 val;bool cur_state; - reg =FDI_TX_CTL (pipe); - val =I915_READ (reg); - cur_state = !!(val &FDI_TX_ENABLE ); +if (IS_HASWELL (dev_priv->dev)) { +/* On Haswell, DDI is used instead of FDI_TX_CTL */ + reg =DDI_FUNC_CTL (pipe); + val =I915_READ (reg); + cur_state = !!(val &PIPE_DDI_FUNC_ENABLE ); + }else { + reg =FDI_TX_CTL (pipe); + val =I915_READ (reg); + cur_state = !!(val &FDI_TX_ENABLE ); + }WARN (cur_state != state,"FDI TX state assertion failure (expected %s, current %s)\n" ,state_string (state),state_string (cur_state));@@ -991,6 +998,10 @@ static void assert_fdi_tx_pll_enabled(struct drm_i915_private *dev_priv,if (dev_priv->info->gen ==5 )return ; +/* On Haswell, DDI ports are responsible for the FDI PLL setup */ +if (IS_HASWELL (dev_priv->dev)) +return ; + reg =FDI_TX_CTL (pipe); val =I915_READ (reg);WARN (!(val &FDI_TX_PLL_ENABLE ),"FDI TX PLL assertion failure, should be active but is disabled\n" );@@ -2515,14 +2526,18 @@ static void ironlake_fdi_pll_enable(struct drm_crtc *crtc)POSTING_READ (reg);udelay (200 ); -/* Enable CPU FDI TX PLL, always on for Ironlake */ - reg =FDI_TX_CTL (pipe); - temp =I915_READ (reg); -if ((temp &FDI_TX_PLL_ENABLE ) ==0 ) { -I915_WRITE (reg, temp |FDI_TX_PLL_ENABLE ); +/* On Haswell, the PLL configuration for ports and pipes is handled +* separately, as part of DDI setup */ +if (!IS_HASWELL (dev)) { +/* Enable CPU FDI TX PLL, always on for Ironlake */ + reg =FDI_TX_CTL (pipe); + temp =I915_READ (reg); +if ((temp &FDI_TX_PLL_ENABLE ) ==0 ) {
drivers/gpu/drm/i915/intel_display.c static void ironlake_fdi_pll_enable(struct drm_crtc *crtc) · line 2543
Quoted 10 lines
drivers/gpu/drm/i915/intel_display.c +4
-2+I915_WRITE (reg, temp |FDI_TX_PLL_ENABLE ); -POSTING_READ (reg); -udelay (100 ); +POSTING_READ (reg); +udelay (100 ); + } } }
Maybe some small helper functions instead? Or possibly separate high level enable/disable functions...
Signature · 1 line
Jesse Barnes, Intel Open Source Technology Center
PATCH 14/24 drm/i915: account for only one PCH receiver on Haswell
In reply to Eugeni DodonovOn Haswell, only one pipe can work in FDI mode, so this patch prevents messing with wrong registers when FDI is being used by non-first pipe.
--- drivers/gpu/drm/i915/intel_display.c | 19 ++++++++++++++++--- 1 file changed, 16 insertions(+), 3 deletions(-)
drivers/gpu/drm/i915/intel_display.c +16 -3
@@ -978,9 +978,14 @@ static void assert_fdi_rx(struct drm_i915_private *dev_priv,u32 val;bool cur_state; - reg =FDI_RX_CTL (pipe); - val =I915_READ (reg); - cur_state = !!(val &FDI_RX_ENABLE ); +if (IS_HASWELL (dev_priv->dev) && pipe >0 ) { +DRM_ERROR ("Attempting to enable FDI_RX on Haswell pipe > 0\n" ); +return ; + }else { + reg =FDI_RX_CTL (pipe); + val =I915_READ (reg); + cur_state = !!(val &FDI_RX_ENABLE ); + }WARN (cur_state != state,"FDI RX state assertion failure (expected %s, current %s)\n" ,state_string (state),state_string (cur_state));
@@ -1013,6 +1018,10 @@ static void assert_fdi_rx_pll_enabled(struct drm_i915_private *dev_priv,int reg;u32 val; +if (IS_HASWELL (dev_priv->dev) && pipe >0 ) { +DRM_ERROR ("Attempting to enable FDI on Haswell with pipe > 0\n" ); +return ; + } reg =FDI_RX_CTL (pipe); val =I915_READ (reg);WARN (!(val &FDI_RX_PLL_ENABLE ),"FDI RX PLL assertion failure, should be active but is disabled\n" );
@@ -1484,6 +1493,10 @@ static void intel_enable_transcoder(struct drm_i915_private *dev_priv,assert_fdi_tx_enabled (dev_priv, pipe);assert_fdi_rx_enabled (dev_priv, pipe); +if (IS_HASWELL (dev_priv->dev) && pipe >0 ) { +DRM_ERROR ("Attempting to enable transcoder on Haswell with pipe > 0\n" ); +return ; + } reg =TRANSCONF (pipe); val =I915_READ (reg); pipeconf_val =I915_READ (PIPECONF (pipe));
Signature · 1 line
1.7.10
Re: [PATCH 14/24] drm/i915: account for only one PCH receiver on Haswell
Quoted 4 lines · Eugeni Dodonov
On Haswell, only one pipe can work in FDI mode, so this patch prevents messing with wrong registers when FDI is being used by non-first pipe.
Signed-off-by Eugeni Dodonov <[email protected]>
I think we need to restrict the vga encoder to pipe 0 with possible_crtcs, otherwise userspace won't figure out why vga just won't work. Can you please add this to this patch? Also, please add a small note to the commit message that fdi should work on any pipe, we're just making our lifes easier for now ...
-Daniel
Quoted 55 lines
--- drivers/gpu/drm/i915/intel_display.c | 19 ++++++++++++++++--- 1 file changed, 16 insertions(+), 3 deletions(-)drivers/gpu/drm/i915/intel_display.c +16
-3@@ -978,9 +978,14 @@ static void assert_fdi_rx(struct drm_i915_private *dev_priv,u32 val;bool cur_state; - reg =FDI_RX_CTL (pipe); - val =I915_READ (reg); - cur_state = !!(val &FDI_RX_ENABLE ); +if (IS_HASWELL (dev_priv->dev) && pipe >0 ) { +DRM_ERROR ("Attempting to enable FDI_RX on Haswell pipe > 0\n" ); +return ; + }else { + reg =FDI_RX_CTL (pipe); + val =I915_READ (reg); + cur_state = !!(val &FDI_RX_ENABLE ); + }WARN (cur_state != state,"FDI RX state assertion failure (expected %s, current %s)\n" ,state_string (state),state_string (cur_state));@@ -1013,6 +1018,10 @@ static void assert_fdi_rx_pll_enabled(struct drm_i915_private *dev_priv,int reg;u32 val; +if (IS_HASWELL (dev_priv->dev) && pipe >0 ) { +DRM_ERROR ("Attempting to enable FDI on Haswell with pipe > 0\n" ); +return ; + } reg =FDI_RX_CTL (pipe); val =I915_READ (reg);WARN (!(val &FDI_RX_PLL_ENABLE ),"FDI RX PLL assertion failure, should be active but is disabled\n" );@@ -1484,6 +1493,10 @@ static void intel_enable_transcoder(struct drm_i915_private *dev_priv,assert_fdi_tx_enabled (dev_priv, pipe);assert_fdi_rx_enabled (dev_priv, pipe); +if (IS_HASWELL (dev_priv->dev) && pipe >0 ) { +DRM_ERROR ("Attempting to enable transcoder on Haswell with pipe > 0\n" ); +return ; + } reg =TRANSCONF (pipe); val =I915_READ (reg); pipeconf_val =I915_READ (PIPECONF (pipe));Signature · 6 lines
1.7.10 _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Signature · 3 lines
Daniel Vetter Mail: [email protected] Mobile: +41 (0)79 365 57 48
Re: [PATCH 14/24] drm/i915: account for only one PCH receiver on Haswell
In reply to Eugeni DodonovQuoted 42 lines · On Thu, 26 Apr 2012 15:21:09 -0300 Eugeni Dodonov <[email protected]>…
On Haswell, only one pipe can work in FDI mode, so this patch prevents messing with wrong registers when FDI is being used by non-first pipe.
Signed-off-by Eugeni Dodonov <[email protected]>--- drivers/gpu/drm/i915/intel_display.c | 19 ++++++++++++++++--- 1 file changed, 16 insertions(+), 3 deletions(-)drivers/gpu/drm/i915/intel_display.c +12
-3@@ -978,9 +978,14 @@ static void assert_fdi_rx(struct drm_i915_private *dev_priv,u32 val;bool cur_state; - reg =FDI_RX_CTL (pipe); - val =I915_READ (reg); - cur_state = !!(val &FDI_RX_ENABLE ); +if (IS_HASWELL (dev_priv->dev) && pipe >0 ) { +DRM_ERROR ("Attempting to enable FDI_RX on Haswell pipe > 0\n" ); +return ; + }else { + reg =FDI_RX_CTL (pipe); + val =I915_READ (reg); + cur_state = !!(val &FDI_RX_ENABLE ); + }WARN (cur_state != state,"FDI RX state assertion failure (expected %s, current %s)\n" ,state_string (state),state_string (cur_state));@@ -1013,6 +1018,10 @@ static void assert_fdi_rx_pll_enabled(struct drm_i915_private *dev_priv,int reg;u32 val; +if (IS_HASWELL (dev_priv->dev) && pipe >0 ) { +DRM_ERROR ("Attempting to enable FDI on Haswell with pipe > 0\n" ); +return ; + } reg =FDI_RX_CTL (pipe); val =I915_READ (reg);WARN (!(val &FDI_RX_PLL_ENABLE ),"FDI RX PLL assertion failure, should be active but is disabled\n" );
drivers/gpu/drm/i915/intel_display.c static void intel_enable_transcoder(struct drm_i915_private *dev_priv, · line 1502
Quoted 10 lines
drivers/gpu/drm/i915/intel_display.c +4
-0@@ -1484,6 +1493,10 @@ static void intel_enable_transcoder(struct drm_i915_private *dev_priv,assert_fdi_tx_enabled (dev_priv, pipe);assert_fdi_rx_enabled (dev_priv, pipe); +if (IS_HASWELL (dev_priv->dev) && pipe >0 ) { +DRM_ERROR ("Attempting to enable transcoder on Haswell with pipe > 0\n" ); +return ; + } reg =TRANSCONF (pipe); val =I915_READ (reg); pipeconf_val =I915_READ (PIPECONF (pipe));
Yuck... good thing only VGA is on the PCH.
If you don't end up doing separate high level functions for this:
Signature · 1 line
Jesse Barnes, Intel Open Source Technology Center
PATCH 15/24 drm/i915: initialize DDI buffer translations
In reply to Eugeni DodonovDDI is introduced starting with Haswell GPU generation. So to simplify its management in the future, we also add intel_ddi.c to hold all the DDI-related items.
Buffer translations for DDI links must be initialized prior to enablement. For FDI and DP, first 9 pairs of values are used to select the connection parameters. HDMI uses the last pair of values and ignores the first 9 pairs. So we program HDMI values in both cases, which allows HDMI to work over both FDI and DP-friendly buffers.
--- drivers/gpu/drm/i915/Makefile | 1 + drivers/gpu/drm/i915/intel_ddi.c | 111 ++++++++++++++++++++++++++++++++++ drivers/gpu/drm/i915/intel_display.c | 2 + drivers/gpu/drm/i915/intel_drv.h | 1 + 4 files changed, 115 insertions(+) create mode 100644 drivers/gpu/drm/i915/intel_ddi.c
drivers/gpu/drm/i915/Makefile +1 -0
@@ -19,6 +19,7 @@ i915-y := i915_drv.o i915_dma.o i915_irq.o \ intel_crt.o \ intel_lvds.o \ intel_bios.o \ + intel_ddi.o \ intel_dp.o \ intel_hdmi.o \ intel_sdvo.o \
drivers/gpu/drm/i915/intel_ddi.c new file +111 -0
111 lines not on this page · raw message
drivers/gpu/drm/i915/intel_display.c +2 -0
@@ -6815,6 +6815,8 @@ void intel_modeset_init(struct drm_device *dev)intel_init_pm (dev); +intel_prepare_ddi (dev); +intel_init_display (dev);if (IS_GEN2 (dev)) {
drivers/gpu/drm/i915/intel_drv.h +1 -0
@@ -442,6 +442,7 @@ extern void intel_init_clock_gating(struct drm_device *dev);extern void intel_write_eld (struct drm_encoder *encoder,struct drm_display_mode *mode);extern void intel_cpt_verify_modeset (struct drm_device *dev,int pipe); +extern void intel_prepare_ddi (struct drm_device *dev);/* For use by IVB LP watermark workaround in intel_sprite.c */ extern void intel_update_watermarks (struct drm_device *dev);
Signature · 6 lines
1.7.10 _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 15/24 drm/i915: initialize DDI buffer translations
DDI is introduced starting with Haswell GPU generation. So to simplify its management in the future, we also add intel_ddi.c to hold all the DDI-related items.
Buffer translations for DDI links must be initialized prior to enablement. For FDI and DP, first 9 pairs of values are used to select the connection parameters. HDMI uses the last pair of values and ignores the first 9 pairs. So we program HDMI values in both cases, which allows HDMI to work over both FDI and DP-friendly buffers.
v2: simplify the loop as suggested by Chris Wilson.
--- drivers/gpu/drm/i915/Makefile | 1 + drivers/gpu/drm/i915/intel_ddi.c | 111 ++++++++++++++++++++++++++++++++++ drivers/gpu/drm/i915/intel_display.c | 2 + drivers/gpu/drm/i915/intel_drv.h | 1 + 4 files changed, 115 insertions(+) create mode 100644 drivers/gpu/drm/i915/intel_ddi.c
drivers/gpu/drm/i915/Makefile +1 -0
@@ -19,6 +19,7 @@ i915-y := i915_drv.o i915_dma.o i915_irq.o \ intel_crt.o \ intel_lvds.o \ intel_bios.o \ + intel_ddi.o \ intel_dp.o \ intel_hdmi.o \ intel_sdvo.o \
drivers/gpu/drm/i915/intel_ddi.c new file +111 -0
111 lines not on this page · raw message
drivers/gpu/drm/i915/intel_display.c +2 -0
@@ -6815,6 +6815,8 @@ void intel_modeset_init(struct drm_device *dev)intel_init_pm (dev); +intel_prepare_ddi (dev); +intel_init_display (dev);if (IS_GEN2 (dev)) {
drivers/gpu/drm/i915/intel_drv.h +1 -0
@@ -442,6 +442,7 @@ extern void intel_init_clock_gating(struct drm_device *dev);extern void intel_write_eld (struct drm_encoder *encoder,struct drm_display_mode *mode);extern void intel_cpt_verify_modeset (struct drm_device *dev,int pipe); +extern void intel_prepare_ddi (struct drm_device *dev);/* For use by IVB LP watermark workaround in intel_sprite.c */ extern void intel_update_watermarks (struct drm_device *dev);
Signature · 6 lines
1.7.10 _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 15/24] drm/i915: initialize DDI buffer translations
In reply to Eugeni DodonovQuoted 86 lines · On Thu, 26 Apr 2012 15:21:10 -0300 Eugeni Dodonov <[email protected]>…
DDI is introduced starting with Haswell GPU generation. So to simplify its management in the future, we also add
intel_ddi.cto hold all the DDI-related items.Buffer translations for DDI links must be initialized prior to enablement. For FDI and DP, first 9 pairs of values are used to select the connection parameters. HDMI uses the last pair of values and ignores the first 9 pairs. So we program HDMI values in both cases, which allows HDMI to work over both FDI and DP-friendly buffers.
Signed-off-by Eugeni Dodonov <[email protected]>--- drivers/gpu/drm/i915/Makefile | 1 + drivers/gpu/drm/i915/intel_ddi.c | 111 ++++++++++++++++++++++++++++++++++ drivers/gpu/drm/i915/intel_display.c | 2 + drivers/gpu/drm/i915/intel_drv.h | 1 + 4 files changed, 115 insertions(+) create mode 100644 drivers/gpu/drm/i915/intel_ddi.cdrivers/gpu/drm/i915/Makefile +1
-0@@ -19,6 +19,7 @@ i915-y := i915_drv.o i915_dma.o i915_irq.o \ intel_crt.o \ intel_lvds.o \ intel_bios.o \ + intel_ddi.o \ intel_dp.o \ intel_hdmi.o \ intel_sdvo.o \drivers/gpu/drm/i915/intel_ddi.c new file +49
-0@@ -0,0 +1,111 @@ +/* +* Copyright © 2012 Intel Corporation +* +* Permission is hereby granted, free of charge, to any person obtaining a +* copy of this software and associated documentation files (the "Software"), +* to deal in the Software without restriction, including without limitation +* the rights to use, copy, modify, merge, publish, distribute, sublicense, +* and/or sell copies of the Software, and to permit persons to whom the +* Software is furnished to do so, subject to the following conditions: +* +* The above copyright notice and this permission notice (including the next +* paragraph) shall be included in all copies or substantial portions of the +* Software. +* +* THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR +* IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, +* FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL +* THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER +* LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING +* FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS +* IN THE SOFTWARE. +* +* Authors: +* Eugeni Dodonov <[email protected]> +* +*/ + +#include "i915_drv.h" +#include "intel_drv.h" + +/* HDMI/DVI modes ignore everything but the last 2 items. So we share +* them for both DP and FDI transports, allowing those ports to +* automatically adapt to HDMI connections as well +*/ +static const long hsw_ddi_translations_dp[] = { +0x00FFFFFF ,0x0006000E , +0x00D75FFF ,0x0005000A , +0x00C30FFF ,0x00040006 , +0x80AAAFFF ,0x000B0000 , +0x00FFFFFF ,0x0005000A , +0x00D75FFF ,0x000C0004 , +0x80C30FFF ,0x000B0000 , +0x00FFFFFF ,0x00040006 , +0x80D75FFF ,0x000B0000 , +0x00FFFFFF ,0x00040006 +}; + +static const long hsw_ddi_translations_fdi[] = { +0x00FFFFFF ,0x0007000E ,
drivers/gpu/drm/i915/intel_ddi.c line 59
Quoted 10 lines
drivers/gpu/drm/i915/intel_ddi.c new file +10
-0+0x00D75FFF ,0x000F000A , +0x00C30FFF ,0x00060006 , +0x00AAAFFF ,0x001E0000 , +0x00FFFFFF ,0x000F000A , +0x00D75FFF ,0x00160004 , +0x00C30FFF ,0x001E0000 , +0x00FFFFFF ,0x00060006 , +0x00D75FFF ,0x001E0000 , +0x00FFFFFF ,0x00040006 +};
Ahh these are vswing and preemphasis values for the various types...
Doesn't look like this goes up to the 19 dwords the docs specify?
Quoted 22 lines
drivers/gpu/drm/i915/intel_ddi.c new file +22
-0+ +/* On Haswell, DDI port buffers must be programmed with correct values +* in advance. The buffer values are different for FDI and DP modes, +* but the HDMI/DVI fields are shared among those. So we program the DDI +* in either FDI or DP modes only, as HDMI connections will work with both +* of those +*/ +void intel_prepare_ddi_buffers (struct drm_device *dev,enum port port,bool use_fdi_mode) +{ +struct drm_i915_private *dev_priv = dev->dev_private; +u32 reg; +int i, j; + +DRM_DEBUG_DRIVER ("Initializing DDI buffers for port %c in %s mode\n" , +port_name (port), + use_fdi_mode ?"FDI" :"DP" ); + +WARN ((use_fdi_mode && (port !=PORT_E )), +"Programming port %c in FDI mode, this probably will not work.\n" , +port_name (port)); + +/* Those registers seem to be double-buffered, so write them twice */
drivers/gpu/drm/i915/intel_ddi.c line 91
Quoted 10 lines
drivers/gpu/drm/i915/intel_ddi.c new file +10
-0+for (j=0 ; j <2 ; j++) { +for (i=0 , reg=DDI_BUF_TRANS (port); i <ARRAY_SIZE (hsw_ddi_translations_fdi); i++) { +I915_WRITE (reg, + (use_fdi_mode) ? + hsw_ddi_translations_fdi[i] : + hsw_ddi_translations_dp[i]); + reg +=4 ; + } +udelay (20 ); + }
Usually, double buffered means we need to write a trigger reg somewhere for the values to be latched in, or wait for vblank. What's different here?
Signature · 5 lines
Jesse Barnes, Intel Open Source Technology Center _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 15/24] drm/i915: initialize DDI buffer translations
Quoted 4 lines · Jesse Barnes
Ahh these are vswing and preemphasis values for the various types...
Doesn't look like this goes up to the 19 dwords the docs specify?
The last pair is for HDMI, it is ignored for FDI/DP, so I write it along with all others to already prepare DDI to work in any mode.
Quoted 4 lines
Usually, double buffered means we need to write a trigger reg somewhere for the values to be latched in, or wait for vblank. What's different here?
I'll double-check, it could be possible that they don't need to be double-buffered. In the first series I split the double-buffering part (with a delay) into a separate patch as it made things work more reliable on my machine, but it got merged when I moved everything to intel_ddi.c.
FDI is not yet stable enough, so I need to find if the issues I was having with it are due to that, or we really need the double-writing.
Signature · 2 lines
Eugeni Dodonov <http://eugeni.dodonov.net/>
_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 16/24 drm/i915: support DDI training in FDI mode
In reply to Eugeni DodonovStarting with Haswell, DDI ports can work in FDI mode to support connectivity with the outputs located on the PCH.
This commit adds support for such connections in the intel_ddi module, and provides Haswell-specific functionality to make it work.
--- drivers/gpu/drm/i915/intel_ddi.c | 121 ++++++++++++++++++++++++++++++++++ drivers/gpu/drm/i915/intel_display.c | 3 + drivers/gpu/drm/i915/intel_drv.h | 1 + drivers/gpu/drm/i915/intel_pm.c | 10 +++ 4 files changed, 135 insertions(+)
drivers/gpu/drm/i915/intel_ddi.c +121 -0
@@ -109,3 +109,124 @@ void intel_prepare_ddi(struct drm_device *dev)intel_prepare_ddi_buffers (dev,PORT_E , true); } } + +static const long hsw_ddi_buf_ctl_values[] = { +DDI_BUF_EMP_400MV_0DB_HSW , +DDI_BUF_EMP_400MV_3_5DB_HSW , +DDI_BUF_EMP_400MV_6DB_HSW , +DDI_BUF_EMP_400MV_9_5DB_HSW , +DDI_BUF_EMP_600MV_0DB_HSW , +DDI_BUF_EMP_600MV_3_5DB_HSW , +DDI_BUF_EMP_600MV_6DB_HSW , +DDI_BUF_EMP_800MV_0DB_HSW , +DDI_BUF_EMP_800MV_3_5DB_HSW +}; + + +/* Link training for Haswell DDI port to work in FDI mode */ +static void hsw_fdi_link_train (struct drm_crtc *crtc) +{ +struct drm_device *dev = crtc->dev; +struct drm_i915_private *dev_priv = dev->dev_private; +struct intel_crtc *intel_crtc =to_intel_crtc (crtc); +int pipe = intel_crtc->pipe; +u32 reg, temp, i; + +/* Configure CPU PLL, wait for warmup */ +I915_WRITE (SPLL_CTL , +SPLL_PLL_ENABLE | + SPLL_PLL_FREQ_1350MHz | +SPLL_PLL_SCC ); + +/* Use SPLL to drive the output when in FDI mode */ +I915_WRITE (PORT_CLK_SEL (PORT_E ), +PORT_CLK_SEL_SPLL ); +I915_WRITE (PIPE_CLK_SEL (pipe), +PIPE_CLK_SEL_PORT (PORT_E )); + +udelay (20 ); + +/* Start the training iterating through available voltages and emphasis */ +for (i=0 ; i <ARRAY_SIZE (hsw_ddi_buf_ctl_values); i++) { +/* Configure DP_TP_CTL with auto-training */ +I915_WRITE (DP_TP_CTL (PORT_E ), +DP_TP_CTL_FDI_AUTOTRAIN | +DP_TP_CTL_ENHANCED_FRAME_ENABLE | +DP_TP_CTL_LINK_TRAIN_PAT1 | +DP_TP_CTL_ENABLE ); + +/* Configure and enable DDI_BUF_CTL for DDI E with next voltage */ + temp =I915_READ (DDI_BUF_CTL (PORT_E )); + temp = (temp & ~DDI_BUF_EMP_MASK ); +I915_WRITE (DDI_BUF_CTL (PORT_E ), + temp | +DDI_BUF_CTL_ENABLE | +DDI_PORT_WIDTH_X2 | + hsw_ddi_buf_ctl_values[i]); + +udelay (600 ); + +/* Enable CPU FDI Receiver with auto-training */ + reg =FDI_RX_CTL (pipe); +I915_WRITE (reg, +I915_READ (reg) | +FDI_LINK_TRAIN_AUTO | +FDI_RX_ENABLE | +FDI_LINK_TRAIN_PATTERN_1_CPT | +FDI_RX_ENHANCE_FRAME_ENABLE | +FDI_PORT_WIDTH_2X_LPT | +FDI_RX_PLL_ENABLE ); +POSTING_READ (reg); +udelay (100 ); + + temp =I915_READ (DP_TP_STATUS (PORT_E )); +if (temp &DP_TP_STATUS_AUTOTRAIN_DONE ) { +DRM_DEBUG_DRIVER ("BUF_CTL training done on %d step\n" , i); + +/* Enable normal pixel sending for FDI */ +I915_WRITE (DP_TP_CTL (PORT_E ), +DP_TP_CTL_FDI_AUTOTRAIN | +DP_TP_CTL_LINK_TRAIN_NORMAL | +DP_TP_CTL_ENHANCED_FRAME_ENABLE | +DP_TP_CTL_ENABLE ); + +/* Enable PIPE_DDI_FUNC_CTL for the pipe to work in FDI mode */ + temp =I915_READ (DDI_FUNC_CTL (pipe)); + temp &= ~PIPE_DDI_PORT_MASK ; + temp |=PIPE_DDI_SELECT_PORT (PORT_E ) | +PIPE_DDI_MODE_SELECT_FDI | +PIPE_DDI_FUNC_ENABLE | +PIPE_DDI_PORT_WIDTH_X2 ; +I915_WRITE (DDI_FUNC_CTL (pipe), + temp); +break ; + }else { +DRM_ERROR ("Error training BUF_CTL %d\n" , i); + +/* Disable DP_TP_CTL and FDI_RX_CTL) and retry */ +I915_WRITE (DP_TP_CTL (PORT_E ), +I915_READ (DP_TP_CTL (PORT_E )) & + ~DP_TP_CTL_ENABLE ); +I915_WRITE (FDI_RX_CTL (pipe), +I915_READ (FDI_RX_CTL (pipe)) & + ~FDI_RX_PLL_ENABLE ); +continue ; + } + } + +DRM_DEBUG_KMS ("FDI train done.\n" ); +} + +/* Starting with Haswell, different DDI ports can work in FDI mode for +* connection to the PCH-located connectors. +* +* To avoid exporting generation-specific functions, we abstract the DDI port +* training in FDI mode here. +*/ +void ddi_fdi_link_train (struct drm_crtc *crtc) +{ +struct drm_device *dev = crtc->dev; + +if (IS_HASWELL (dev)) +hsw_fdi_link_train (crtc); +}
drivers/gpu/drm/i915/intel_display.c +3 -0
@@ -6617,6 +6617,9 @@ static void intel_init_display(struct drm_device *dev)/* FIXME: detect B0+ stepping and use auto training */ dev_priv->display.fdi_link_train = ivb_manual_fdi_link_train; dev_priv->display.write_eld = ironlake_write_eld; + }else if (IS_HASWELL (dev)) { + dev_priv->display.fdi_link_train = ddi_fdi_link_train; + dev_priv->display.write_eld = ironlake_write_eld; }else dev_priv->display.update_wm =NULL ; }else if (IS_VALLEYVIEW (dev)) {
drivers/gpu/drm/i915/intel_drv.h +1 -0
@@ -443,6 +443,7 @@ extern void intel_write_eld(struct drm_encoder *encoder, struct drm_display_mode *mode);extern void intel_cpt_verify_modeset (struct drm_device *dev,int pipe);extern void intel_prepare_ddi (struct drm_device *dev); +extern void ddi_fdi_link_train (struct drm_crtc *crtc);/* For use by IVB LP watermark workaround in intel_sprite.c */ extern void intel_update_watermarks (struct drm_device *dev);
drivers/gpu/drm/i915/intel_pm.c +10 -0
@@ -3055,6 +3055,16 @@ void intel_init_pm(struct drm_device *dev) dev_priv->display.update_wm =NULL ; } dev_priv->display.init_clock_gating = ivybridge_init_clock_gating; + }else if (IS_HASWELL (dev)) { +if (SNB_READ_WM0_LATENCY ()) { + dev_priv->display.update_wm = sandybridge_update_wm; + dev_priv->display.update_sprite_wm = sandybridge_update_sprite_wm; + }else { +DRM_DEBUG_KMS ("Failed to read display plane latency. " +"Disable CxSR\n" ); + dev_priv->display.update_wm =NULL ; + } + dev_priv->display.init_clock_gating = ivybridge_init_clock_gating; }else dev_priv->display.update_wm =NULL ; }else if (IS_VALLEYVIEW (dev)) {
Signature · 1 line
1.7.10
Re: [PATCH 16/24] drm/i915: support DDI training in FDI mode
Quoted 133 lines · Eugeni Dodonov
Starting with Haswell, DDI ports can work in FDI mode to support connectivity with the outputs located on the PCH.
This commit adds support for such connections in the
intel_ddimodule, and provides Haswell-specific functionality to make it work.Signed-off-by Eugeni Dodonov <[email protected]>--- drivers/gpu/drm/i915/intel_ddi.c | 121 ++++++++++++++++++++++++++++++++++ drivers/gpu/drm/i915/intel_display.c | 3 + drivers/gpu/drm/i915/intel_drv.h | 1 + drivers/gpu/drm/i915/intel_pm.c | 10 +++ 4 files changed, 135 insertions(+)drivers/gpu/drm/i915/intel_ddi.c +111
-0@@ -109,3 +109,124 @@ void intel_prepare_ddi(struct drm_device *dev)intel_prepare_ddi_buffers (dev,PORT_E , true); } } + +static const long hsw_ddi_buf_ctl_values[] = { +DDI_BUF_EMP_400MV_0DB_HSW , +DDI_BUF_EMP_400MV_3_5DB_HSW , +DDI_BUF_EMP_400MV_6DB_HSW , +DDI_BUF_EMP_400MV_9_5DB_HSW , +DDI_BUF_EMP_600MV_0DB_HSW , +DDI_BUF_EMP_600MV_3_5DB_HSW , +DDI_BUF_EMP_600MV_6DB_HSW , +DDI_BUF_EMP_800MV_0DB_HSW , +DDI_BUF_EMP_800MV_3_5DB_HSW +}; + + +/* Link training for Haswell DDI port to work in FDI mode */ +static void hsw_fdi_link_train (struct drm_crtc *crtc) +{ +struct drm_device *dev = crtc->dev; +struct drm_i915_private *dev_priv = dev->dev_private; +struct intel_crtc *intel_crtc =to_intel_crtc (crtc); +int pipe = intel_crtc->pipe; +u32 reg, temp, i; + +/* Configure CPU PLL, wait for warmup */ +I915_WRITE (SPLL_CTL , +SPLL_PLL_ENABLE | + SPLL_PLL_FREQ_1350MHz | +SPLL_PLL_SCC ); + +/* Use SPLL to drive the output when in FDI mode */ +I915_WRITE (PORT_CLK_SEL (PORT_E ), +PORT_CLK_SEL_SPLL ); +I915_WRITE (PIPE_CLK_SEL (pipe), +PIPE_CLK_SEL_PORT (PORT_E )); + +udelay (20 ); + +/* Start the training iterating through available voltages and emphasis */ +for (i=0 ; i <ARRAY_SIZE (hsw_ddi_buf_ctl_values); i++) { +/* Configure DP_TP_CTL with auto-training */ +I915_WRITE (DP_TP_CTL (PORT_E ), +DP_TP_CTL_FDI_AUTOTRAIN | +DP_TP_CTL_ENHANCED_FRAME_ENABLE | +DP_TP_CTL_LINK_TRAIN_PAT1 | +DP_TP_CTL_ENABLE ); + +/* Configure and enable DDI_BUF_CTL for DDI E with next voltage */ + temp =I915_READ (DDI_BUF_CTL (PORT_E )); + temp = (temp & ~DDI_BUF_EMP_MASK ); +I915_WRITE (DDI_BUF_CTL (PORT_E ), + temp | +DDI_BUF_CTL_ENABLE | +DDI_PORT_WIDTH_X2 | + hsw_ddi_buf_ctl_values[i]); + +udelay (600 ); + +/* Enable CPU FDI Receiver with auto-training */ + reg =FDI_RX_CTL (pipe); +I915_WRITE (reg, +I915_READ (reg) | +FDI_LINK_TRAIN_AUTO | +FDI_RX_ENABLE | +FDI_LINK_TRAIN_PATTERN_1_CPT | +FDI_RX_ENHANCE_FRAME_ENABLE | +FDI_PORT_WIDTH_2X_LPT | +FDI_RX_PLL_ENABLE ); +POSTING_READ (reg); +udelay (100 ); + + temp =I915_READ (DP_TP_STATUS (PORT_E )); +if (temp &DP_TP_STATUS_AUTOTRAIN_DONE ) { +DRM_DEBUG_DRIVER ("BUF_CTL training done on %d step\n" , i); + +/* Enable normal pixel sending for FDI */ +I915_WRITE (DP_TP_CTL (PORT_E ), +DP_TP_CTL_FDI_AUTOTRAIN | +DP_TP_CTL_LINK_TRAIN_NORMAL | +DP_TP_CTL_ENHANCED_FRAME_ENABLE | +DP_TP_CTL_ENABLE ); + +/* Enable PIPE_DDI_FUNC_CTL for the pipe to work in FDI mode */ + temp =I915_READ (DDI_FUNC_CTL (pipe)); + temp &= ~PIPE_DDI_PORT_MASK ; + temp |=PIPE_DDI_SELECT_PORT (PORT_E ) | +PIPE_DDI_MODE_SELECT_FDI | +PIPE_DDI_FUNC_ENABLE | +PIPE_DDI_PORT_WIDTH_X2 ; +I915_WRITE (DDI_FUNC_CTL (pipe), + temp); +break ; + }else { +DRM_ERROR ("Error training BUF_CTL %d\n" , i); + +/* Disable DP_TP_CTL and FDI_RX_CTL) and retry */ +I915_WRITE (DP_TP_CTL (PORT_E ), +I915_READ (DP_TP_CTL (PORT_E )) & + ~DP_TP_CTL_ENABLE ); +I915_WRITE (FDI_RX_CTL (pipe), +I915_READ (FDI_RX_CTL (pipe)) & + ~FDI_RX_PLL_ENABLE ); +continue ; + } + } + +DRM_DEBUG_KMS ("FDI train done.\n" ); +} + +/* Starting with Haswell, different DDI ports can work in FDI mode for +* connection to the PCH-located connectors. +*
drivers/gpu/drm/i915/intel_ddi.c void intel_prepare_ddi(struct drm_device *dev) · line 232
Quoted 10 lines
drivers/gpu/drm/i915/intel_ddi.c +10
-0+* To avoid exporting generation-specific functions, we abstract the DDI port +* training in FDI mode here. +*/ +void ddi_fdi_link_train (struct drm_crtc *crtc) +{ +struct drm_device *dev = crtc->dev; + +if (IS_HASWELL (dev)) +hsw_fdi_link_train (crtc); +}
Can't we put this directly into the vtable? Imo the indirection here adds nothing. (I also like to bikeshed about the ddi prefix, atm almost all of the extern functions start with i915_ intel_ ;-)
drivers/gpu/drm/i915/intel_display.c static void intel_init_display(struct drm_device *dev) · line 6622
Quoted 11 lines
drivers/gpu/drm/i915/intel_display.c +3
-0@@ -6617,6 +6617,9 @@ static void intel_init_display(struct drm_device *dev)/* FIXME: detect B0+ stepping and use auto training */ dev_priv->display.fdi_link_train = ivb_manual_fdi_link_train; dev_priv->display.write_eld = ironlake_write_eld; + }else if (IS_HASWELL (dev)) { + dev_priv->display.fdi_link_train = ddi_fdi_link_train; + dev_priv->display.write_eld = ironlake_write_eld;
The write_eld asignment smells like rebase fail.
Quoted 26 lines
drivers/gpu/drm/i915/intel_display.c +0
-0}else dev_priv->display.update_wm =NULL ; }else if (IS_VALLEYVIEW (dev)) {drivers/gpu/drm/i915/intel_drv.h +1
-0@@ -443,6 +443,7 @@ extern void intel_write_eld(struct drm_encoder *encoder, struct drm_display_mode *mode);extern void intel_cpt_verify_modeset (struct drm_device *dev,int pipe);extern void intel_prepare_ddi (struct drm_device *dev); +extern void ddi_fdi_link_train (struct drm_crtc *crtc);/* For use by IVB LP watermark workaround in intel_sprite.c */ extern void intel_update_watermarks (struct drm_device *dev);drivers/gpu/drm/i915/intel_pm.c +3
-0@@ -3055,6 +3055,16 @@ void intel_init_pm(struct drm_device *dev) dev_priv->display.update_wm =NULL ; } dev_priv->display.init_clock_gating = ivybridge_init_clock_gating; + }else if (IS_HASWELL (dev)) { +if (SNB_READ_WM0_LATENCY ()) { + dev_priv->display.update_wm = sandybridge_update_wm;
drivers/gpu/drm/i915/intel_pm.c void intel_init_pm(struct drm_device *dev) · line 3070
Quoted 10 lines
drivers/gpu/drm/i915/intel_pm.c +7
-0+ dev_priv->display.update_sprite_wm = sandybridge_update_sprite_wm; + }else { +DRM_DEBUG_KMS ("Failed to read display plane latency. " +"Disable CxSR\n" ); + dev_priv->display.update_wm =NULL ; + } + dev_priv->display.init_clock_gating = ivybridge_init_clock_gating; }else dev_priv->display.update_wm =NULL ; }else if (IS_VALLEYVIEW (dev)) {
This hunk here smells like rebase fail ...
-Daniel
Signature · 3 lines
Daniel Vetter Mail: [email protected] Mobile: +41 (0)79 365 57 48
PATCH 17/24 drm/i915: disable pipe DDI function when disabling pipe
In reply to Eugeni Dodonov--- drivers/gpu/drm/i915/intel_display.c | 10 ++++++++++ 1 file changed, 10 insertions(+)
drivers/gpu/drm/i915/intel_display.c +10 -0
@@ -1627,6 +1627,16 @@ static void intel_disable_pipe(struct drm_i915_private *dev_priv,I915_WRITE (reg, val & ~PIPECONF_ENABLE );intel_wait_for_pipe_off (dev_priv->dev, pipe); + +/* On HSW, disable pipe DDI function the pipe */ +if (IS_HASWELL (dev_priv->dev)) { + val =I915_READ (DDI_FUNC_CTL (pipe)); + val &= ~PIPE_DDI_PORT_MASK ; + val &= ~PIPE_DDI_FUNC_ENABLE ; +I915_WRITE (DDI_FUNC_CTL (pipe), + val); + } + }/*
Signature · 1 line
1.7.10
Re: [PATCH 17/24] drm/i915: disable pipe DDI function when disabling pipe
Quoted 16 lines · On Thu, 26 Apr 2012 15:21:12 -0300 Eugeni Dodonov <[email protected]>…
Signed-off-by Eugeni Dodonov <[email protected]>--- drivers/gpu/drm/i915/intel_display.c | 10 ++++++++++ 1 file changed, 10 insertions(+)drivers/gpu/drm/i915/intel_display.c +3
-0@@ -1627,6 +1627,16 @@ static void intel_disable_pipe(struct drm_i915_private *dev_priv,I915_WRITE (reg, val & ~PIPECONF_ENABLE );intel_wait_for_pipe_off (dev_priv->dev, pipe); + +/* On HSW, disable pipe DDI function the pipe */ +if (IS_HASWELL (dev_priv->dev)) {
drivers/gpu/drm/i915/intel_display.c static void intel_disable_pipe(struct drm_i915_private *dev_priv, · line 1642
Quoted 10 lines
drivers/gpu/drm/i915/intel_display.c +7
-0+ val =I915_READ (DDI_FUNC_CTL (pipe)); + val &= ~PIPE_DDI_PORT_MASK ; + val &= ~PIPE_DDI_FUNC_ENABLE ; +I915_WRITE (DDI_FUNC_CTL (pipe), + val); + } + }/*
Looks like we could just write 0 here?
Signature · 1 line
Jesse Barnes, Intel Open Source Technology Center
PATCH 18/24 drm/i915: program iCLKIP on Lynx Point
In reply to Eugeni DodonovThe iCLKIP clock is used to drive the VGA pixel clock on the PCH. In order to do so, it must be programmed to properly do the clock ticks according to the divisor, phase direction, phase increments and a special auxiliary divisor for 20MHz clock.
Those values can be programmed individually, by doing some math; or we could use a pre-defined table of values for each modeset. For speed and simplification, the idea was to just adopt the table of valid pixel clocks and select the matching iCLKIP values from there.
As a possible idea for the future, it would be possible to add a fallback and calculate those values manually in case no match is found. But I don't think we'll encounter a mode not covered by those table, and VGA is pretty much going away in the future anyway.
--- drivers/gpu/drm/i915/intel_display.c | 319 +++++++++++++++++++++++++++++++++- 1 file changed, 314 insertions(+), 5 deletions(-)
drivers/gpu/drm/i915/intel_display.c +314 -5
@@ -2702,6 +2702,308 @@ static bool intel_crtc_driving_pch(struct drm_crtc *crtc)return true; } +/* Available pixel clock values */ +struct iclk_vga_clock { +u32 clock; +u16 auxdiv; +u16 divsel; +u16 phasedir; +u16 phaseinc; +}; + +static const struct iclk_vga_clock iclk_vga_clock_table[] = { + {20000 ,1 ,0x41 ,0 ,0x20 },/* 20000 ppm=0 */ + {21000 ,0 ,0x7E ,0 ,0x25 },/* 20999 ppm=-53 */ + {21912 ,0 ,0x79 ,0 ,0x0E },/* 21912 ppm=12 */ + {22000 ,0 ,0x78 ,0 ,0x2F },/* 21999 ppm=-58 */ + {23000 ,0 ,0x73 ,0 ,0x19 },/* 23000 ppm=6 */ + {24000 ,0 ,0x6E ,0 ,0x20 },/* 24000 ppm=0 */ + {25000 ,0 ,0x6A ,0 ,0x00 },/* 25000 ppm=0 */ + {25175 ,0 ,0x69 ,0 ,0x10 },/* 25175 ppm=-7 */ + {25200 ,0 ,0x69 ,0 ,0x09 },/* 25201 ppm=21 */ + {26000 ,0 ,0x66 ,1 ,0x0A },/* 26001 ppm=24 */ + {27000 ,0 ,0x62 ,0 ,0x00 },/* 27000 ppm=0 */ + {27027 ,0 ,0x62 ,1 ,0x06 },/* 27025 ppm=-62 */ + {27500 ,0 ,0x60 ,0 ,0x0C },/* 27498 ppm=-58 */ + {28000 ,0 ,0x5E ,0 ,0x1B },/* 28002 ppm=70 */ + {28320 ,0 ,0x5D ,0 ,0x16 },/* 28319 ppm=-50 */ + {28322 ,0 ,0x5D ,0 ,0x15 },/* 28323 ppm=44 */ + {29000 ,0 ,0x5B ,0 ,0x07 },/* 28998 ppm=-64 */ + {30000 ,0 ,0x58 ,0 ,0x00 },/* 30000 ppm=0 */ + {31000 ,0 ,0x55 ,0 ,0x06 },/* 31001 ppm=35 */ + {31500 ,0 ,0x54 ,1 ,0x12 },/* 31498 ppm=-53 */ + {32000 ,0 ,0x52 ,0 ,0x18 },/* 32000 ppm=0 */ + {32500 ,0 ,0x51 ,0 ,0x05 },/* 32500 ppm=-15 */ + {33000 ,0 ,0x50 ,1 ,0x0C },/* 33002 ppm=70 */ + {34000 ,0 ,0x4D ,0 ,0x1A },/* 34002 ppm=70 */ + {35000 ,0 ,0x4B ,0 ,0x09 },/* 35001 ppm=29 */ + {35500 ,0 ,0x4A ,0 ,0x04 },/* 35497 ppm=-82 */ + {36000 ,0 ,0x49 ,0 ,0x00 },/* 36000 ppm=0 */ + {37000 ,0 ,0x47 ,1 ,0x02 },/* 37002 ppm=58 */ + {38000 ,0 ,0x45 ,0 ,0x03 },/* 38003 ppm=82 */ + {39000 ,0 ,0x43 ,0 ,0x0F },/* 38998 ppm=-53 */ + {40000 ,0 ,0x41 ,0 ,0x20 },/* 40000 ppm=0 */ + {40500 ,0 ,0x41 ,1 ,0x15 },/* 40497 ppm=-79 */ + {40541 ,0 ,0x41 ,1 ,0x1A },/* 40544 ppm=95 */ + {41000 ,0 ,0x40 ,1 ,0x09 },/* 40996 ppm=-87 */ + {41540 ,0 ,0x3F ,0 ,0x00 },/* 41538 ppm=-38 */ + {42000 ,0 ,0x3E ,0 ,0x12 },/* 42003 ppm=70 */ + {43000 ,0 ,0x3D ,1 ,0x0D },/* 42996 ppm=-99 */ + {43163 ,0 ,0x3D ,1 ,0x1D },/* 43168 ppm=108 */ + {44000 ,0 ,0x3B ,0 ,0x17 },/* 44003 ppm=70 */ + {44900 ,0 ,0x3A ,0 ,0x09 },/* 44895 ppm=-117 */ + {45000 ,0 ,0x3A ,0 ,0x00 },/* 45000 ppm=0 */ + {46000 ,0 ,0x39 ,1 ,0x13 },/* 45994 ppm=-128 */ + {47000 ,0 ,0x37 ,0 ,0x1D },/* 46995 ppm=-110 */ + {48000 ,0 ,0x36 ,0 ,0x10 },/* 48000 ppm=0 */ + {49000 ,0 ,0x35 ,0 ,0x07 },/* 48993 ppm=-134 */ + {49500 ,0 ,0x35 ,1 ,0x1D },/* 49499 ppm=-27 */ + {50000 ,0 ,0x34 ,0 ,0x00 },/* 50000 ppm=0 */ + {51000 ,0 ,0x33 ,1 ,0x04 },/* 51004 ppm=70 */ + {52000 ,0 ,0x32 ,1 ,0x05 },/* 52001 ppm=24 */ + {52406 ,0 ,0x32 ,1 ,0x1F },/* 52411 ppm=101 */ + {53000 ,0 ,0x31 ,1 ,0x04 },/* 53006 ppm=116 */ + {54000 ,0 ,0x30 ,0 ,0x00 },/* 54000 ppm=0 */ + {54054 ,0 ,0x30 ,1 ,0x03 },/* 54051 ppm=-62 */ + {55000 ,0 ,0x2F ,0 ,0x06 },/* 54997 ppm=-58 */ + {56000 ,0 ,0x2E ,0 ,0x0E },/* 55995 ppm=-93 */ + {56250 ,0 ,0x2E ,0 ,0x00 },/* 56250 ppm=0 */ + {57000 ,0 ,0x2D ,0 ,0x18 },/* 56992 ppm=-139 */ + {58000 ,0 ,0x2D ,1 ,0x1D },/* 58006 ppm=105 */ + {59000 ,0 ,0x2C ,1 ,0x0F },/* 58996 ppm=-64 */ + {60000 ,0 ,0x2B ,0 ,0x00 },/* 60000 ppm=0 */ + {61000 ,0 ,0x2A ,0 ,0x11 },/* 60995 ppm=-76 */ + {62000 ,0 ,0x2A ,1 ,0x1D },/* 62002 ppm=35 */ + {63000 ,0 ,0x29 ,1 ,0x09 },/* 62997 ppm=-53 */ + {64000 ,0 ,0x28 ,0 ,0x0C },/* 64000 ppm=0 */ + {65000 ,0 ,0x28 ,1 ,0x1E },/* 65011 ppm=174 */ + {66000 ,0 ,0x27 ,1 ,0x06 },/* 66005 ppm=70 */ + {66667 ,0 ,0x26 ,0 ,0x20 },/* 66667 ppm=-5 */ + {67000 ,0 ,0x26 ,0 ,0x13 },/* 67003 ppm=41 */ + {68000 ,0 ,0x26 ,1 ,0x13 },/* 68005 ppm=70 */ + {68179 ,0 ,0x26 ,1 ,0x19 },/* 68166 ppm=-196 */ + {69000 ,0 ,0x25 ,0 ,0x08 },/* 69010 ppm=139 */ + {70000 ,0 ,0x25 ,1 ,0x1B },/* 69988 ppm=-174 */ + {71000 ,0 ,0x24 ,0 ,0x02 },/* 70994 ppm=-82 */ + {72000 ,0 ,0x23 ,0 ,0x20 },/* 72000 ppm=0 */ + {73000 ,0 ,0x23 ,1 ,0x01 },/* 73004 ppm=53 */ + {74000 ,0 ,0x22 ,0 ,0x1F },/* 74004 ppm=58 */ + {74175 ,0 ,0x22 ,0 ,0x1A },/* 74163 ppm=-161 */ + {74250 ,0 ,0x22 ,0 ,0x17 },/* 74259 ppm=118 */ + {74481 ,0 ,0x22 ,0 ,0x10 },/* 74483 ppm=24 */ + {75000 ,0 ,0x22 ,0 ,0x00 },/* 75000 ppm=0 */ + {76000 ,0 ,0x22 ,1 ,0x1E },/* 75989 ppm=-139 */ + {77000 ,0 ,0x21 ,0 ,0x04 },/* 77005 ppm=70 */ + {78000 ,0 ,0x21 ,1 ,0x19 },/* 78014 ppm=174 */ + {78750 ,0 ,0x20 ,0 ,0x12 },/* 78760 ppm=131 */ + {79000 ,0 ,0x20 ,0 ,0x0B },/* 79012 ppm=157 */ + {80000 ,0 ,0x20 ,1 ,0x10 },/* 80000 ppm=0 */ + {81000 ,0 ,0x1F ,0 ,0x15 },/* 81013 ppm=157 */ + {81081 ,0 ,0x1F ,0 ,0x13 },/* 81089 ppm=95 */ + {81624 ,0 ,0x1F ,0 ,0x05 },/* 81625 ppm=12 */ + {82000 ,0 ,0x1F ,1 ,0x05 },/* 82012 ppm=151 */ + {83000 ,0 ,0x1F ,1 ,0x1E },/* 82997 ppm=-35 */ + {83950 ,0 ,0x1E ,0 ,0x0A },/* 83965 ppm=179 */ + {84000 ,0 ,0x1E ,0 ,0x09 },/* 84006 ppm=70 */ + {85000 ,0 ,0x1E ,1 ,0x0F },/* 84998 ppm=-29 */ + {86000 ,0 ,0x1D ,0 ,0x19 },/* 86013 ppm=151 */ + {87000 ,0 ,0x1D ,0 ,0x02 },/* 87009 ppm=105 */ + {88000 ,0 ,0x1D ,1 ,0x14 },/* 87984 ppm=-186 */ + {89000 ,0 ,0x1C ,0 ,0x16 },/* 88980 ppm=-220 */ + {90000 ,0 ,0x1C ,0 ,0x00 },/* 90000 ppm=0 */ + {91000 ,0 ,0x1C ,1 ,0x15 },/* 90995 ppm=-53 */ + {92000 ,0 ,0x1B ,0 ,0x16 },/* 92013 ppm=139 */ + {93000 ,0 ,0x1B ,0 ,0x02 },/* 93003 ppm=35 */ + {94000 ,0 ,0x1B ,1 ,0x12 },/* 94015 ppm=163 */ + {94500 ,0 ,0x1B ,1 ,0x1B },/* 94478 ppm=-235 */ + {95000 ,0 ,0x1A ,0 ,0x1B },/* 94997 ppm=-29 */ + {95654 ,0 ,0x1A ,0 ,0x0F },/* 95628 ppm=-271 */ + {96000 ,0 ,0x1A ,0 ,0x08 },/* 96000 ppm=0 */ + {97000 ,0 ,0x1A ,1 ,0x0B },/* 97024 ppm=249 */ + {98000 ,0 ,0x1A ,1 ,0x1D },/* 98015 ppm=151 */ + {99000 ,0 ,0x19 ,0 ,0x11 },/* 99026 ppm=261 */ + {100000 ,0 ,0x19 ,0 ,0x00 },/* 100000 ppm=0 */ + {101000 ,0 ,0x19 ,1 ,0x11 },/* 100994 ppm=-64 */ + {102000 ,0 ,0x18 ,0 ,0x1E },/* 102007 ppm=70 */ + {103000 ,0 ,0x18 ,0 ,0x0E },/* 102980 ppm=-197 */ + {104000 ,0 ,0x18 ,1 ,0x02 },/* 103971 ppm=-278 */ + {105000 ,0 ,0x18 ,1 ,0x12 },/* 104982 ppm=-174 */ + {106000 ,0 ,0x17 ,0 ,0x1E },/* 106012 ppm=116 */ + {107000 ,0 ,0x17 ,0 ,0x0F },/* 106997 ppm=-29 */ + {107214 ,0 ,0x17 ,0 ,0x0C },/* 107196 ppm=-168 */ + {108000 ,0 ,0x17 ,0 ,0x00 },/* 108000 ppm=0 */ + {109000 ,0 ,0x17 ,1 ,0x0F },/* 109022 ppm=203 */ + {110000 ,0 ,0x17 ,1 ,0x1D },/* 109994 ppm=-58 */ + {110013 ,0 ,0x17 ,1 ,0x1D },/* 109994 ppm=-177 */ + {111000 ,0 ,0x16 ,0 ,0x15 },/* 110983 ppm=-157 */ + {111263 ,0 ,0x16 ,0 ,0x11 },/* 111269 ppm=55 */ + {111375 ,0 ,0x16 ,0 ,0x10 },/* 111340 ppm=-313 */ + {112000 ,0 ,0x16 ,0 ,0x07 },/* 111990 ppm=-93 */ + {113000 ,0 ,0x16 ,1 ,0x07 },/* 113015 ppm=134 */ + {113309 ,0 ,0x16 ,1 ,0x0B },/* 113311 ppm=22 */ + {113100 ,0 ,0x16 ,1 ,0x08 },/* 113089 ppm=-98 */ + {114000 ,0 ,0x16 ,1 ,0x14 },/* 113984 ppm=-139 */ + {115000 ,0 ,0x15 ,0 ,0x1F },/* 114970 ppm=-261 */ + {116000 ,0 ,0x15 ,0 ,0x12 },/* 115973 ppm=-232 */ + {117000 ,0 ,0x15 ,0 ,0x05 },/* 116994 ppm=-53 */ + {118000 ,0 ,0x15 ,1 ,0x08 },/* 118033 ppm=278 */ + {119000 ,0 ,0x15 ,1 ,0x14 },/* 119008 ppm=70 */ + {119651 ,0 ,0x15 ,1 ,0x1C },/* 119668 ppm=139 */ + {120000 ,0 ,0x14 ,0 ,0x20 },/* 120000 ppm=0 */ + {121000 ,0 ,0x14 ,0 ,0x14 },/* 121008 ppm=70 */ + {122000 ,0 ,0x14 ,0 ,0x08 },/* 122034 ppm=278 */ + {122614 ,0 ,0x14 ,0 ,0x01 },/* 122640 ppm=214 */ + {123000 ,0 ,0x14 ,1 ,0x03 },/* 122989 ppm=-87 */ + {123379 ,0 ,0x14 ,1 ,0x07 },/* 123340 ppm=-313 */ + {124000 ,0 ,0x14 ,1 ,0x0E },/* 123960 ppm=-324 */ + {125000 ,0 ,0x14 ,1 ,0x1A },/* 125036 ppm=290 */ + {126000 ,0 ,0x13 ,0 ,0x1B },/* 126039 ppm=313 */ + {127000 ,0 ,0x13 ,0 ,0x11 },/* 126965 ppm=-272 */ + {128000 ,0 ,0x13 ,0 ,0x06 },/* 128000 ppm=0 */ + {129000 ,0 ,0x13 ,1 ,0x04 },/* 128955 ppm=-348 */ + {129859 ,0 ,0x13 ,1 ,0x0D },/* 129827 ppm=-245 */ + {130000 ,0 ,0x13 ,1 ,0x0F },/* 130023 ppm=174 */ + {131000 ,0 ,0x13 ,1 ,0x19 },/* 131008 ppm=64 */ + {131850 ,0 ,0x12 ,0 ,0x1F },/* 131808 ppm=-321 */ + {132000 ,0 ,0x12 ,0 ,0x1D },/* 132009 ppm=70 */ + {133000 ,0 ,0x12 ,0 ,0x13 },/* 133025 ppm=192 */ + {133330 ,0 ,0x12 ,0 ,0x10 },/* 133333 ppm=26 */ + {134000 ,0 ,0x12 ,0 ,0x0A },/* 133953 ppm=-348 */ + {135000 ,0 ,0x12 ,0 ,0x00 },/* 135000 ppm=0 */ + {136000 ,0 ,0x12 ,1 ,0x09 },/* 135956 ppm=-324 */ + {137000 ,0 ,0x12 ,1 ,0x13 },/* 137034 ppm=249 */ + {138000 ,0 ,0x12 ,1 ,0x1C },/* 138019 ppm=139 */ + {139000 ,0 ,0x11 ,0 ,0x1B },/* 139019 ppm=134 */ + {139050 ,0 ,0x11 ,0 ,0x1B },/* 139019 ppm=-227 */ + {139054 ,0 ,0x11 ,0 ,0x1B },/* 139019 ppm=-256 */ + {140000 ,0 ,0x11 ,0 ,0x12 },/* 140032 ppm=232 */ + {141000 ,0 ,0x11 ,0 ,0x0A },/* 140946 ppm=-382 */ + {142000 ,0 ,0x11 ,0 ,0x01 },/* 141988 ppm=-82 */ + {143000 ,0 ,0x11 ,1 ,0x08 },/* 143046 ppm=325 */ + {143472 ,0 ,0x11 ,1 ,0x0C },/* 143522 ppm=346 */ + {144000 ,0 ,0x11 ,1 ,0x10 },/* 144000 ppm=0 */ + {145000 ,0 ,0x11 ,1 ,0x18 },/* 144966 ppm=-232 */ + {146000 ,0 ,0x10 ,0 ,0x20 },/* 145946 ppm=-371 */ + {147000 ,0 ,0x10 ,0 ,0x18 },/* 146939 ppm=-417 */ + {147891 ,0 ,0x10 ,0 ,0x10 },/* 147945 ppm=367 */ + {148000 ,0 ,0x10 ,0 ,0x10 },/* 147945 ppm=-371 */ + {148350 ,0 ,0x10 ,0 ,0x0D },/* 148326 ppm=-161 */ + {148500 ,0 ,0x10 ,0 ,0x0C },/* 148454 ppm=-313 */ + {149000 ,0 ,0x10 ,0 ,0x08 },/* 148966 ppm=-232 */ + {150000 ,0 ,0x10 ,0 ,0x00 },/* 150000 ppm=0 */ + {151000 ,0 ,0x10 ,1 ,0x08 },/* 151049 ppm=325 */ + {152000 ,0 ,0x10 ,1 ,0x0F },/* 151979 ppm=-139 */ + {152280 ,0 ,0x10 ,1 ,0x11 },/* 152247 ppm=-219 */ + {153000 ,0 ,0x10 ,1 ,0x17 },/* 153056 ppm=365 */ + {154000 ,0 ,0x10 ,1 ,0x1E },/* 154011 ppm=70 */ + {155000 ,0 ,0x0F ,0 ,0x1B },/* 154978 ppm=-145 */ + {156000 ,0 ,0x0F ,0 ,0x14 },/* 155957 ppm=-278 */ + {157000 ,0 ,0x0F ,0 ,0x0D },/* 156948 ppm=-330 */ + {157500 ,0 ,0x0F ,0 ,0x09 },/* 157521 ppm=131 */ + {158000 ,0 ,0x0F ,0 ,0x06 },/* 157952 ppm=-301 */ + {159000 ,0 ,0x0F ,1 ,0x01 },/* 158970 ppm=-191 */ + {160000 ,0 ,0x0F ,1 ,0x08 },/* 160000 ppm=0 */ + {161000 ,0 ,0x0F ,1 ,0x0F },/* 161044 ppm=273 */ + {162000 ,0 ,0x0F ,1 ,0x15 },/* 161949 ppm=-313 */ + {163000 ,0 ,0x0F ,1 ,0x1C },/* 163019 ppm=116 */ + {164000 ,0 ,0x0E ,0 ,0x1E },/* 163947 ppm=-324 */ + {165000 ,0 ,0x0E ,0 ,0x17 },/* 165043 ppm=261 */ + {166000 ,0 ,0x0E ,0 ,0x11 },/* 165994 ppm=-35 */ + {167000 ,0 ,0x0E ,0 ,0x0B },/* 166957 ppm=-261 */ + {168000 ,0 ,0x0E ,0 ,0x05 },/* 167930 ppm=-417 */ + {169000 ,0 ,0x0E ,1 ,0x02 },/* 169080 ppm=475 */ + {169128 ,0 ,0x0E ,1 ,0x02 },/* 169080 ppm=-283 */ + {170000 ,0 ,0x0E ,1 ,0x08 },/* 170079 ppm=464 */ + {171000 ,0 ,0x0E ,1 ,0x0D },/* 170920 ppm=-469 */ + {172000 ,0 ,0x0E ,1 ,0x13 },/* 171940 ppm=-348 */ + {172800 ,0 ,0x0E ,1 ,0x18 },/* 172800 ppm=0 */ + {173000 ,0 ,0x0E ,1 ,0x19 },/* 172973 ppm=-157 */ + {174000 ,0 ,0x0E ,1 ,0x1F },/* 174018 ppm=105 */ + {174787 ,0 ,0x0D ,0 ,0x1D },/* 174722 ppm=-373 */ + {175000 ,0 ,0x0D ,0 ,0x1B },/* 175076 ppm=435 */ + {175500 ,0 ,0x0D ,0 ,0x19 },/* 175431 ppm=-391 */ + {176000 ,0 ,0x0D ,0 ,0x16 },/* 175967 ppm=-186 */ + {177000 ,0 ,0x0D ,0 ,0x10 },/* 177049 ppm=278 */ + {178000 ,0 ,0x0D ,0 ,0x0B },/* 177961 ppm=-220 */ + {179000 ,0 ,0x0D ,0 ,0x05 },/* 179067 ppm=377 */ + {180000 ,0 ,0x0D ,0 ,0x00 },/* 180000 ppm=0 */ +}; + +/* Program iCLKIP clock to the desired frequency */ +static void lpt_program_iclkip (struct drm_crtc *crtc) +{ +struct drm_device *dev = crtc->dev; +struct drm_i915_private *dev_priv = dev->dev_private; +u32 auxdiv=0 , divsel=0 , phasedir=0 , phaseinc=0 , valid=0 ; +u32 temp, i; + +/* Ungate pixel clock */ +I915_WRITE (PIXCLK_GATE ,PIXCLK_GATE_GATE ); + +/* Disable SSCCTL */ +intel_sbi_write (dev_priv,SBI_SSCCTL6 , +intel_sbi_read (dev_priv,SBI_SSCCTL6 ) | +SBI_SSCCTL_DISABLE ); + +/* Calculating clock values for iCLKIP */ +for (i=0 ; i <ARRAY_SIZE (iclk_vga_clock_table); i++) { +if (crtc->mode.clock == iclk_vga_clock_table[i].clock) { +DRM_DEBUG_KMS ("iCLKIP clock: found settings for %dKHz refresh rate: auxdiv=%x, divsel=%x, phasedir=%x, phaseinc=%x\n" , + crtc->mode.clock, + auxdiv, + divsel, + phasedir, + phaseinc); + + auxdiv = iclk_vga_clock_table[i].auxdiv; + divsel = iclk_vga_clock_table[i].divsel; + phasedir = iclk_vga_clock_table[i].phasedir; + phaseinc = iclk_vga_clock_table[i].phaseinc; + + valid =1 ; + +break ; + } + } + +if (!valid) { +DRM_ERROR ("Unable to find iCLKIP clock settings for %dKHz refresh rate\n" , + crtc->mode.clock); +return ; + } + +/* Program SSCDIVINTPHASE6 */ + temp =intel_sbi_read (dev_priv,SBI_SSCDIVINTPHASE6 ); + temp &= ~SBI_SSCDIVINTPHASE_DIVSEL_MASK ; + temp |=SBI_SSCDIVINTPHASE_DIVSEL (divsel); + temp &= ~SBI_SSCDIVINTPHASE_INCVAL_MASK ; + temp |=SBI_SSCDIVINTPHASE_INCVAL (phaseinc); + temp |=SBI_SSCDIVINTPHASE_DIR (phasedir); + temp |=SBI_SSCDIVINTPHASE_PROPAGATE ; + +intel_sbi_write (dev_priv, +SBI_SSCDIVINTPHASE6 , + temp); + +/* Program SSCAUXDIV */ +intel_sbi_write (dev_priv, +SBI_SSCAUXDIV6 , +intel_sbi_read (dev_priv,SBI_SSCAUXDIV6 ) | +SBI_SSCAUXDIV_FINALDIV2SEL (auxdiv)); + + +/* Enable modulator and associated divider */ +intel_sbi_write (dev_priv,SBI_SSCCTL6 , +intel_sbi_read (dev_priv,SBI_SSCCTL6 ) & + ~SBI_SSCCTL_DISABLE ); + +/* Wait for initialization time */ +udelay (50 ); + +/* Gate pixel clock */ +I915_WRITE (PIXCLK_GATE ,PIXCLK_GATE_UNGATE ); +} +/* * Enable PCH resources required for PCH ports: * - PCH PLLs
@@ -2721,11 +3023,14 @@ static void ironlake_pch_enable(struct drm_crtc *crtc)/* For PCH output, training FDI link */ dev_priv->display.fdi_link_train (crtc); -intel_enable_pch_pll (intel_crtc); - -if (HAS_PCH_CPT (dev)) { +if (HAS_PCH_LPT (dev)) { +DRM_DEBUG_KMS ("LPT detected: programming iCLKIP\n" ); +lpt_program_iclkip (crtc); + }else if (HAS_PCH_CPT (dev)) {u32 sel; +intel_enable_pch_pll (intel_crtc); + temp =I915_READ (PCH_DPLL_SEL );switch (pipe) {default :
@@ -4468,8 +4773,12 @@ static int ironlake_crtc_mode_set(struct drm_crtc *crtc,DRM_DEBUG_KMS ("Mode for pipe %d:\n" , pipe);drm_mode_debug_printmodeline (mode); -/* CPU eDP is the only output that doesn't need a PCH PLL of its own */ -if (!is_cpu_edp) { +/* CPU eDP is the only output that doesn't need a PCH PLL of its own on +* pre-Haswell/LPT generation */ +if (HAS_PCH_LPT (dev)) { +DRM_DEBUG_KMS ("LPT detected: no PLL for pipe %d necessary\n" , + pipe); + }else if (!is_cpu_edp) {struct intel_pch_pll *pll; pll =intel_get_pch_pll (intel_crtc, dpll, fp);
Signature · 1 line
1.7.10
Re: [PATCH 18/24] drm/i915: program iCLKIP on Lynx Point
Quoted 10 lines · On Thu, 26 Apr 2012 15:21:13 -0300 Eugeni Dodonov <[email protected]>…
The iCLKIP clock is used to drive the VGA pixel clock on the PCH. In order to do so, it must be programmed to properly do the clock ticks according to the divisor, phase direction, phase increments and a special auxiliary divisor for 20MHz clock.
Those values can be programmed individually, by doing some math; or we could use a pre-defined table of values for each modeset. For speed and simplification, the idea was to just adopt the table of valid pixel clocks and select the matching iCLKIP values from there.
Quoted 7 lines
As a possible idea for the future, it would be possible to add a fallback and calculate those values manually in case no match is found. But I don't think we'll encounter a mode not covered by those table, and VGA is pretty much going away in the future anyway.
Signed-off-by Eugeni Dodonov <[email protected]>---
I don't mind the table and like the fact that it documents the PPM. But I think we should fuzzy match the clocks, since e.g. 1920x1080@60Hz with reduced blanking is a 138.5MHz clock, and we don't have a match for that it appears? Or do we already fuzzy match elsewhere?
Signature · 1 line
Jesse Barnes, Intel Open Source Technology Center
PATCH 19/24 drm/i915: detect digital outputs on Haswell
In reply to Eugeni DodonovDigital port detection on Haswell is indicated by the presence of a bit in DDI_BUF_CTL for port A, and by a different register for ports B, C and D. So we check for those bits during the initialization time and let the hdmi function know about those.
Note that this bit does not indicates whether the output is DP or HDMI. However, the DDI buffers can be programmed in a way that is shared between DP/HDMI and FDI/HDMI except for PORT E.
So for now, we detect those digital outputs as being HDMI, but proper DP support is still pending.
Note that DDI A can only drive eDP, so we do not handle it here for hdmi initialization.
v2: simplify Haswell handling logic
v3: use generic function for handling digital outputs.
--- drivers/gpu/drm/i915/intel_ddi.c | 29 +++++++++++++++++++++++++++++ drivers/gpu/drm/i915/intel_display.c | 21 ++++++++++++++++++++- drivers/gpu/drm/i915/intel_drv.h | 1 + 3 files changed, 50 insertions(+), 1 deletion(-)
drivers/gpu/drm/i915/intel_ddi.c +29 -0
@@ -230,3 +230,32 @@ void ddi_fdi_link_train(struct drm_crtc *crtc)if (IS_HASWELL (dev))hsw_fdi_link_train (crtc); } + +/* For DDI connections, it is possible to support different outputs over the +* same DDI port, such as HDMI or DP or even VGA via FDI. So we don't know by +* the time the output is detected what exactly is on the other end of it. This +* function aims at providing support for this detection and proper output +* configuration. +*/ +void intel_ddi_init (struct drm_device *dev,enum port port) +{ +/* For now, we don't do any proper output detection and assume that we +* handle HDMI only */ + +switch (port){ +case PORT_A : +/* We don't handle eDP and DP yet */ +DRM_DEBUG_DRIVER ("Found digital output on DDI port A\n" ); +break ; +/* Assume that the ports B, C and D are working in HDMI mode for now */ +case PORT_B : +case PORT_C : +case PORT_D : +intel_hdmi_init (dev,DDI_BUF_CTL (port)); +break ; +default : +DRM_DEBUG_DRIVER ("No handlers defined for port %d, skipping DDI initialization\n" , + port); +break ; + } +}
drivers/gpu/drm/i915/intel_display.c +20 -1
@@ -6707,7 +6707,26 @@ static void intel_setup_outputs(struct drm_device *dev)intel_crt_init (dev); -if (HAS_PCH_SPLIT (dev)) { +if (IS_HASWELL (dev)) { +int found; + +/* Haswell uses DDI functions to detect digital outputs */ + found =I915_READ (DDI_BUF_CTL_A ) &DDI_INIT_DISPLAY_DETECTED ; +/* DDI A only supports eDP */ +if (found) +intel_ddi_init (dev,PORT_A ); + +/* DDI B, C and D detection is indicated by the SFUSE_STRAP +* register */ + found =I915_READ (SFUSE_STRAP ); + +if (found &SFUSE_STRAP_DDIB_DETECTED ) +intel_ddi_init (dev,PORT_B ); +if (found &SFUSE_STRAP_DDIC_DETECTED ) +intel_ddi_init (dev,PORT_C ); +if (found &SFUSE_STRAP_DDID_DETECTED ) +intel_ddi_init (dev,PORT_D ); + }else if (HAS_PCH_SPLIT (dev)) {int found;if (I915_READ (HDMIB ) &PORT_DETECTED ) {
drivers/gpu/drm/i915/intel_drv.h +1 -0
@@ -444,6 +444,7 @@ extern void intel_write_eld(struct drm_encoder *encoder,extern void intel_cpt_verify_modeset (struct drm_device *dev,int pipe);extern void intel_prepare_ddi (struct drm_device *dev);extern void ddi_fdi_link_train (struct drm_crtc *crtc); +extern void intel_ddi_init (struct drm_device *dev,enum port port);/* For use by IVB LP watermark workaround in intel_sprite.c */ extern void intel_update_watermarks (struct drm_device *dev);
Signature · 1 line
1.7.10
Re: [PATCH 19/24] drm/i915: detect digital outputs on Haswell
Quoted 53 lines · On Thu, 26 Apr 2012 15:21:14 -0300 Eugeni Dodonov <[email protected]>…
Digital port detection on Haswell is indicated by the presence of a bit in
DDI_BUF_CTLfor port A, and by a different register for ports B, C and D. So we check for those bits during the initialization time and let the hdmi function know about those.Note that this bit does not indicates whether the output is DP or HDMI. However, the DDI buffers can be programmed in a way that is shared between DP/HDMI and FDI/HDMI except for PORT E.
So for now, we detect those digital outputs as being HDMI, but proper DP support is still pending.
Note that DDI A can only drive eDP, so we do not handle it here for hdmi initialization.
v2: simplify Haswell handling logic
v3: use generic function for handling digital outputs.
Signed-off-by Eugeni Dodonov <[email protected]>--- drivers/gpu/drm/i915/intel_ddi.c | 29 +++++++++++++++++++++++++++++ drivers/gpu/drm/i915/intel_display.c | 21 ++++++++++++++++++++- drivers/gpu/drm/i915/intel_drv.h | 1 + 3 files changed, 50 insertions(+), 1 deletion(-)drivers/gpu/drm/i915/intel_ddi.c +19
-0@@ -230,3 +230,32 @@ void ddi_fdi_link_train(struct drm_crtc *crtc)if (IS_HASWELL (dev))hsw_fdi_link_train (crtc); } + +/* For DDI connections, it is possible to support different outputs over the +* same DDI port, such as HDMI or DP or even VGA via FDI. So we don't know by +* the time the output is detected what exactly is on the other end of it. This +* function aims at providing support for this detection and proper output +* configuration. +*/ +void intel_ddi_init (struct drm_device *dev,enum port port) +{ +/* For now, we don't do any proper output detection and assume that we +* handle HDMI only */ + +switch (port){ +case PORT_A : +/* We don't handle eDP and DP yet */ +DRM_DEBUG_DRIVER ("Found digital output on DDI port A\n" ); +break ; +/* Assume that the ports B, C and D are working in HDMI mode for now */ +case PORT_B :
drivers/gpu/drm/i915/intel_ddi.c void ddi_fdi_link_train(struct drm_crtc *crtc) · line 261
Quoted 10 lines
drivers/gpu/drm/i915/intel_ddi.c +10
-0+case PORT_C : +case PORT_D : +intel_hdmi_init (dev,DDI_BUF_CTL (port)); +break ; +default : +DRM_DEBUG_DRIVER ("No handlers defined for port %d, skipping DDI initialization\n" , + port); +break ; + } +}
We really really need to get the port detection working on HSW using the VBT.
Signature · 1 line
Jesse Barnes, Intel Open Source Technology Center
Re: [PATCH 19/24] drm/i915: detect digital outputs on Haswell
Quoted 3 lines · Jesse Barnes
We really really need to get the port detection working on HSW using the VBT.
It is not that easy from what I've seen. VBT can give some hints on which ports can support only DP or HDMI, but it does not answers all the cases. So the best solution seems to be running a DP AUX query when we got an output, and if it succeeds - it is a DP; otherwise, it is HDMI.
So my idea here is:
- add both HDMI and DP connectors for each available port (those we can
get via VBT and from the GPU variant - some variants don't have specific DDIs in hardware, and VBT can further say which DDI are incapable of driving HDMI when present)
- add an intel_ddi_detect routine for .detect of each of them
- the intel_ddi_detect would try doing the DP AUX test, and dispatch
either intel_hdmi_detect or intel_dp_detect accordingly.
Once the DP code will be ready, we'll put this in place. But for now, only HDMI works anyway, and I don't have any DP monitor around to play with :).
Does this looks reasonable?
Signature · 2 lines
Eugeni Dodonov <http://eugeni.dodonov.net/>
_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 19/24] drm/i915: detect digital outputs on Haswell
Quoted 20 lines · On Mon, 30 Apr 2012 21:33:42 -0300 Eugeni Dodonov <[email protected]> wrote:
Quoted 3 lines · Jesse Barnes
We really really need to get the port detection working on HSW using the VBT.
It is not that easy from what I've seen. VBT can give some hints on which ports can support only DP or HDMI, but it does not answers all the cases. So the best solution seems to be running a DP AUX query when we got an output, and if it succeeds - it is a DP; otherwise, it is HDMI.
So my idea here is:
- add both HDMI and DP connectors for each available port (those we can
get via VBT and from the GPU variant - some variants don't have specific DDIs in hardware, and VBT can further say which DDI are incapable of driving HDMI when present)
- add anintel_ddi_detectroutine for .detect of each of them
- theintel_ddi_detectwould try doing the DP AUX test, and dispatch
eitherintel_hdmi_detectorintel_dp_detectaccordingly.
Quoted 4 lines
Once the DP code will be ready, we'll put this in place. But for now, only HDMI works anyway, and I don't have any DP monitor around to play with :).
Does this looks reasonable?
I had wanted to avoid every HSW system looking like it had a bunch of HDMI and DP ports, when it really only has one of each or something.
Signature · 1 line
Jesse Barnes, Intel Open Source Technology Center
Re: [PATCH 19/24] drm/i915: detect digital outputs on Haswell
Quoted 2 lines · Jesse Barnes
I had wanted to avoid every HSW system looking like it had a bunch of HDMI and DP ports, when it really only has one of each or something.
Every DP port is also an HDMI port when a DP to HDMI converter is plugged in.
Signature · 1 line
[email protected]
_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 20/24 drm/i915: add support for DDI-controlled digital outputs
In reply to Eugeni DodonovThose are driven by DDIs on Haswell architecture, so we need to keep track of which DDI is being used on each output.
--- drivers/gpu/drm/i915/intel_hdmi.c | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+)
drivers/gpu/drm/i915/intel_hdmi.c +19 -0
@@ -41,6 +41,7 @@ struct intel_hdmi {struct intel_encoder base;u32 sdvox_reg;int ddc_bus; +int ddi_port;uint32_t color_range;bool has_hdmi_sink;bool has_audio;
@@ -606,6 +607,24 @@ void intel_hdmi_init(struct drm_device *dev, int sdvox_reg) intel_encoder->clone_mask = (1 <<INTEL_HDMIF_CLONE_BIT ); intel_hdmi->ddc_bus =GMBUS_PORT_DPD ; dev_priv->hotplug_supported_mask |=HDMID_HOTPLUG_INT_STATUS ; + }else if (sdvox_reg ==DDI_BUF_CTL (PORT_B )) { +DRM_DEBUG_DRIVER ("LPT: detected output on DDI B\n" ); + intel_encoder->clone_mask = (1 <<INTEL_HDMIB_CLONE_BIT ); + intel_hdmi->ddc_bus =GMBUS_PORT_DPB ; + intel_hdmi->ddi_port =PORT_B ; + dev_priv->hotplug_supported_mask |=HDMIB_HOTPLUG_INT_STATUS ; + }else if (sdvox_reg ==DDI_BUF_CTL (PORT_C )) { +DRM_DEBUG_DRIVER ("LPT: detected output on DDI C\n" ); + intel_encoder->clone_mask = (1 <<INTEL_HDMIC_CLONE_BIT ); + intel_hdmi->ddc_bus =GMBUS_PORT_DPC ; + intel_hdmi->ddi_port =PORT_C ; + dev_priv->hotplug_supported_mask |=HDMIC_HOTPLUG_INT_STATUS ; + }else if (sdvox_reg ==DDI_BUF_CTL (PORT_D )) { +DRM_DEBUG_DRIVER ("LPT: detected output on DDI D\n" ); + intel_encoder->clone_mask = (1 <<INTEL_HDMID_CLONE_BIT ); + intel_hdmi->ddc_bus =GMBUS_PORT_DPD ; + intel_hdmi->ddi_port =PORT_D ; + dev_priv->hotplug_supported_mask |=HDMID_HOTPLUG_INT_STATUS ; }else {DRM_ERROR ("Unknown sdvox register on HDMI init: %x\n" , sdvox_reg); }
Signature · 1 line
1.7.10
Re: [PATCH 20/24] drm/i915: add support for DDI-controlled digital outputs
Quoted 35 lines · On Thu, 26 Apr 2012 15:21:15 -0300 Eugeni Dodonov <[email protected]>…
Those are driven by DDIs on Haswell architecture, so we need to keep track of which DDI is being used on each output.
Signed-off-by Eugeni Dodonov <[email protected]>--- drivers/gpu/drm/i915/intel_hdmi.c | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+)drivers/gpu/drm/i915/intel_hdmi.c +12
-0@@ -41,6 +41,7 @@ struct intel_hdmi {struct intel_encoder base;u32 sdvox_reg;int ddc_bus; +int ddi_port;uint32_t color_range;bool has_hdmi_sink;bool has_audio;@@ -606,6 +607,24 @@ void intel_hdmi_init(struct drm_device *dev, int sdvox_reg) intel_encoder->clone_mask = (1 <<INTEL_HDMIF_CLONE_BIT ); intel_hdmi->ddc_bus =GMBUS_PORT_DPD ; dev_priv->hotplug_supported_mask |=HDMID_HOTPLUG_INT_STATUS ; + }else if (sdvox_reg ==DDI_BUF_CTL (PORT_B )) { +DRM_DEBUG_DRIVER ("LPT: detected output on DDI B\n" ); + intel_encoder->clone_mask = (1 <<INTEL_HDMIB_CLONE_BIT ); + intel_hdmi->ddc_bus =GMBUS_PORT_DPB ; + intel_hdmi->ddi_port =PORT_B ; + dev_priv->hotplug_supported_mask |=HDMIB_HOTPLUG_INT_STATUS ; + }else if (sdvox_reg ==DDI_BUF_CTL (PORT_C )) { +DRM_DEBUG_DRIVER ("LPT: detected output on DDI C\n" ); + intel_encoder->clone_mask = (1 <<INTEL_HDMIC_CLONE_BIT ); + intel_hdmi->ddc_bus =GMBUS_PORT_DPC ; + intel_hdmi->ddi_port =PORT_C ;
drivers/gpu/drm/i915/intel_hdmi.c void intel_hdmi_init(struct drm_device *dev, int sdvox_reg) · line 630
Quoted 10 lines
drivers/gpu/drm/i915/intel_hdmi.c +7
-0+ dev_priv->hotplug_supported_mask |=HDMIC_HOTPLUG_INT_STATUS ; + }else if (sdvox_reg ==DDI_BUF_CTL (PORT_D )) { +DRM_DEBUG_DRIVER ("LPT: detected output on DDI D\n" ); + intel_encoder->clone_mask = (1 <<INTEL_HDMID_CLONE_BIT ); + intel_hdmi->ddc_bus =GMBUS_PORT_DPD ; + intel_hdmi->ddi_port =PORT_D ; + dev_priv->hotplug_supported_mask |=HDMID_HOTPLUG_INT_STATUS ; }else {DRM_ERROR ("Unknown sdvox register on HDMI init: %x\n" , sdvox_reg); }
I think this'll work unless we want to split out the accessor functions some more.
Signature · 1 line
Jesse Barnes, Intel Open Source Technology Center
PATCH 21/24 drm/i915: add WR PLL programming table
In reply to Eugeni DodonovThis table is used for programming WR PLL clocks, used by HDMI and DVI outputs. I split it into a separate patch to simplify the HDMI enabling patch which was getting huge.
--- drivers/gpu/drm/i915/intel_ddi.c | 388 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 388 insertions(+)
drivers/gpu/drm/i915/intel_ddi.c +388 -0
@@ -259,3 +259,391 @@ void intel_ddi_init(struct drm_device *dev, enum port port)break ; } } + +/* WRPLL clock dividers */ +struct wrpll_tmds_clock { +u32 clock; +u16 p;/* Post divider */ +u16 n2;/* Feedback divider */ +u16 r2;/* Reference divider */ +}; + +/* Table of matching values for WRPLL clocks programming for each frequency */ +static const struct wrpll_tmds_clock wrpll_tmds_clock_table[] = { + {19750 ,38 ,25 ,18 }, + {20000 ,48 ,32 ,18 }, + {21000 ,36 ,21 ,15 }, + {21912 ,42 ,29 ,17 }, + {22000 ,36 ,22 ,15 }, + {23000 ,36 ,23 ,15 }, + {23500 ,40 ,40 ,23 }, + {23750 ,26 ,16 ,14 }, + {23750 ,26 ,16 ,14 }, + {24000 ,36 ,24 ,15 }, + {25000 ,36 ,25 ,15 }, + {25175 ,26 ,40 ,33 }, + {25200 ,30 ,21 ,15 }, + {26000 ,36 ,26 ,15 }, + {27000 ,30 ,21 ,14 }, + {27027 ,18 ,100 ,111 }, + {27500 ,30 ,29 ,19 }, + {28000 ,34 ,30 ,17 }, + {28320 ,26 ,30 ,22 }, + {28322 ,32 ,42 ,25 }, + {28750 ,24 ,23 ,18 }, + {29000 ,30 ,29 ,18 }, + {29750 ,32 ,30 ,17 }, + {30000 ,30 ,25 ,15 }, + {30750 ,30 ,41 ,24 }, + {31000 ,30 ,31 ,18 }, + {31500 ,30 ,28 ,16 }, + {32000 ,30 ,32 ,18 }, + {32500 ,28 ,32 ,19 }, + {33000 ,24 ,22 ,15 }, + {34000 ,28 ,30 ,17 }, + {35000 ,26 ,32 ,19 }, + {35500 ,24 ,30 ,19 }, + {36000 ,26 ,26 ,15 }, + {36750 ,26 ,46 ,26 }, + {37000 ,24 ,23 ,14 }, + {37762 ,22 ,40 ,26 }, + {37800 ,20 ,21 ,15 }, + {38000 ,24 ,27 ,16 }, + {38250 ,24 ,34 ,20 }, + {39000 ,24 ,26 ,15 }, + {40000 ,24 ,32 ,18 }, + {40500 ,20 ,21 ,14 }, + {40541 ,22 ,147 ,89 }, + {40750 ,18 ,19 ,14 }, + {41000 ,16 ,17 ,14 }, + {41500 ,22 ,44 ,26 }, + {41540 ,22 ,44 ,26 }, + {42000 ,18 ,21 ,15 }, + {42500 ,22 ,45 ,26 }, + {43000 ,20 ,43 ,27 }, + {43163 ,20 ,24 ,15 }, + {44000 ,18 ,22 ,15 }, + {44900 ,20 ,108 ,65 }, + {45000 ,20 ,25 ,15 }, + {45250 ,20 ,52 ,31 }, + {46000 ,18 ,23 ,15 }, + {46750 ,20 ,45 ,26 }, + {47000 ,20 ,40 ,23 }, + {48000 ,18 ,24 ,15 }, + {49000 ,18 ,49 ,30 }, + {49500 ,16 ,22 ,15 }, + {50000 ,18 ,25 ,15 }, + {50500 ,18 ,32 ,19 }, + {51000 ,18 ,34 ,20 }, + {52000 ,18 ,26 ,15 }, + {52406 ,14 ,34 ,25 }, + {53000 ,16 ,22 ,14 }, + {54000 ,16 ,24 ,15 }, + {54054 ,16 ,173 ,108 }, + {54500 ,14 ,24 ,17 }, + {55000 ,12 ,22 ,18 }, + {56000 ,14 ,45 ,31 }, + {56250 ,16 ,25 ,15 }, + {56750 ,14 ,25 ,17 }, + {57000 ,16 ,27 ,16 }, + {58000 ,16 ,43 ,25 }, + {58250 ,16 ,38 ,22 }, + {58750 ,16 ,40 ,23 }, + {59000 ,14 ,26 ,17 }, + {59341 ,14 ,40 ,26 }, + {59400 ,16 ,44 ,25 }, + {60000 ,16 ,32 ,18 }, + {60500 ,12 ,39 ,29 }, + {61000 ,14 ,49 ,31 }, + {62000 ,14 ,37 ,23 }, + {62250 ,14 ,42 ,26 }, + {63000 ,12 ,21 ,15 }, + {63500 ,14 ,28 ,17 }, + {64000 ,12 ,27 ,19 }, + {65000 ,14 ,32 ,19 }, + {65250 ,12 ,29 ,20 }, + {65500 ,12 ,32 ,22 }, + {66000 ,12 ,22 ,15 }, + {66667 ,14 ,38 ,22 }, + {66750 ,10 ,21 ,17 }, + {67000 ,14 ,33 ,19 }, + {67750 ,14 ,58 ,33 }, + {68000 ,14 ,30 ,17 }, + {68179 ,14 ,46 ,26 }, + {68250 ,14 ,46 ,26 }, + {69000 ,12 ,23 ,15 }, + {70000 ,12 ,28 ,18 }, + {71000 ,12 ,30 ,19 }, + {72000 ,12 ,24 ,15 }, + {73000 ,10 ,23 ,17 }, + {74000 ,12 ,23 ,14 }, + {74176 ,8 ,100 ,91 }, + {74250 ,10 ,22 ,16 }, + {74481 ,12 ,43 ,26 }, + {74500 ,10 ,29 ,21 }, + {75000 ,12 ,25 ,15 }, + {75250 ,10 ,39 ,28 }, + {76000 ,12 ,27 ,16 }, + {77000 ,12 ,53 ,31 }, + {78000 ,12 ,26 ,15 }, + {78750 ,12 ,28 ,16 }, + {79000 ,10 ,38 ,26 }, + {79500 ,10 ,28 ,19 }, + {80000 ,12 ,32 ,18 }, + {81000 ,10 ,21 ,14 }, + {81081 ,6 ,100 ,111 }, + {81624 ,8 ,29 ,24 }, + {82000 ,8 ,17 ,14 }, + {83000 ,10 ,40 ,26 }, + {83950 ,10 ,28 ,18 }, + {84000 ,10 ,28 ,18 }, + {84750 ,6 ,16 ,17 }, + {85000 ,6 ,17 ,18 }, + {85250 ,10 ,30 ,19 }, + {85750 ,10 ,27 ,17 }, + {86000 ,10 ,43 ,27 }, + {87000 ,10 ,29 ,18 }, + {88000 ,10 ,44 ,27 }, + {88500 ,10 ,41 ,25 }, + {89000 ,10 ,28 ,17 }, + {89012 ,6 ,90 ,91 }, + {89100 ,10 ,33 ,20 }, + {90000 ,10 ,25 ,15 }, + {91000 ,10 ,32 ,19 }, + {92000 ,10 ,46 ,27 }, + {93000 ,10 ,31 ,18 }, + {94000 ,10 ,40 ,23 }, + {94500 ,10 ,28 ,16 }, + {95000 ,10 ,44 ,25 }, + {95654 ,10 ,39 ,22 }, + {95750 ,10 ,39 ,22 }, + {96000 ,10 ,32 ,18 }, + {97000 ,8 ,23 ,16 }, + {97750 ,8 ,42 ,29 }, + {98000 ,8 ,45 ,31 }, + {99000 ,8 ,22 ,15 }, + {99750 ,8 ,34 ,23 }, + {100000 ,6 ,20 ,18 }, + {100500 ,6 ,19 ,17 }, + {101000 ,6 ,37 ,33 }, + {101250 ,8 ,21 ,14 }, + {102000 ,6 ,17 ,15 }, + {102250 ,6 ,25 ,22 }, + {103000 ,8 ,29 ,19 }, + {104000 ,8 ,37 ,24 }, + {105000 ,8 ,28 ,18 }, + {106000 ,8 ,22 ,14 }, + {107000 ,8 ,46 ,29 }, + {107214 ,8 ,27 ,17 }, + {108000 ,8 ,24 ,15 }, + {108108 ,8 ,173 ,108 }, + {109000 ,6 ,23 ,19 }, + {109000 ,6 ,23 ,19 }, + {110000 ,6 ,22 ,18 }, + {110013 ,6 ,22 ,18 }, + {110250 ,8 ,49 ,30 }, + {110500 ,8 ,36 ,22 }, + {111000 ,8 ,23 ,14 }, + {111264 ,8 ,150 ,91 }, + {111375 ,8 ,33 ,20 }, + {112000 ,8 ,63 ,38 }, + {112500 ,8 ,25 ,15 }, + {113100 ,8 ,57 ,34 }, + {113309 ,8 ,42 ,25 }, + {114000 ,8 ,27 ,16 }, + {115000 ,6 ,23 ,18 }, + {116000 ,8 ,43 ,25 }, + {117000 ,8 ,26 ,15 }, + {117500 ,8 ,40 ,23 }, + {118000 ,6 ,38 ,29 }, + {119000 ,8 ,30 ,17 }, + {119500 ,8 ,46 ,26 }, + {119651 ,8 ,39 ,22 }, + {120000 ,8 ,32 ,18 }, + {121000 ,6 ,39 ,29 }, + {121250 ,6 ,31 ,23 }, + {121750 ,6 ,23 ,17 }, + {122000 ,6 ,42 ,31 }, + {122614 ,6 ,30 ,22 }, + {123000 ,6 ,41 ,30 }, + {123379 ,6 ,37 ,27 }, + {124000 ,6 ,51 ,37 }, + {125000 ,6 ,25 ,18 }, + {125250 ,4 ,13 ,14 }, + {125750 ,4 ,27 ,29 }, + {126000 ,6 ,21 ,15 }, + {127000 ,6 ,24 ,17 }, + {127250 ,6 ,41 ,29 }, + {128000 ,6 ,27 ,19 }, + {129000 ,6 ,43 ,30 }, + {129859 ,4 ,25 ,26 }, + {130000 ,6 ,26 ,18 }, + {130250 ,6 ,42 ,29 }, + {131000 ,6 ,32 ,22 }, + {131500 ,6 ,38 ,26 }, + {131850 ,6 ,41 ,28 }, + {132000 ,6 ,22 ,15 }, + {132750 ,6 ,28 ,19 }, + {133000 ,6 ,34 ,23 }, + {133330 ,6 ,37 ,25 }, + {134000 ,6 ,61 ,41 }, + {135000 ,6 ,21 ,14 }, + {135250 ,6 ,167 ,111 }, + {136000 ,6 ,62 ,41 }, + {137000 ,6 ,35 ,23 }, + {138000 ,6 ,23 ,15 }, + {138500 ,6 ,40 ,26 }, + {138750 ,6 ,37 ,24 }, + {139000 ,6 ,34 ,22 }, + {139050 ,6 ,34 ,22 }, + {139054 ,6 ,34 ,22 }, + {140000 ,6 ,28 ,18 }, + {141000 ,6 ,36 ,23 }, + {141500 ,6 ,22 ,14 }, + {142000 ,6 ,30 ,19 }, + {143000 ,6 ,27 ,17 }, + {143472 ,4 ,17 ,16 }, + {144000 ,6 ,24 ,15 }, + {145000 ,6 ,29 ,18 }, + {146000 ,6 ,47 ,29 }, + {146250 ,6 ,26 ,16 }, + {147000 ,6 ,49 ,30 }, + {147891 ,6 ,23 ,14 }, + {148000 ,6 ,23 ,14 }, + {148250 ,6 ,28 ,17 }, + {148352 ,4 ,100 ,91 }, + {148500 ,6 ,33 ,20 }, + {149000 ,6 ,48 ,29 }, + {150000 ,6 ,25 ,15 }, + {151000 ,4 ,19 ,17 }, + {152000 ,6 ,27 ,16 }, + {152280 ,6 ,44 ,26 }, + {153000 ,6 ,34 ,20 }, + {154000 ,6 ,53 ,31 }, + {155000 ,6 ,31 ,18 }, + {155250 ,6 ,50 ,29 }, + {155750 ,6 ,45 ,26 }, + {156000 ,6 ,26 ,15 }, + {157000 ,6 ,61 ,35 }, + {157500 ,6 ,28 ,16 }, + {158000 ,6 ,65 ,37 }, + {158250 ,6 ,44 ,25 }, + {159000 ,6 ,53 ,30 }, + {159500 ,6 ,39 ,22 }, + {160000 ,6 ,32 ,18 }, + {161000 ,4 ,31 ,26 }, + {162000 ,4 ,18 ,15 }, + {162162 ,4 ,131 ,109 }, + {162500 ,4 ,53 ,44 }, + {163000 ,4 ,29 ,24 }, + {164000 ,4 ,17 ,14 }, + {165000 ,4 ,22 ,18 }, + {166000 ,4 ,32 ,26 }, + {167000 ,4 ,26 ,21 }, + {168000 ,4 ,46 ,37 }, + {169000 ,4 ,104 ,83 }, + {169128 ,4 ,64 ,51 }, + {169500 ,4 ,39 ,31 }, + {170000 ,4 ,34 ,27 }, + {171000 ,4 ,19 ,15 }, + {172000 ,4 ,51 ,40 }, + {172750 ,4 ,32 ,25 }, + {172800 ,4 ,32 ,25 }, + {173000 ,4 ,41 ,32 }, + {174000 ,4 ,49 ,38 }, + {174787 ,4 ,22 ,17 }, + {175000 ,4 ,35 ,27 }, + {176000 ,4 ,30 ,23 }, + {177000 ,4 ,38 ,29 }, + {178000 ,4 ,29 ,22 }, + {178500 ,4 ,37 ,28 }, + {179000 ,4 ,53 ,40 }, + {179500 ,4 ,73 ,55 }, + {180000 ,4 ,20 ,15 }, + {181000 ,4 ,55 ,41 }, + {182000 ,4 ,31 ,23 }, + {183000 ,4 ,42 ,31 }, + {184000 ,4 ,30 ,22 }, + {184750 ,4 ,26 ,19 }, + {185000 ,4 ,37 ,27 }, + {186000 ,4 ,51 ,37 }, + {187000 ,4 ,36 ,26 }, + {188000 ,4 ,32 ,23 }, + {189000 ,4 ,21 ,15 }, + {190000 ,4 ,38 ,27 }, + {190960 ,4 ,41 ,29 }, + {191000 ,4 ,41 ,29 }, + {192000 ,4 ,27 ,19 }, + {192250 ,4 ,37 ,26 }, + {193000 ,4 ,20 ,14 }, + {193250 ,4 ,53 ,37 }, + {194000 ,4 ,23 ,16 }, + {194208 ,4 ,23 ,16 }, + {195000 ,4 ,26 ,18 }, + {196000 ,4 ,45 ,31 }, + {197000 ,4 ,35 ,24 }, + {197750 ,4 ,41 ,28 }, + {198000 ,4 ,22 ,15 }, + {198500 ,4 ,25 ,17 }, + {199000 ,4 ,28 ,19 }, + {200000 ,4 ,37 ,25 }, + {201000 ,4 ,61 ,41 }, + {202000 ,4 ,112 ,75 }, + {202500 ,4 ,21 ,14 }, + {203000 ,4 ,146 ,97 }, + {204000 ,4 ,62 ,41 }, + {204750 ,4 ,44 ,29 }, + {205000 ,4 ,38 ,25 }, + {206000 ,4 ,29 ,19 }, + {207000 ,4 ,23 ,15 }, + {207500 ,4 ,40 ,26 }, + {208000 ,4 ,37 ,24 }, + {208900 ,4 ,48 ,31 }, + {209000 ,4 ,48 ,31 }, + {209250 ,4 ,31 ,20 }, + {210000 ,4 ,28 ,18 }, + {211000 ,4 ,25 ,16 }, + {212000 ,4 ,22 ,14 }, + {213000 ,4 ,30 ,19 }, + {213750 ,4 ,38 ,24 }, + {214000 ,4 ,46 ,29 }, + {214750 ,4 ,35 ,22 }, + {215000 ,4 ,43 ,27 }, + {216000 ,4 ,24 ,15 }, + {217000 ,4 ,37 ,23 }, + {218000 ,4 ,42 ,26 }, + {218250 ,4 ,42 ,26 }, + {218750 ,4 ,34 ,21 }, + {219000 ,4 ,47 ,29 }, + {219000 ,4 ,47 ,29 }, + {220000 ,4 ,44 ,27 }, + {220640 ,4 ,49 ,30 }, + {220750 ,4 ,36 ,22 }, + {221000 ,4 ,36 ,22 }, + {222000 ,4 ,23 ,14 }, + {222525 ,4 ,28 ,17 }, + {222750 ,4 ,33 ,20 }, + {227000 ,4 ,37 ,22 }, + {230250 ,4 ,29 ,17 }, + {233500 ,4 ,38 ,22 }, + {235000 ,4 ,40 ,23 }, + {238000 ,4 ,30 ,17 }, + {241500 ,2 ,17 ,19 }, + {245250 ,2 ,20 ,22 }, + {247750 ,2 ,22 ,24 }, + {253250 ,2 ,15 ,16 }, + {256250 ,2 ,18 ,19 }, + {262500 ,2 ,31 ,32 }, + {267250 ,2 ,66 ,67 }, + {268500 ,2 ,94 ,95 }, + {270000 ,2 ,14 ,14 }, + {272500 ,2 ,77 ,76 }, + {273750 ,2 ,57 ,56 }, + {280750 ,2 ,24 ,23 }, + {281250 ,2 ,23 ,22 }, + {286000 ,2 ,17 ,16 }, + {291750 ,2 ,26 ,24 }, + {296703 ,2 ,56 ,51 }, + {297000 ,2 ,22 ,20 }, + {298000 ,2 ,21 ,19 }, +};
Signature · 1 line
1.7.10
PATCH 22/24 drm/i915: move HDMI structs to shared location
In reply to Eugeni DodonovMove intel_hdmi data structure and support functions to a shared location, to allow their usage from intel_ddi module.
--- drivers/gpu/drm/i915/intel_drv.h | 18 +++++++++++++++++- drivers/gpu/drm/i915/intel_hdmi.c | 19 +++---------------- 2 files changed, 20 insertions(+), 17 deletions(-)
drivers/gpu/drm/i915/intel_drv.h +17 -1
@@ -284,6 +284,19 @@ struct dip_infoframe { } __attribute__ ((packed)) body; } __attribute__((packed)); +struct intel_hdmi { +struct intel_encoder base; +u32 sdvox_reg; +int ddc_bus; +int ddi_port; +uint32_t color_range; +bool has_hdmi_sink; +bool has_audio; +enum hdmi_force_audio force_audio; +void (*write_infoframe)(struct drm_encoder *encoder, +struct dip_infoframe *frame); +}; +static inline struct drm_crtc *intel_get_crtc_for_pipe (struct drm_device *dev,int pipe) {
@@ -323,7 +336,10 @@ extern void intel_attach_broadcast_rgb_property(struct drm_connector *connector)extern void intel_crt_init (struct drm_device *dev);extern void intel_hdmi_init (struct drm_device *dev,int sdvox_reg); -void intel_dip_infoframe_csum (struct dip_infoframe *avi_if); +extern struct intel_hdmi *enc_to_intel_hdmi (struct drm_encoder *encoder); +extern void intel_hdmi_set_avi_infoframe (struct drm_encoder *encoder); +extern void intel_hdmi_set_spd_infoframe (struct drm_encoder *encoder); +extern void intel_dip_infoframe_csum (struct dip_infoframe *avi_if);extern bool intel_sdvo_init (struct drm_device *dev,uint32_t sdvo_reg,bool is_sdvob);extern void intel_dvo_init (struct drm_device *dev);
drivers/gpu/drm/i915/intel_hdmi.c +3 -16
@@ -37,20 +37,7 @@#include "i915_drm.h" #include "i915_drv.h" -struct intel_hdmi { -struct intel_encoder base; -u32 sdvox_reg; -int ddc_bus; -int ddi_port; -uint32_t color_range; -bool has_hdmi_sink; -bool has_audio; -enum hdmi_force_audio force_audio; -void (*write_infoframe)(struct drm_encoder *encoder, -struct dip_infoframe *frame); -}; - -static struct intel_hdmi *enc_to_intel_hdmi (struct drm_encoder *encoder) +struct intel_hdmi *enc_to_intel_hdmi (struct drm_encoder *encoder) { return container_of(encoder, struct intel_hdmi, base.base); }
@@ -251,7 +238,7 @@ static void intel_set_infoframe(struct drm_encoder *encoder, intel_hdmi->write_infoframe (encoder, frame); } -static void intel_hdmi_set_avi_infoframe (struct drm_encoder *encoder) +void intel_hdmi_set_avi_infoframe (struct drm_encoder *encoder) {struct dip_infoframe avi_if = { .type =DIP_TYPE_AVI ,
@@ -262,7 +249,7 @@ static void intel_hdmi_set_avi_infoframe(struct drm_encoder *encoder)intel_set_infoframe (encoder, &avi_if); } -static void intel_hdmi_set_spd_infoframe (struct drm_encoder *encoder) +void intel_hdmi_set_spd_infoframe (struct drm_encoder *encoder) {struct dip_infoframe spd_if;
Signature · 1 line
1.7.10
Re: [PATCH 22/24] drm/i915: move HDMI structs to shared location
Quoted 81 lines · On Thu, 26 Apr 2012 15:21:17 -0300 Eugeni Dodonov <[email protected]>…
Move
intel_hdmidata structure and support functions to a shared location, to allow their usage fromintel_ddimodule.Signed-off-by Eugeni Dodonov <[email protected]>--- drivers/gpu/drm/i915/intel_drv.h | 18 +++++++++++++++++- drivers/gpu/drm/i915/intel_hdmi.c | 19 +++---------------- 2 files changed, 20 insertions(+), 17 deletions(-)drivers/gpu/drm/i915/intel_drv.h +17
-1@@ -284,6 +284,19 @@ struct dip_infoframe { } __attribute__ ((packed)) body; } __attribute__((packed)); +struct intel_hdmi { +struct intel_encoder base; +u32 sdvox_reg; +int ddc_bus; +int ddi_port; +uint32_t color_range; +bool has_hdmi_sink; +bool has_audio; +enum hdmi_force_audio force_audio; +void (*write_infoframe)(struct drm_encoder *encoder, +struct dip_infoframe *frame); +}; +static inline struct drm_crtc *intel_get_crtc_for_pipe (struct drm_device *dev,int pipe) {@@ -323,7 +336,10 @@ extern void intel_attach_broadcast_rgb_property(struct drm_connector *connector)extern void intel_crt_init (struct drm_device *dev);extern void intel_hdmi_init (struct drm_device *dev,int sdvox_reg); -void intel_dip_infoframe_csum (struct dip_infoframe *avi_if); +extern struct intel_hdmi *enc_to_intel_hdmi (struct drm_encoder *encoder); +extern void intel_hdmi_set_avi_infoframe (struct drm_encoder *encoder); +extern void intel_hdmi_set_spd_infoframe (struct drm_encoder *encoder); +extern void intel_dip_infoframe_csum (struct dip_infoframe *avi_if);extern bool intel_sdvo_init (struct drm_device *dev,uint32_t sdvo_reg,bool is_sdvob);extern void intel_dvo_init (struct drm_device *dev);drivers/gpu/drm/i915/intel_hdmi.c +2
-15@@ -37,20 +37,7 @@#include "i915_drm.h" #include "i915_drv.h" -struct intel_hdmi { -struct intel_encoder base; -u32 sdvox_reg; -int ddc_bus; -int ddi_port; -uint32_t color_range; -bool has_hdmi_sink; -bool has_audio; -enum hdmi_force_audio force_audio; -void (*write_infoframe)(struct drm_encoder *encoder, -struct dip_infoframe *frame); -}; - -static struct intel_hdmi *enc_to_intel_hdmi (struct drm_encoder *encoder) +struct intel_hdmi *enc_to_intel_hdmi (struct drm_encoder *encoder) { return container_of(encoder, struct intel_hdmi, base.base); }@@ -251,7 +238,7 @@ static void intel_set_infoframe(struct drm_encoder *encoder, intel_hdmi->write_infoframe (encoder, frame); } -static void intel_hdmi_set_avi_infoframe (struct drm_encoder *encoder) +void intel_hdmi_set_avi_infoframe (struct drm_encoder *encoder) {struct dip_infoframe avi_if = { .type =DIP_TYPE_AVI ,
drivers/gpu/drm/i915/intel_hdmi.c static void intel_hdmi_set_avi_infoframe(struct drm_encoder *encoder) · line 255
Quoted 8 lines
drivers/gpu/drm/i915/intel_hdmi.c +1
-1@@ -262,7 +249,7 @@ static void intel_hdmi_set_avi_infoframe(struct drm_encoder *encoder)intel_set_infoframe (encoder, &avi_if); } -static void intel_hdmi_set_spd_infoframe (struct drm_encoder *encoder) +void intel_hdmi_set_spd_infoframe (struct drm_encoder *encoder) {struct dip_infoframe spd_if;
Signature · 1 line
Jesse Barnes, Intel Open Source Technology Center
PATCH 23/24 drm/i915: prepare HDMI link for Haswell
In reply to Eugeni DodonovOn Haswell, we need to properly train the DDI buffers prior to enabling HDMI, and enable the required clocks with correct dividers for the desired frequency.
Also, we cannot simple reuse HDMI routines from previous generations of GPU, as most of HDMI-specific stuff is being done via the DDI port programming instead of HDMI-specific registers.
This commit take advantage of the WR PLL clock table which is in a separate (previous) commit to select the right divisors for each mode.
--- drivers/gpu/drm/i915/intel_ddi.c | 116 +++++++++++++++++++++++++++++++++++++ drivers/gpu/drm/i915/intel_drv.h | 5 ++ drivers/gpu/drm/i915/intel_hdmi.c | 13 ++++- 3 files changed, 133 insertions(+), 1 deletion(-)
drivers/gpu/drm/i915/intel_ddi.c +116 -0
@@ -647,3 +647,119 @@ static const struct wrpll_tmds_clock wrpll_tmds_clock_table[] = { {297000, 2, 22, 20}, {298000, 2, 21, 19}, }; + +void intel_ddi_mode_set (struct drm_encoder *encoder, +struct drm_display_mode *mode, +struct drm_display_mode *adjusted_mode) +{ +struct drm_device *dev = encoder->dev; +struct drm_i915_private *dev_priv = dev->dev_private; +struct drm_crtc *crtc = encoder->crtc; +struct intel_crtc *intel_crtc =to_intel_crtc (crtc); +struct intel_hdmi *intel_hdmi =enc_to_intel_hdmi (encoder); +int port = intel_hdmi->ddi_port; +int pipe = intel_crtc->pipe; +int p, n2, r2, valid=0 ; +u32 temp, i; + +/* On Haswell, we need to enable the clocks and prepare DDI function to +* work in HDMI mode for this pipe. +*/ +DRM_DEBUG_KMS ("Preparing HDMI DDI mode for Haswell on port %c, pipe %c\n" ,port_name (port),pipe_name (pipe)); + +for (i=0 ; i <ARRAY_SIZE (wrpll_tmds_clock_table); i++) { +if (crtc->mode.clock == wrpll_tmds_clock_table[i].clock) { + p = wrpll_tmds_clock_table[i].p; + n2 = wrpll_tmds_clock_table[i].n2; + r2 = wrpll_tmds_clock_table[i].r2; + +DRM_DEBUG_KMS ("WR PLL clock: found settings for %dKHz refresh rate: p=%d, n2=%d, r2=%d\n" , + crtc->mode.clock, + p, n2, r2); + + valid =1 ; +break ; + } + } + +if (!valid) { +DRM_ERROR ("Unable to find WR PLL clock settings for %dKHz refresh rate\n" , + crtc->mode.clock); +return ; + } + +/* Enable LCPLL if disabled */ + temp =I915_READ (LCPLL_CTL ); +if (temp &LCPLL_PLL_DISABLE ) +I915_WRITE (LCPLL_CTL , + temp & ~LCPLL_PLL_DISABLE ); + +/* Configure WR PLL 1, program the correct divider values for +* the desired frequency and wait for warmup */ +I915_WRITE (WRPLL_CTL1 , +WRPLL_PLL_ENABLE | +WRPLL_PLL_SELECT_LCPLL_2700 | +WRPLL_DIVIDER_REFERENCE (r2) | +WRPLL_DIVIDER_FEEDBACK (n2) | +WRPLL_DIVIDER_POST (p)); + +udelay (20 ); + +/* Use WRPLL1 clock to drive the output to the port, and tell the pipe to use +* this port for connection. +*/ +I915_WRITE (PORT_CLK_SEL (port), +PORT_CLK_SEL_WRPLL1 ); +I915_WRITE (PIPE_CLK_SEL (pipe), +PIPE_CLK_SEL_PORT (port)); + +udelay (20 ); + +if (intel_hdmi->has_audio) { +/* Proper support for digital audio needs a new logic and a new set +* of registers, so we leave it for future patch bombing. +*/ +DRM_DEBUG_DRIVER ("HDMI audio on pipe %c not yet supported on DDI\n" , +pipe_name (intel_crtc->pipe)); + } + +/* Enable PIPE_DDI_FUNC_CTL for the pipe to work in HDMI mode */ + temp =I915_READ (DDI_FUNC_CTL (pipe)); + temp &= ~PIPE_DDI_PORT_MASK ; + temp &= ~PIPE_DDI_BPC_12 ; + temp |=PIPE_DDI_SELECT_PORT (port) | +PIPE_DDI_MODE_SELECT_HDMI | + ((intel_crtc->bpp >24 ) ? +PIPE_DDI_BPC_12 : +PIPE_DDI_BPC_8 ) | +PIPE_DDI_FUNC_ENABLE ; + +I915_WRITE (DDI_FUNC_CTL (pipe), temp); + +intel_hdmi_set_avi_infoframe (encoder); +intel_hdmi_set_spd_infoframe (encoder); +} + +void intel_ddi_dpms (struct drm_encoder *encoder,int mode) +{ +struct drm_device *dev = encoder->dev; +struct drm_i915_private *dev_priv = dev->dev_private; +struct intel_hdmi *intel_hdmi =enc_to_intel_hdmi (encoder); +int port = intel_hdmi->ddi_port; +u32 temp; + + temp =I915_READ (DDI_BUF_CTL (port)); + +if (mode !=DRM_MODE_DPMS_ON ) { + temp &= ~DDI_BUF_CTL_ENABLE ; + }else { + temp |=DDI_BUF_CTL_ENABLE ; + } + +/* Enable DDI_BUF_CTL. In HDMI/DVI mode, the port width, +* and swing/emphasis values are ignored so nothing special needs +* to be done besides enabling the port. +*/ +I915_WRITE (DDI_BUF_CTL (port), + temp); +}
drivers/gpu/drm/i915/intel_drv.h +5 -0
@@ -482,4 +482,9 @@ 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); +extern void intel_ddi_dpms (struct drm_encoder *encoder,int mode); +extern void intel_ddi_mode_set (struct drm_encoder *encoder, +struct drm_display_mode *mode, +struct drm_display_mode *adjusted_mode); +#endif /* __INTEL_DRV_H__ */
drivers/gpu/drm/i915/intel_hdmi.c +12 -1
@@ -505,6 +505,14 @@ static void intel_hdmi_destroy(struct drm_connector *connector)kfree (connector); } +static const struct drm_encoder_helper_funcs intel_hdmi_helper_funcs_hsw = { + .dpms = intel_ddi_dpms, + .mode_fixup = intel_hdmi_mode_fixup, + .prepare = intel_encoder_prepare, + .mode_set = intel_ddi_mode_set, + .commit = intel_encoder_commit, +}; +static const struct drm_encoder_helper_funcs intel_hdmi_helper_funcs = { .dpms = intel_hdmi_dpms, .mode_fixup = intel_hdmi_mode_fixup,
@@ -635,7 +643,10 @@ void intel_hdmi_init(struct drm_device *dev, int sdvox_reg)I915_WRITE (TVIDEO_DIP_CTL (i),0 ); } -drm_encoder_helper_add (&intel_encoder->base, &intel_hdmi_helper_funcs); +if (IS_HASWELL (dev)) +drm_encoder_helper_add (&intel_encoder->base, &intel_hdmi_helper_funcs_hsw); +else +drm_encoder_helper_add (&intel_encoder->base, &intel_hdmi_helper_funcs);intel_hdmi_add_properties (intel_hdmi, connector);
Signature · 1 line
1.7.10
PATCH 24/24 drm/i915: hook Haswell devices in place
In reply to Eugeni DodonovThis patch enables i915 driver to handle Haswell devices. It should go in last, when things are working stable enough.
--- drivers/char/agp/intel-agp.c | 4 ++++ drivers/gpu/drm/i915/i915_drv.c | 7 +++++++ 2 files changed, 11 insertions(+)
drivers/char/agp/intel-agp.c +4 -0
@@ -908,6 +908,10 @@ static struct pci_device_id agp_intel_pci_table[] = {ID (PCI_DEVICE_ID_INTEL_IVYBRIDGE_M_HB ),ID (PCI_DEVICE_ID_INTEL_IVYBRIDGE_S_HB ),ID (PCI_DEVICE_ID_INTEL_VALLEYVIEW_HB ), +ID (PCI_DEVICE_ID_INTEL_HASWELL_HB ), +ID (PCI_DEVICE_ID_INTEL_HASWELL_M_HB ), +ID (PCI_DEVICE_ID_INTEL_HASWELL_S_HB ), + ID(PCI_DEVICE_ID_INTEL_HASWELL_E_HB), { } };
drivers/gpu/drm/i915/i915_drv.c +7 -0
@@ -345,6 +345,13 @@ static const struct pci_device_id pciidlist[] = { /* aka */INTEL_VGA_DEVICE (0x0162 , &intel_ivybridge_d_info),/* GT2 desktop */ INTEL_VGA_DEVICE (0x015a , &intel_ivybridge_d_info),/* GT1 server */ INTEL_VGA_DEVICE (0x016a , &intel_ivybridge_d_info),/* GT2 server */ +INTEL_VGA_DEVICE (0x0402 , &intel_haswell_d_info),/* GT1 desktop */ +INTEL_VGA_DEVICE (0x0412 , &intel_haswell_d_info),/* GT2 desktop */ +INTEL_VGA_DEVICE (0x040a , &intel_haswell_d_info),/* GT1 server */ +INTEL_VGA_DEVICE (0x041a , &intel_haswell_d_info),/* GT2 server */ +INTEL_VGA_DEVICE (0x0406 , &intel_haswell_m_info),/* GT1 mobile */ +INTEL_VGA_DEVICE (0x0416 , &intel_haswell_m_info),/* GT2 mobile */ +INTEL_VGA_DEVICE (0x0c16 , &intel_haswell_d_info),/* SDV */ {0, 0, 0} };
Signature · 1 line
1.7.10