6c49df92fa
Multiple plane overlay is a feature supported by AMD hardware, but it has specific details that deserve proper documentation. This commit introduces a documentation that describes some of the features, limitations, and use cases for this feature. Part of this documentation came from some discussion in the public upstream [1][2]. [1]. https://lore.kernel.org/amd-gfx/3qY-QeukF_Q_MJeIXAuBjO4szbS4jRtqkTifXnbnN3bp88SxVodFQRpah3mIIVJq24DUkF6g0rOGdCmSqTvVxx9LCGEItmzLw8uWU44jtXE=@emersion.fr/ [2]. https://lore.kernel.org/amd-gfx/864e45d0-c14b-3b12-0f5b-9d26a9cb41bd@amd.com/ Cc: Harry Wentland <harry.wentland@amd.com> Cc: Nicholas Kazlauskas <Nicholas.Kazlauskas@amd.com> Cc: Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com> Cc: Hersen Wu <hersenxs.wu@amd.com> Cc: Alex Hung <alex.hung@amd.com> Cc: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com> Cc: Simon Ser <contact@emersion.fr> Cc: Pekka Paalanen <pekka.paalanen@collabora.com> Cc: Sean Paul <seanpaul@chromium.org> Cc: Mark Yacoub <markyacoub@chromium.org> Cc: Leo Li <sunpeng.li@amd.com> Cc: Pierre-Loup <pgriffais@valvesoftware.com> Cc: Michel Dänzer <michel.daenzer@mailbox.org> Reviewed-by: Harry Wentland <Harry.Wentland@amd.com> Signed-off-by: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
33 lines
1.0 KiB
ReStructuredText
33 lines
1.0 KiB
ReStructuredText
.. _amdgpu-display-core:
|
|
|
|
===================================
|
|
drm/amd/display - Display Core (DC)
|
|
===================================
|
|
|
|
AMD display engine is partially shared with other operating systems; for this
|
|
reason, our Display Core Driver is divided into two pieces:
|
|
|
|
1. **Display Core (DC)** contains the OS-agnostic components. Things like
|
|
hardware programming and resource management are handled here.
|
|
2. **Display Manager (DM)** contains the OS-dependent components. Hooks to the
|
|
amdgpu base driver and DRM are implemented here.
|
|
|
|
The display pipe is responsible for "scanning out" a rendered frame from the
|
|
GPU memory (also called VRAM, FrameBuffer, etc.) to a display. In other words,
|
|
it would:
|
|
|
|
1. Read frame information from memory;
|
|
2. Perform required transformation;
|
|
3. Send pixel data to sink devices.
|
|
|
|
If you want to learn more about our driver details, take a look at the below
|
|
table of content:
|
|
|
|
.. toctree::
|
|
|
|
display-manager.rst
|
|
dc-debug.rst
|
|
dcn-overview.rst
|
|
mpo-overview.rst
|
|
dc-glossary.rst
|