| /Linux-v5.4/drivers/gpu/drm/selftests/ |
| D | test-drm_damage_helper.c | 287 struct drm_mode_rect damage; in igt_damage_iter_simple_damage() local
305 set_damage_clip(&damage, 0, 0, 1024, 768); in igt_damage_iter_simple_damage()
306 set_damage_blob(&damage_blob, &damage, sizeof(damage)); in igt_damage_iter_simple_damage()
323 struct drm_mode_rect damage; in igt_damage_iter_single_damage() local
340 set_damage_clip(&damage, 256, 192, 768, 576); in igt_damage_iter_single_damage()
341 set_damage_blob(&damage_blob, &damage, sizeof(damage)); in igt_damage_iter_single_damage()
358 struct drm_mode_rect damage; in igt_damage_iter_single_damage_intersect_src() local
376 set_damage_clip(&damage, 256, 192, 1360, 768); in igt_damage_iter_single_damage_intersect_src()
377 set_damage_blob(&damage_blob, &damage, sizeof(damage)); in igt_damage_iter_single_damage_intersect_src()
394 struct drm_mode_rect damage; in igt_damage_iter_single_damage_outside_src() local
[all …]
|
| /Linux-v5.4/drivers/gpu/drm/ |
| D | drm_damage_helper.c | 166 struct drm_property_blob *damage = NULL; in drm_atomic_helper_dirtyfb() local
201 damage = drm_property_create_blob(fb->dev, in drm_atomic_helper_dirtyfb()
204 if (IS_ERR(damage)) { in drm_atomic_helper_dirtyfb()
205 ret = PTR_ERR(damage); in drm_atomic_helper_dirtyfb()
206 damage = NULL; in drm_atomic_helper_dirtyfb()
225 damage); in drm_atomic_helper_dirtyfb()
238 drm_property_blob_put(damage); in drm_atomic_helper_dirtyfb()
|
| /Linux-v5.4/Documentation/fb/ |
| D | udlfb.rst | 47 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
107 report damage, should be able to work with this enabled.
|
| /Linux-v5.4/Documentation/x86/ |
| D | tlb.rst | 11 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-v5.4/Documentation/core-api/ |
| D | debug-objects.rst | 79 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-v5.4/drivers/staging/olpc_dcon/ |
| D | TODO | 6 drm damage tracking and self-refresh helpers.
|
| /Linux-v5.4/Documentation/power/regulator/ |
| D | design.rst | 12 for the system, potentially including lasting hardware damage.
|
| D | overview.rst | 165 provide regulator constraints that will prevent device damage through
|
| /Linux-v5.4/drivers/regulator/ |
| D | max8997-regulator.c | 621 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-v5.4/drivers/memstick/core/ |
| D | Kconfig | 38 Driver is new and not yet well tested, thus it can damage your card
|
| /Linux-v5.4/arch/powerpc/boot/dts/fsl/ |
| D | b4420qds.dts | 32 * this software, even if advised of the possibility of such damage.
|
| D | b4420si-pre.dtsi | 32 * this software, even if advised of the possibility of such damage.
|
| D | b4420si-post.dtsi | 32 * this software, even if advised of the possibility of such damage.
|
| D | p5040si-pre.dtsi | 32 * software, even if advised of the possibility of such damage.
|
| D | b4qds.dtsi | 32 * this software, even if advised of the possibility of such damage.
|
| /Linux-v5.4/drivers/scsi/smartpqi/ |
| D | Kconfig | 28 # the risks and costs of program errors, damage to or loss of data,
|
| /Linux-v5.4/include/uapi/linux/ |
| D | cdrom.h | 863 __u8 damage : 1; member
877 __u8 damage : 1; member
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | ntfs.txt | 373 correctly to avoid the possibility of causing damage to the data on the ntfs
392 superblock used by the MD driver would damage the NTFS volume.
420 are working read-only when playing with this as you may damage your data
433 setup correctly to avoid the possibility of causing damage to the data on the
444 will cause massive damage to the data on the volume which will only become
|
| D | ocfs2-online-filecheck.txt | 34 may end up with more damage than before the repair attempt. So, this has to
|
| /Linux-v5.4/drivers/scsi/mpt3sas/ |
| D | Kconfig | 26 # the risks and costs of program errors, damage to or loss of data,
|
| /Linux-v5.4/Documentation/scsi/ |
| D | dpti.txt | 17 * of the possibility of such damage.
|
| /Linux-v5.4/fs/ntfs/ |
| D | Kconfig | 64 While we cannot guarantee that it will not damage any data, we have
|
| /Linux-v5.4/Documentation/media/uapi/v4l/ |
| D | vidioc-dbg-g-register.rst | 55 security, its stability and damage the hardware, both ioctls require
|
| /Linux-v5.4/Documentation/hwmon/ |
| D | k10temp.rst | 118 which the processor will throttle itself to avoid damage is available in
|
| /Linux-v5.4/drivers/scsi/ufs/ |
| D | Kconfig | 29 # program errors, damage to or loss of data, programs or equipment,
|
