tree: 8b88aeb41d7216dcabee3f0dda3a41f476fa6d9b [path history] [tgz]
  1. clock/
  2. bind_tests.json
  3. BUILD.gn
  4. ddi.cc
  5. ddi.h
  6. display-device.cc
  7. display-device.h
  8. dp-capabilities-unittest.cc
  9. dp-display-unittest.cc
  10. dp-display.cc
  11. dp-display.h
  12. dpcd.h
  13. dpll.cc
  14. dpll.h
  15. fake-dpcd-channel.cc
  16. fake-dpcd-channel.h
  17. gtt-unittest.cc
  18. gtt.cc
  19. gtt.h
  20. hdmi-display.cc
  21. hdmi-display.h
  22. igd.cc
  23. igd.h
  24. intel-i915-info.json
  25. intel-i915-test.cc
  26. intel-i915.bind
  27. intel-i915.cc
  28. intel-i915.h
  29. interrupts-unittest.cc
  30. interrupts.cc
  31. interrupts.h
  32. macros.h
  33. pci-ids.h
  34. pipe-unittest.cc
  35. pipe.cc
  36. pipe.h
  37. power-unittest.cc
  38. power.cc
  39. power.h
  40. README.md
  41. registers-ddi.h
  42. registers-dpll.h
  43. registers-pipe.h
  44. registers-transcoder.h
  45. registers-unittest.cc
  46. registers.h
  47. tiling.h
src/graphics/display/drivers/intel-i915/README.md

Display Driver for Intel GPUs

Target Hardware

Changes to the driver should be reviewed against the documentation for the following hardware.

  • Tiger Lake - on Intel NUC11
  • Kaby Lake - on Google Pixelbook (eve), Google Pixelbook Go (atlas), and Intel NUC7
  • Skylake - on Acer Switch Alpha 12

Some of the hardware listed here is not supported, meaning we don't regularly run tests on it. The hardware development page on fuchsia.dev has the most up to date hardware support status.

Documentation References

The driver code here is based on the Programmer's Reference Manuals published by Intel for graphics driver developers.

To facilitate reviews, driver code should include comments pointing to the relevant manual sections. Reference comments should include the following parts:

  1. The document reference ID, such as IHD-OS-TGL-Vol 2c-12.21. This facilitates searching for a downloadable version of the manual.
  2. The section title, such as "Sequences for DisplayPort" > "Enable Sequence". This facilitates searching for equivalent information in a different manual. This example uses a two-level section name because "Enable Sequence" is too generic, resulting in too many hits.
  3. A part number, if the document is split in multiple parts. For example, IHD-OS-TGL-Vol 2c-12.21 is split into two parts. Without a Part 1 / Part 2 qualifier, page numbers would be ambiguous.
  4. A page number or page range, such as pages 143-145. This optimizes for reviewers who need to check that the code matches the documentation.

The most relevant manuals for this driver are: