Lines Matching full:drm

4 DRM client usage stats
7 DRM drivers can choose to export partly standardised text output via the
9 in the `struct drm_driver` object registered with the DRM core.
14 Given the differences between various DRM drivers the specification of the
24 - All keys shall be prefixed with `drm-`.
48 - drm-driver: <valstr>
59 - drm-pdev: <aaaa:bb.cc.d>
64 - drm-client-id: <uint>
66 Unique value relating to the open DRM file descriptor used to distinguish
71 scope of each device, in which case `drm-pdev` shall be present as well.
79 - drm-engine-<keystr>: <uint> ns
94 - drm-engine-capacity-<keystr>: <uint>
97 drm-engine-<keystr> tag and shall contain a greater than zero number in case the
103 - drm-cycles-<keystr>: <uint>
106 drm-engine-<keystr> tag and shall contain the number of busy cycles for the given
115 - drm-total-cycles-<keystr>: <uint>
118 drm-cycles-<keystr> tag and shall contain the total number cycles for the given
122 of drm-cycles-<keystr>. For drivers that implement this interface, the engine
126 A driver may implement either this key or drm-maxfreq-<keystr>, but not both.
128 - drm-maxfreq-<keystr>: <uint> [Hz|MHz|KHz]
131 drm-engine-<keystr> tag and shall contain the maximum frequency for the given
132 engine.  Taken together with drm-cycles-<keystr>, this can be used to calculate
133 percentage utilization of the engine, whereas drm-engine-<keystr> only reflects
137 A driver may implement either this key or drm-total-cycles-<keystr>, but not
143 - drm-memory-<region>: <uint> [KiB|MiB]
155 - drm-shared-<region>: <uint> [KiB|MiB]
160 - drm-total-<region>: <uint> [KiB|MiB]
164 - drm-resident-<region>: <uint> [KiB|MiB]
168 - drm-purgeable-<region>: <uint> [KiB|MiB]
172 - drm-active-<region>: <uint> [KiB|MiB]