Features/DisplayPort

From FedoraProject

< Features(Difference between revisions)
Jump to: navigation, search
m (Documentation)
(reconsidered and accepted by FESCo on 2009-10-09)
 
(12 intermediate revisions by 6 users not shown)
Line 1: Line 1:
= DisplayPort support =
+
= DisplayPort support for Intel =
<!-- The name of your feature -->
+
  
 
== Summary ==
 
== Summary ==
  
Enhanced support for DisplayPort in X and kernel drivers.
+
Enhanced support for DisplayPort in X and kernel drivers for Intel hardware.
  
 
== Owner ==
 
== Owner ==
Line 14: Line 13:
  
 
* Targeted release: [[Releases/12|Fedora 12]]  
 
* Targeted release: [[Releases/12|Fedora 12]]  
* Last updated: 2009-06-24
+
* Last updated: 2009-10-08
* Percentage of completion: 10%
+
* Percentage of completion: 100%
 +
 
 +
The intel driver has DisplayPort and embedded-DP support.
  
 
== Detailed Description ==
 
== Detailed Description ==
Line 27: Line 28:
 
== Scope ==
 
== Scope ==
  
Every device with a DisplayPort PHY will almost certainly need driver work to enable it.  At the moment this includes the big three of intel, radeon, and nouveau.  Some DisplayPort functionality will likely be common among all devices and can be lifted to helper routines in the X server or drm core.
+
Every device with a DisplayPort PHY will almost certainly need driver work to enable it.  At the moment this includes the big three of intel, radeon, and nouveau.  This feature only covers the intel driver.  See the [[Features/RadeonDisplayPort|Radeon DisplayPort feature]] and the [[Features/NouveauDisplayPort|Nouveau DisplayPort feature]] for the other two.  Some DisplayPort functionality will likely be common among all devices and can be lifted to helper routines in the X server or drm core.
  
 
Affected packages:
 
Affected packages:
Line 33: Line 34:
 
* kernel
 
* kernel
 
* xorg-x11-server
 
* xorg-x11-server
* xorg-x11-drv-{ati,intel,nouveau}
+
* xorg-x11-drv-intel
  
 
== How To Test ==
 
== How To Test ==
  
See this grid? Fill it in.
+
Test hardware with display port sources by connecting to a DisplayPort sink, DP-to-HDMI converter, DP-to-DVI converter, and DP-to-VGA converter. For each of these cases, also test hotplug switching.  When laptops start showing up with embedded DisplayPort support, test the internal laptop screen.
  
{|
+
Known DP sinks:
! Device !! DisplayPort sink !! DP-to-HDMI converter !! DP-to-DVI converter !! DP-to-VGA converter !! Embedded DP
+
|-
+
| ATI Radeon, UNIPHY (>=RV630) || ? || ? || ? || ? || ?
+
|-
+
| ATI Radeon, Kaleidoscope (<RV630) || ? || ? || ? || ? || ?
+
|-
+
| Intel GM45 || ? || ? || ? || ? || ?
+
|-
+
| NVIDIA || ? || ? || ? || ? || ?
+
|}
+
  
For full rigor points, make another set of grids per device class, with DP/HDMI/DVI/VGA as both rows and columns, and test hotplug switching between all cases.
+
* Apple: 24" LED
 +
* Dell: 2408WFP, 3008WFP
 +
* HP: LP2275w, LP2480zx
  
 
== User Experience ==
 
== User Experience ==
Line 58: Line 51:
  
 
== Dependencies ==
 
== Dependencies ==
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel feature)? -->
 
  
 
DisplayPort sinks with EDID are required to support EDID 1.4.  This is landed.
 
DisplayPort sinks with EDID are required to support EDID 1.4.  This is landed.
  
