drm/docs: Fix usage stats typos
Subsystems (3)
PATCH 1/1 drm/docs: Fix usage stats typos
From: Rob Clark <[email protected]>
Fix a couple missing ':'s.
Signed-off-by Rob Clark <[email protected]>
--- Documentation/gpu/drm-usage-stats.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
Documentation/gpu/drm-usage-stats.rst +2 -2
@@ -105,7 +105,7 @@ object belong to this client, in the respective memory region. Default unit shall be bytes with optional unit specifiers of 'KiB' or 'MiB' indicating kibi- or mebi-bytes. -- drm-cycles-<str> <uint> +- drm-cycles-<str>: <uint> Engine identifier string must be the same as the one specified in the drm-engine-<str> tag and shall contain the number of busy cycles for the given
@@ -117,7 +117,7 @@ larger value within a reasonable period. Upon observing a value lower than what was previously read, userspace is expected to stay with that larger previous value until a monotonic update is seen. -- drm-maxfreq-<str> <uint> [Hz|MHz|KHz] +- drm-maxfreq-<str>: <uint> [Hz|MHz|KHz] Engine identifier string must be the same as the one specified in the drm-engine-<str> tag and shall contain the maximum frequency for the given
Signature · 1 line
2.39.2
Quoted 5 lines · Rob Clark
From: Rob Clark <[email protected]>
Fix a couple missing ':'s.
Signed-off-by Rob Clark <[email protected]>
Reviewed-by Rodrigo Vivi <[email protected]>
Quoted 29 lines
--- Documentation/gpu/drm-usage-stats.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)Documentation/gpu/drm-usage-stats.rst +2
-2@@ -105,7 +105,7 @@ object belong to this client, in the respective memory region. Default unit shall be bytes with optional unit specifiers of 'KiB' or 'MiB' indicating kibi- or mebi-bytes. -- drm-cycles-<str> <uint> +- drm-cycles-<str>: <uint> Engine identifier string must be the same as the one specified in the drm-engine-<str> tag and shall contain the number of busy cycles for the given@@ -117,7 +117,7 @@ larger value within a reasonable period. Upon observing a value lower than what was previously read, userspace is expected to stay with that larger previous value until a monotonic update is seen. -- drm-maxfreq-<str> <uint> [Hz|MHz|KHz] +- drm-maxfreq-<str>: <uint> [Hz|MHz|KHz] Engine identifier string must be the same as the one specified in the drm-engine-<str> tag and shall contain the maximum frequency for the givenSignature · 1 line
2.39.2