drm/i915: Use correct reST syntax for WOPCM and GuC kernel-doc diagrams
GuC Address Space and WOPCM Layout diagrams won't be generated correctly by sphinx build if not using proper reST syntax. This patch uses reST literal blocks to make sure GuC Address Space and WOPCM Layout diagrams to be generated correctly, and it also corrects some errors in the diagram description. v2: - Fixed errors in diagram description v3: - Updated GuC Address Space kernel-doc based on Michal's suggestion v4: - Added WOPCM layout and GuC address space docs into i915.rst (Joonas) Signed-off-by: Jackie Li <yaodong.li@intel.com> Cc: Michal Wajdeczko <michal.wajdeczko@intel.com> Cc: Sagar Arun Kamble <sagar.a.kamble@intel.com> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com> Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com> Signed-off-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/1521763162-11424-1-git-send-email-yaodong.li@intel.com
This commit is contained in:

committed by
Joonas Lahtinen

parent
7fd9e82993
commit
fbe6f8f2a6
@@ -11,28 +11,30 @@
|
||||
* DOC: WOPCM Layout
|
||||
*
|
||||
* The layout of the WOPCM will be fixed after writing to GuC WOPCM size and
|
||||
* offset registers whose are calculated are determined by size of HuC/GuC
|
||||
* firmware size and set of hw requirements/restrictions as shown below:
|
||||
* offset registers whose values are calculated and determined by HuC/GuC
|
||||
* firmware size and set of hardware requirements/restrictions as shown below:
|
||||
*
|
||||
* +=========> +====================+ <== WOPCM Top
|
||||
* ^ | HW contexts RSVD |
|
||||
* | +===> +====================+ <== GuC WOPCM Top
|
||||
* | ^ | |
|
||||
* | | | |
|
||||
* | | | |
|
||||
* | GuC | |
|
||||
* | WOPCM | |
|
||||
* | Size +--------------------+
|
||||
* WOPCM | | GuC FW RSVD |
|
||||
* | | +--------------------+
|
||||
* | | | GuC Stack RSVD |
|
||||
* | | +------------------- +
|
||||
* | v | GuC WOPCM RSVD |
|
||||
* | +===> +====================+ <== GuC WOPCM base
|
||||
* | | WOPCM RSVD |
|
||||
* | +------------------- + <== HuC Firmware Top
|
||||
* v | HuC FW |
|
||||
* +=========> +====================+ <== WOPCM Base
|
||||
* ::
|
||||
*
|
||||
* +=========> +====================+ <== WOPCM Top
|
||||
* ^ | HW contexts RSVD |
|
||||
* | +===> +====================+ <== GuC WOPCM Top
|
||||
* | ^ | |
|
||||
* | | | |
|
||||
* | | | |
|
||||
* | GuC | |
|
||||
* | WOPCM | |
|
||||
* | Size +--------------------+
|
||||
* WOPCM | | GuC FW RSVD |
|
||||
* | | +--------------------+
|
||||
* | | | GuC Stack RSVD |
|
||||
* | | +------------------- +
|
||||
* | v | GuC WOPCM RSVD |
|
||||
* | +===> +====================+ <== GuC WOPCM base
|
||||
* | | WOPCM RSVD |
|
||||
* | +------------------- + <== HuC Firmware Top
|
||||
* v | HuC FW |
|
||||
* +=========> +====================+ <== WOPCM Base
|
||||
*
|
||||
* GuC accessible WOPCM starts at GuC WOPCM base and ends at GuC WOPCM top.
|
||||
* The top part of the WOPCM is reserved for hardware contexts (e.g. RC6
|
||||
|
Reference in New Issue
Block a user