Lines Matching full:damage

1424  * DOC: damage tracking
1427  * specify a list of damage rectangles on a plane in framebuffer coordinates of
1428  * the framebuffer attached to the plane. In current context damage is the area
1438  * ignore damage clips property and in that case driver will do a full plane
1439  * update. In case damage clips are provided then it is guaranteed that the area
1440  * inside damage clips will be updated to plane. For efficiency driver can do
1441  * full update or can update more than specified in damage clips. Since driver
1444  * provides damage clips which doesn't encompass the actual damage to
1449  * damage clips are not in 16.16 fixed point. Similar to plane src in
1450  * framebuffer, damage clips cannot be negative. In damage clip, x1/y1 are
1452  * damage clips, it is strongly discouraged.
1454  * Drivers that are interested in damage interface for plane should enable
1456  * Drivers implementing damage can use drm_atomic_helper_damage_iter_init() and
1457  * drm_atomic_helper_damage_iter_next() helper iterator function to get damage
1462  * drm_plane_enable_fb_damage_clips - Enables plane fb damage clips property.
1463  * @plane: Plane on which to enable damage clips property.
1465  * This function lets driver to enable the damage clips property on a plane.
1478  * drm_plane_get_damage_clips_count - Returns damage clips count.
1502  * drm_plane_get_damage_clips - Returns damage clips.
1508  * the driver can only handle a single damage region at most.
1510  * Return: Damage clips in plane fb_damage_clips blob property.