Searched full:damage (Results 1 – 25 of 1330) sorted by relevance
12345678910>>...54
| /linux-5.10/drivers/gpu/drm/selftests/ |
| D | test-drm_damage_helper.c | 47 * Round down x1/y1 and round up x2/y2. This is because damage is not in in check_damage_clip()
56 pr_err("Cannot have damage clip with no dimension.\n"); in check_damage_clip()
61 pr_err("Damage cannot be outside rounded plane src.\n"); in check_damage_clip()
66 pr_err("Damage = %d %d %d %d\n", r->x1, r->y1, r->x2, r->y2); in check_damage_clip()
98 FAIL(num_hits != 1, "Should return plane src as damage."); in igt_damage_iter_no_damage()
131 FAIL(num_hits != 1, "Should return rounded off plane src as damage."); in igt_damage_iter_no_damage_fractional_src()
163 FAIL(num_hits != 1, "Should return plane src as damage."); in igt_damage_iter_no_damage_src_moved()
196 FAIL(num_hits != 1, "Should return plane src as damage."); in igt_damage_iter_no_damage_fractional_src_moved()
226 FAIL(num_hits != 0, "Should have no damage."); in igt_damage_iter_no_damage_not_visible()
254 FAIL(num_hits != 0, "Should have no damage."); in igt_damage_iter_no_damage_no_crtc()
[all …]
|
| /linux-5.10/drivers/gpu/drm/ |
| D | drm_damage_helper.c | 41 * specify a list of damage rectangles on a plane in framebuffer coordinates of
42 * the framebuffer attached to the plane. In current context damage is the area
52 * ignore damage clips property and in that case driver will do a full plane
53 * update. In case damage clips are provided then it is guaranteed that the area
54 * inside damage clips will be updated to plane. For efficiency driver can do
55 * full update or can update more than specified in damage clips. Since driver
58 * provides damage clips which doesn't encompass the actual damage to
63 * damage clips are not in 16.16 fixed point. Similar to plane src in
64 * framebuffer, damage clips cannot be negative. In damage clip, x1/y1 are
66 * damage clips, it is strongly discouraged.
[all …]
|
| /linux-5.10/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. */
86 * drm_helper_get_plane_damage_clips - Returns damage clips in &drm_rect.
89 * Returns plane damage rectangles in internal &drm_rect. Currently &drm_rect
91 * are signed 32 and during drm_atomic_check_only() it is verified that damage
|
| /linux-5.10/arch/s390/include/asm/ |
| D | nmi.h | 38 u64 sd : 1; /* 00 system damage */
39 u64 pd : 1; /* 01 instruction-processing damage */
42 u64 cd : 1; /* 04 timing-facility damage */
43 u64 ed : 1; /* 05 external damage */
48 u64 sp : 1; /* 10 service-processor damage */
49 u64 ck : 1; /* 11 channel-subsystem damage */
63 u64 ec : 1; /* 26 external damage code validity */
|
| /linux-5.10/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-5.10/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-5.10/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-5.10/arch/s390/kernel/ |
| D | nmi.c | 327 #define ED_STP_ISLAND 6 /* External damage STP island check */
328 #define ED_STP_SYNC 7 /* External damage STP sync check */
352 /* System damage -> stopping machine */ in s390_do_machine_check()
392 /* Processing damage -> stopping machine */ in s390_do_machine_check()
414 /* Timing facility damage */ in s390_do_machine_check()
418 /* External damage */ in s390_do_machine_check()
453 * If there are only Channel Report Pending and External Damage in s390_do_machine_check()
480 ctl_set_bit(14, 25); /* enable external damage MCH */ in machine_check_init()
|
| /linux-5.10/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-5.10/Documentation/hwmon/ |
| D | drivetemp.rst | 61 this temperature may cause physical damage to the
66 this temperature may cause physical damage to the
|
| /linux-5.10/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-5.10/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-5.10/include/sound/ |
| D | wm9090.h | 19 * potentially causing hardware damage.
|
| /linux-5.10/drivers/staging/olpc_dcon/ |
| D | TODO | 6 drm damage tracking and self-refresh helpers.
|
| /linux-5.10/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-5.10/drivers/memstick/core/ |
| D | Kconfig | 38 Driver is new and not yet well tested, thus it can damage your card
|
| /linux-5.10/include/dt-bindings/pinctrl/ |
| D | dm814x.h | 17 * (bit 18 set) for all 3.3V I/Os to avoid cumulative hardware damage. For
|
| /linux-5.10/Documentation/devicetree/bindings/leds/backlight/ |
| D | common.yaml | 32 that a LED can be made so bright that it gets damaged or causes damage
|
| /linux-5.10/scripts/dtc/libfdt/ |
| D | fdt_strerror.c | 5 * EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
| /linux-5.10/Documentation/power/regulator/ |
| D | design.rst | 12 for the system, potentially including lasting hardware damage.
|
| /linux-5.10/include/linux/ |
| D | soundcard.h | 22 * SUCH DAMAGE.
|
| /linux-5.10/arch/arm/boot/dts/ |
| D | bcm9hmidc.dtsi | 30 * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
| /linux-5.10/LICENSES/preferred/ |
| D | BSD-2-Clause | 32 POSSIBILITY OF SUCH DAMAGE.
|
| /linux-5.10/arch/arm/mach-omap1/ |
| D | board-h3.h | 21 * THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
12345678910>>...54