Home
last modified time | relevance | path

Searched refs:damage (Results 1 – 25 of 70) sorted by relevance

123

/Linux-v6.1/drivers/gpu/drm/tests/
Ddrm_damage_helper_test.c256 struct drm_mode_rect damage; in drm_test_damage_iter_simple_damage() local
263 set_damage_clip(&damage, 0, 0, 1024, 768); in drm_test_damage_iter_simple_damage()
264 set_damage_blob(&damage_blob, &damage, sizeof(damage)); in drm_test_damage_iter_simple_damage()
279 struct drm_mode_rect damage; in drm_test_damage_iter_single_damage() local
285 set_damage_clip(&damage, 256, 192, 768, 576); in drm_test_damage_iter_single_damage()
286 set_damage_blob(&damage_blob, &damage, sizeof(damage)); in drm_test_damage_iter_single_damage()
301 struct drm_mode_rect damage; in drm_test_damage_iter_single_damage_intersect_src() local
308 set_damage_clip(&damage, 256, 192, 1360, 768); in drm_test_damage_iter_single_damage_intersect_src()
309 set_damage_blob(&damage_blob, &damage, sizeof(damage)); in drm_test_damage_iter_single_damage_intersect_src()
324 struct drm_mode_rect damage; in drm_test_damage_iter_single_damage_outside_src() local
[all …]
/Linux-v6.1/drivers/gpu/drm/gud/
Dgud_pipe.c330 gdrm->damage.x1 = INT_MAX; in gud_clear_damage()
331 gdrm->damage.y1 = INT_MAX; in gud_clear_damage()
332 gdrm->damage.x2 = 0; in gud_clear_damage()
333 gdrm->damage.y2 = 0; in gud_clear_damage()
336 static void gud_add_damage(struct gud_device *gdrm, struct drm_rect *damage) in gud_add_damage() argument
338 gdrm->damage.x1 = min(gdrm->damage.x1, damage->x1); in gud_add_damage()
339 gdrm->damage.y1 = min(gdrm->damage.y1, damage->y1); in gud_add_damage()
340 gdrm->damage.x2 = max(gdrm->damage.x2, damage->x2); in gud_add_damage()
341 gdrm->damage.y2 = max(gdrm->damage.y2, damage->y2); in gud_add_damage()
345 struct drm_rect *damage) in gud_retry_failed_flush() argument
[all …]
Dgud_internal.h44 struct drm_rect damage; member
/Linux-v6.1/drivers/gpu/drm/
Ddrm_damage_helper.c113 struct drm_property_blob *damage = NULL; in drm_atomic_helper_dirtyfb() local
148 damage = drm_property_create_blob(fb->dev, in drm_atomic_helper_dirtyfb()
151 if (IS_ERR(damage)) { in drm_atomic_helper_dirtyfb()
152 ret = PTR_ERR(damage); in drm_atomic_helper_dirtyfb()
153 damage = NULL; in drm_atomic_helper_dirtyfb()
178 damage); in drm_atomic_helper_dirtyfb()
191 drm_property_blob_put(damage); in drm_atomic_helper_dirtyfb()
/Linux-v6.1/Documentation/fb/
Dudlfb.rst47 Accurate damage/changed area notifications work around this problem.
49 interface to allow mmap clients to report damage, for the benefit
69 application must send down damage notifications to trigger repaints of the
79 damage interface (which will hopefully be standardized for all virtual
80 framebuffers that need damage info). These damage notifications allow
114 report damage, should be able to work with this enabled.
/Linux-v6.1/Documentation/x86/
Dtlb.rst11 a quick operation, but it causes collateral damage: TLB entries
17 damage to other TLB entries.
25 be no collateral damage caused by doing the global flush, and
29 damage we do with a full flush. So, the larger the TLB, the
/Linux-v6.1/Documentation/hwmon/
Ddrivetemp.rst61 this temperature may cause physical damage to the
66 this temperature may cause physical damage to the
/Linux-v6.1/Documentation/core-api/
Ddebug-objects.rst79 can deactivate an active object in order to prevent damage to the
102 can deactivate an active object in order to prevent damage to the
126 deactivate an active object in order to prevent damage to the subsystem.
166 deactivate an active object in order to prevent damage to the subsystem.
182 prevent damage to the subsystem.
225 again, after the damage has been repaired in order to keep the state
244 function again after the damage has been repaired in order to keep the
/Linux-v6.1/drivers/staging/olpc_dcon/
DTODO6 drm damage tracking and self-refresh helpers.
/Linux-v6.1/drivers/gpu/drm/tiny/
Dsimpledrm.c482 struct drm_rect damage; in simpledrm_primary_plane_helper_atomic_update() local
493 drm_atomic_for_each_plane_damage(&iter, &damage) { in simpledrm_primary_plane_helper_atomic_update()
497 if (!drm_rect_intersect(&dst_clip, &damage)) in simpledrm_primary_plane_helper_atomic_update()
502 &damage); in simpledrm_primary_plane_helper_atomic_update()
/Linux-v6.1/Documentation/power/regulator/
Ddesign.rst12 for the system, potentially including lasting hardware damage.
/Linux-v6.1/drivers/regulator/
Dmax8997-regulator.c621 int new_val, new_idx, damage, tmp_val, tmp_idx, tmp_dmg; in max8997_set_voltage_buck() local
655 damage = max8997_assess_side_effect(rdev, new_val, &new_idx); in max8997_set_voltage_buck()
656 if (damage == 0) in max8997_set_voltage_buck()
659 if (tmp_dmg > damage) { in max8997_set_voltage_buck()
662 tmp_dmg = damage; in max8997_set_voltage_buck()
/Linux-v6.1/drivers/memstick/core/
DKconfig38 Driver is new and not yet well tested, thus it can damage your card
/Linux-v6.1/drivers/gpu/drm/mgag200/
Dmgag200_mode.c503 struct drm_rect damage; in mgag200_primary_plane_helper_atomic_update() local
510 drm_atomic_for_each_plane_damage(&iter, &damage) { in mgag200_primary_plane_helper_atomic_update()
511 mgag200_handle_damage(mdev, shadow_plane_state->data, fb, &damage); in mgag200_primary_plane_helper_atomic_update()
/Linux-v6.1/arch/powerpc/boot/dts/fsl/
Db4420qds.dts32 * this software, even if advised of the possibility of such damage.
Db4420si-pre.dtsi32 * this software, even if advised of the possibility of such damage.
Db4420si-post.dtsi32 * this software, even if advised of the possibility of such damage.
Dp5040si-pre.dtsi32 * software, even if advised of the possibility of such damage.
/Linux-v6.1/drivers/scsi/smartpqi/
DKconfig28 # the risks and costs of program errors, damage to or loss of data,
/Linux-v6.1/include/uapi/linux/
Dcdrom.h885 __u8 damage : 1; member
899 __u8 damage : 1; member
/Linux-v6.1/Documentation/filesystems/
Dntfs.rst386 correctly to avoid the possibility of causing damage to the data on the ntfs
405 superblock used by the MD driver would damage the NTFS volume.
433 are working read-only when playing with this as you may damage your data
448 setup correctly to avoid the possibility of causing damage to the data on the
459 will cause massive damage to the data on the volume which will only become
/Linux-v6.1/fs/ntfs/
DKconfig65 While we cannot guarantee that it will not damage any data, we have
/Linux-v6.1/drivers/scsi/mpt3sas/
DKconfig26 # the risks and costs of program errors, damage to or loss of data,
/Linux-v6.1/Documentation/scsi/
Ddpti.rst21 of the possibility of such damage.
/Linux-v6.1/Documentation/userspace-api/media/v4l/
Dvidioc-dbg-g-register.rst48 security, its stability and damage the hardware, both ioctls require

123