162306a36Sopenharmony_ci=============== 262306a36Sopenharmony_ciGPU RFC Section 362306a36Sopenharmony_ci=============== 462306a36Sopenharmony_ci 562306a36Sopenharmony_ciFor complex work, especially new uapi, it is often good to nail the high level 662306a36Sopenharmony_cidesign issues before getting lost in the code details. This section is meant to 762306a36Sopenharmony_cihost such documentation: 862306a36Sopenharmony_ci 962306a36Sopenharmony_ci* Each RFC should be a section in this file, explaining the goal and main design 1062306a36Sopenharmony_ci considerations. Especially for uapi make sure you Cc: all relevant project 1162306a36Sopenharmony_ci mailing lists and involved people outside of dri-devel. 1262306a36Sopenharmony_ci 1362306a36Sopenharmony_ci* For uapi structures add a file to this directory with and then pull the 1462306a36Sopenharmony_ci kerneldoc in like with real uapi headers. 1562306a36Sopenharmony_ci 1662306a36Sopenharmony_ci* Once the code has landed move all the documentation to the right places in 1762306a36Sopenharmony_ci the main core, helper or driver sections. 1862306a36Sopenharmony_ci 1962306a36Sopenharmony_ci.. toctree:: 2062306a36Sopenharmony_ci 2162306a36Sopenharmony_ci i915_gem_lmem.rst 2262306a36Sopenharmony_ci 2362306a36Sopenharmony_ci.. toctree:: 2462306a36Sopenharmony_ci 2562306a36Sopenharmony_ci i915_scheduler.rst 2662306a36Sopenharmony_ci 2762306a36Sopenharmony_ci.. toctree:: 2862306a36Sopenharmony_ci 2962306a36Sopenharmony_ci i915_small_bar.rst 3062306a36Sopenharmony_ci 3162306a36Sopenharmony_ci.. toctree:: 3262306a36Sopenharmony_ci 3362306a36Sopenharmony_ci i915_vm_bind.rst 3462306a36Sopenharmony_ci 3562306a36Sopenharmony_ci.. toctree:: 3662306a36Sopenharmony_ci 3762306a36Sopenharmony_ci xe.rst 38