1e1a5e6a8SDaniel Vetter=============== 2e1a5e6a8SDaniel VetterGPU RFC Section 3e1a5e6a8SDaniel Vetter=============== 4e1a5e6a8SDaniel Vetter 5e1a5e6a8SDaniel VetterFor complex work, especially new uapi, it is often good to nail the high level 6e1a5e6a8SDaniel Vetterdesign issues before getting lost in the code details. This section is meant to 7e1a5e6a8SDaniel Vetterhost such documentation: 8e1a5e6a8SDaniel Vetter 9e1a5e6a8SDaniel Vetter* Each RFC should be a section in this file, explaining the goal and main design 10e1a5e6a8SDaniel Vetter considerations. Especially for uapi make sure you Cc: all relevant project 11e1a5e6a8SDaniel Vetter mailing lists and involved people outside of dri-devel. 12e1a5e6a8SDaniel Vetter 13e1a5e6a8SDaniel Vetter* For uapi structures add a file to this directory with and then pull the 14e1a5e6a8SDaniel Vetter kerneldoc in like with real uapi headers. 15e1a5e6a8SDaniel Vetter 16e1a5e6a8SDaniel Vetter* Once the code has landed move all the documentation to the right places in 17e1a5e6a8SDaniel Vetter the main core, helper or driver sections. 182bc9c04eSMatthew Auld 192bc9c04eSMatthew Auld.. toctree:: 202bc9c04eSMatthew Auld 212bc9c04eSMatthew Auld i915_gem_lmem.rst 22f587623bSMatthew Brost 23f587623bSMatthew Brost.. toctree:: 24f587623bSMatthew Brost 25f587623bSMatthew Brost i915_scheduler.rst 26fff1d972SMatthew Auld 27fff1d972SMatthew Auld.. toctree:: 28fff1d972SMatthew Auld 29fff1d972SMatthew Auld i915_small_bar.rst 30ece91c88SNiranjana Vishwanathapura 31ece91c88SNiranjana Vishwanathapura.. toctree:: 32ece91c88SNiranjana Vishwanathapura 33ece91c88SNiranjana Vishwanathapura i915_vm_bind.rst 34*40aeab04SRodrigo Vivi 35*40aeab04SRodrigo Vivi.. toctree:: 36*40aeab04SRodrigo Vivi 37*40aeab04SRodrigo Vivi xe.rst 38