diff options
| author | Ville Syrjälä | 2018-03-06 17:48:47 +0100 |
|---|---|---|
| committer | Ville Syrjälä | 2018-03-07 17:22:05 +0100 |
| commit | 147ccf931e3152e06961bd6d29a5650d25c2f156 (patch) | |
| tree | c3d361e221f0958f9b6559a8ffd3c17a04c487d3 /drivers/gpu/drm/drm_property.c | |
| parent | drm: WARN when trying to add enum value > 63 to a bitmask property (diff) | |
| download | kernel-qcow2-linux-147ccf931e3152e06961bd6d29a5650d25c2f156.tar.gz kernel-qcow2-linux-147ccf931e3152e06961bd6d29a5650d25c2f156.tar.xz kernel-qcow2-linux-147ccf931e3152e06961bd6d29a5650d25c2f156.zip | |
drm/uapi: Deprecate DRM_MODE_PROP_PENDING
DRM_MODE_PROP_PENDING is not used anywhere (except printed out
by libdrm proptest/modetest).
This seems to be yet another thing blindly copied from xrandr.
Quoting from the protocol spec:
"If 'pending' is TRUE, changes made to property values with
RRChangeOutputProperty will be saved in the pending property value
and be automatically copied to the current value on the next
RRSetCrtcConfig request involving the named output. If 'pending' is
FALSE, changes are copied immediately."
So it was some kind of early idea for atomic property updates.
Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20180306164849.2862-4-ville.syrjala@linux.intel.com
Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Diffstat (limited to 'drivers/gpu/drm/drm_property.c')
0 files changed, 0 insertions, 0 deletions