eDP sinks may use DisplayID instead.  This is [http://people.freedesktop.org/~ajax/patches/displayid.patch kind of written], but we don't have any eDP devices to test with yet, so who knows.
+
eDP sinks may use DisplayID instead.  X [http://cgit.freedesktop.org/xorg/xserver/commit/?id=0bb9a7e1650180a24246d14493a8168487cf8914 implements] a DisplayID decode but no fetch mechanism.  But we don't have any eDP devices to test with yet, so who knows.
  
 
Possible common functionality: link/lane computation, manual link training, dongle identification, various other AUXCH services.
 
Possible common functionality: link/lane computation, manual link training, dongle identification, various other AUXCH services.
Line 74: Line 66:
 
== Documentation ==
 
== Documentation ==
  
'''FIXME''': None yet.
+
Ideally, none needed, besides "DisplayPort just works now".  It's not like we have documentation for DVI.
  
 
== Release Notes ==
 
== Release Notes ==
Line 83: Line 75:
 
* See [[Talk:Features/DisplayPort]]  
 
* See [[Talk:Features/DisplayPort]]  
  
[[Category:FeatureReadyForWrangler]]
+
[[Category:FeatureAcceptedF12]]
 
<!-- When your feature page is completed and ready for review -->
 
<!-- When your feature page is completed and ready for review -->
 
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->
 
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->
 
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete-->
 
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete-->
 
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->
 
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->

Latest revision as of 23:30, 13 October 2009

Contents

[edit] DisplayPort support for Intel

[edit] Summary

Enhanced support for DisplayPort in X and kernel drivers for Intel hardware.

[edit] Owner

[edit] Current status

  • Targeted release: Fedora 12
  • Last updated: 2009-10-08
  • Percentage of completion: 100%

The intel driver has DisplayPort and embedded-DP support.

[edit] Detailed Description

DisplayPort is a new digital display connector and protocol. While much more capable than DVI, it's also much more complicated, and some work is needed to take advantage of it.

[edit] Benefit to Fedora

DisplayPort has a higher link bandwidth than dual-link DVI. Monitors can take advantage of this by providing higher resolutions, higher color depths, and higher refresh rates. DisplayPort also runs at a lower voltage than DVI and LVDS, using less power. Future laptops will likely switch to embedded DisplayPort for the local panel for this reason. With this feature, Fedora users can take advantage of the the technical superiority of DisplayPort.

[edit] Scope

Every device with a DisplayPort PHY will almost certainly need driver work to enable it. At the moment this includes the big three of intel, radeon, and nouveau. This feature only covers the intel driver. See the Radeon DisplayPort feature and the Nouveau DisplayPort feature for the other two. Some DisplayPort functionality will likely be common among all devices and can be lifted to helper routines in the X server or drm core.

Affected packages:

  • kernel
  • xorg-x11-server
  • xorg-x11-drv-intel

[edit] How To Test

Test hardware with display port sources by connecting to a DisplayPort sink, DP-to-HDMI converter, DP-to-DVI converter, and DP-to-VGA converter. For each of these cases, also test hotplug switching. When laptops start showing up with embedded DisplayPort support, test the internal laptop screen.

Known DP sinks:

  • Apple: 24" LED
  • Dell: 2408WFP, 3008WFP
  • HP: LP2275w, LP2480zx

[edit] User Experience

DisplayPort connections should Just Work.

[edit] Dependencies

DisplayPort sinks with EDID are required to support EDID 1.4. This is landed.

eDP sinks may use DisplayID instead. X implements a DisplayID decode but no fetch mechanism. But we don't have any eDP devices to test with yet, so who knows.

Possible common functionality: link/lane computation, manual link training, dongle identification, various other AUXCH services.

Some IHV communication may be necessary to get details on specific DP PHYs.

[edit] Contingency Plan

None necessary. It doesn't work in F11, so it can continue to not work in F12.

[edit] Documentation

Ideally, none needed, besides "DisplayPort just works now". It's not like we have documentation for DVI.

[edit] Release Notes

DisplayPort is likely to require kernel support in a much stronger way than DVI, since hotplugging the monitor requires another link training cycle, and the only reliable way to detect that is with interrupts. UMS configurations may accidentally work in some situations, but this is not recommended.

[edit] Comments and Discussion