| /Linux-v5.15/drivers/gpu/drm/selftests/ |
| D | test-drm_damage_helper.c | 76 * Round down x1/y1 and round up x2/y2. This is because damage is not in in check_damage_clip()
85 pr_err("Cannot have damage clip with no dimension.\n"); in check_damage_clip()
90 pr_err("Damage cannot be outside rounded plane src.\n"); in check_damage_clip()
95 pr_err("Damage = %d %d %d %d\n", r->x1, r->y1, r->x2, r->y2); in check_damage_clip()
133 FAIL(num_hits != 1, "Should return plane src as damage."); in igt_damage_iter_no_damage()
156 FAIL(num_hits != 1, "Should return rounded off plane src as damage."); in igt_damage_iter_no_damage_fractional_src()
178 FAIL(num_hits != 1, "Should return plane src as damage."); in igt_damage_iter_no_damage_src_moved()
201 FAIL(num_hits != 1, "Should return plane src as damage."); in igt_damage_iter_no_damage_fractional_src_moved()
225 FAIL(num_hits != 0, "Should have no damage."); in igt_damage_iter_no_damage_not_visible()
246 FAIL(num_hits != 0, "Should have no damage."); in igt_damage_iter_no_damage_no_crtc()
[all …]
|
| /Linux-v5.15/drivers/gpu/drm/ |
| D | drm_damage_helper.c | 53 * drm_atomic_helper_check_plane_damage - Verify plane damage on atomic_check.
55 * @plane_state: Plane state for which to verify damage.
57 * This helper function makes sure that damage from plane state is discarded
59 * plane update rather than processing individual damage regions, then those
64 * &drm_plane_state.src as damage.
95 * A helper to implement &drm_framebuffer_funcs.dirty using damage interface
112 struct drm_property_blob *damage = NULL; in drm_atomic_helper_dirtyfb() local
147 damage = drm_property_create_blob(fb->dev, in drm_atomic_helper_dirtyfb()
150 if (IS_ERR(damage)) { in drm_atomic_helper_dirtyfb()
151 ret = PTR_ERR(damage); in drm_atomic_helper_dirtyfb()
[all …]
|
| D | drm_plane.c | 1401 * DOC: damage tracking
1404 * specify a list of damage rectangles on a plane in framebuffer coordinates of
1405 * the framebuffer attached to the plane. In current context damage is the area
1415 * ignore damage clips property and in that case driver will do a full plane
1416 * update. In case damage clips are provided then it is guaranteed that the area
1417 * inside damage clips will be updated to plane. For efficiency driver can do
1418 * full update or can update more than specified in damage clips. Since driver
1421 * provides damage clips which doesn't encompass the actual damage to
1426 * damage clips are not in 16.16 fixed point. Similar to plane src in
1427 * framebuffer, damage clips cannot be negative. In damage clip, x1/y1 are
[all …]
|
| /Linux-v5.15/drivers/gpu/drm/gud/ |
| D | gud_pipe.c | 316 gdrm->damage.x1 = INT_MAX; in gud_clear_damage()
317 gdrm->damage.y1 = INT_MAX; in gud_clear_damage()
318 gdrm->damage.x2 = 0; in gud_clear_damage()
319 gdrm->damage.y2 = 0; in gud_clear_damage()
322 static void gud_add_damage(struct gud_device *gdrm, struct drm_rect *damage) in gud_add_damage() argument
324 gdrm->damage.x1 = min(gdrm->damage.x1, damage->x1); in gud_add_damage()
325 gdrm->damage.y1 = min(gdrm->damage.y1, damage->y1); in gud_add_damage()
326 gdrm->damage.x2 = max(gdrm->damage.x2, damage->x2); in gud_add_damage()
327 gdrm->damage.y2 = max(gdrm->damage.y2, damage->y2); in gud_add_damage()
331 struct drm_rect *damage) in gud_retry_failed_flush() argument
[all …]
|
| /Linux-v5.15/arch/s390/include/asm/ |
| D | nmi.h | 42 u64 sd : 1; /* 00 system damage */
43 u64 pd : 1; /* 01 instruction-processing damage */
46 u64 cd : 1; /* 04 timing-facility damage */
47 u64 ed : 1; /* 05 external damage */
52 u64 sp : 1; /* 10 service-processor damage */
53 u64 ck : 1; /* 11 channel-subsystem damage */
67 u64 ec : 1; /* 26 external damage code validity */
|
| /Linux-v5.15/include/drm/ |
| D | drm_damage_helper.h | 38 * drm_atomic_for_each_plane_damage - Iterator macro for plane damage.
43 * plane update. Iterator will return full plane src when damage is not passed
50 * struct drm_atomic_helper_damage_iter - Closure structure for damage iterator.
52 * This structure tracks state needed to walk the list of plane damage clips.
57 /* private: Rectangles in plane damage blob. */
59 /* private: Number of rectangles in plane damage blob. */
|
| /Linux-v5.15/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
78 rectangles from the X DAMAGE protocol extension down to udlfb via udlfb's
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.15/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.15/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.15/arch/s390/kernel/ |
| D | nmi.c | 374 #define ED_STP_ISLAND 6 /* External damage STP island check */
375 #define ED_STP_SYNC 7 /* External damage STP sync check */
437 /* Processing damage -> stopping machine */ in s390_do_machine_check()
459 /* Timing facility damage */ in s390_do_machine_check()
463 /* External damage */ in s390_do_machine_check()
483 * If there are only Channel Report Pending and External Damage in s390_do_machine_check()
510 ctl_set_bit(14, 25); /* enable external damage MCH */ in machine_check_init()
|
| /Linux-v5.15/drivers/gpu/drm/vmwgfx/ |
| D | vmwgfx_kms.h | 59 * damage clips on display unit @num_hits will be passed to allocate
98 * if needed. This will be called times have damage in display unit,
99 * which is one if doing full update. @clip is the damage in destination
100 * coordinates which is crtc/DU and @src_x, @src_y is damage clip src in
146 * @fb_left: x1 for fb damage bounding box.
147 * @fb_top: y1 for fb damage bounding box.
|
| /Linux-v5.15/Documentation/devicetree/bindings/regulator/ |
| D | regulator.yaml | 128 the hardware propably is malfunctional and damage prevention is requested.
148 the hardware propably is malfunctional and damage prevention is requested
170 the hardware propably is malfunctional and damage prevention is requested
191 the hardware propably is malfunctional and damage prevention is requested
|
| /Linux-v5.15/Documentation/hwmon/ |
| D | drivetemp.rst | 61 this temperature may cause physical damage to the
66 this temperature may cause physical damage to the
|
| /Linux-v5.15/drivers/net/ethernet/amd/xgbe/ |
| D | xgbe-ptp.c | 54 * THE POSSIBILITY OF SUCH DAMAGE.
82 * THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
114 * THE POSSIBILITY OF SUCH DAMAGE.
|
| D | xgbe-dcb.c | 54 * THE POSSIBILITY OF SUCH DAMAGE.
82 * THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
114 * THE POSSIBILITY OF SUCH DAMAGE.
|
| /Linux-v5.15/arch/mips/cavium-octeon/executive/ |
| D | cvmx-helper-jtag.c | 44 * can cause chip damage.
127 * chain. Updating invalid values can possibly cause chip damage.
|
| /Linux-v5.15/include/sound/ |
| D | wm9090.h | 19 * potentially causing hardware damage.
|
| /Linux-v5.15/drivers/staging/olpc_dcon/ |
| D | TODO | 6 drm damage tracking and self-refresh helpers.
|
| /Linux-v5.15/Documentation/filesystems/ |
| D | ntfs.rst | 386 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-v5.15/drivers/memstick/core/ |
| D | Kconfig | 38 Driver is new and not yet well tested, thus it can damage your card
|
| /Linux-v5.15/include/dt-bindings/pinctrl/ |
| D | dm814x.h | 17 * (bit 18 set) for all 3.3V I/Os to avoid cumulative hardware damage. For
|
| /Linux-v5.15/scripts/dtc/libfdt/ |
| D | fdt_strerror.c | 5 * EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
| /Linux-v5.15/Documentation/power/regulator/ |
| D | design.rst | 12 for the system, potentially including lasting hardware damage.
|
| /Linux-v5.15/include/linux/ |
| D | soundcard.h | 22 * SUCH DAMAGE.
|
| /Linux-v5.15/Documentation/devicetree/bindings/leds/backlight/ |
| D | common.yaml | 32 that a LED can be made so bright that it gets damaged or causes damage
|
