|
135 | 135 | * are underneath planes with higher Z position values. Two planes with the
|
136 | 136 | * same Z position value have undefined ordering. Note that the Z position
|
137 | 137 | * value can also be immutable, to inform userspace about the hard-coded
|
138 |
| - * stacking of planes, see drm_plane_create_zpos_immutable_property(). |
| 138 | + * stacking of planes, see drm_plane_create_zpos_immutable_property(). If |
| 139 | + * any plane has a zpos property (either mutable or immutable), then all |
| 140 | + * planes shall have a zpos property. |
139 | 141 | *
|
140 | 142 | * pixel blend mode:
|
141 | 143 | * Pixel blend mode is set up with drm_plane_create_blend_mode_property().
|
@@ -344,10 +346,10 @@ EXPORT_SYMBOL(drm_rotation_simplify);
|
344 | 346 | * should be set to 0 and max to maximal number of planes for given crtc - 1.
|
345 | 347 | *
|
346 | 348 | * If zpos of some planes cannot be changed (like fixed background or
|
347 |
| - * cursor/topmost planes), driver should adjust min/max values and assign those |
348 |
| - * planes immutable zpos property with lower or higher values (for more |
| 349 | + * cursor/topmost planes), drivers shall adjust the min/max values and assign |
| 350 | + * those planes immutable zpos properties with lower or higher values (for more |
349 | 351 | * information, see drm_plane_create_zpos_immutable_property() function). In such
|
350 |
| - * case driver should also assign proper initial zpos values for all planes in |
| 352 | + * case drivers shall also assign proper initial zpos values for all planes in |
351 | 353 | * its plane_reset() callback, so the planes will be always sorted properly.
|
352 | 354 | *
|
353 | 355 | * See also drm_atomic_normalize_zpos().
|
|
0 commit comments