From e3841368f34afe844bab25010b89f497cacc1dad Mon Sep 17 00:00:00 2001 From: Marek Olšák Date: Mon, 22 Apr 2019 17:35:27 -0400 Subject: gallium: replace DRM_CONF_THROTTLE with PIPE_CAP_MAX_FRAMES_IN_FLIGHT Reviewed-by: Kenneth Graunke --- src/gallium/docs/source/screen.rst | 3 +++ 1 file changed, 3 insertions(+) (limited to 'src/gallium/docs') diff --git a/src/gallium/docs/source/screen.rst b/src/gallium/docs/source/screen.rst index fcb16aebe2d..60184116312 100644 --- a/src/gallium/docs/source/screen.rst +++ b/src/gallium/docs/source/screen.rst @@ -516,6 +516,9 @@ The integer capabilities: A driver might rely on the input mapping that was defined with the original GLSL code. * ``PIPE_CAP_IMAGE_LOAD_FORMATTED``: True if a format for image loads does not need to be specified in the shader IR +* ``PIPE_CAP_MAX_FRAMES_IN_FLIGHT``: Maximum number of frames that state + trackers should allow to be in flight before throttling pipe_context + execution. 0 = throttling is disabled. .. _pipe_capf: -- cgit v1.2.3