Home
last modified time | relevance | path

Searched full:damage (Results 1 – 25 of 978) sorted by relevance

12345678910>>...40

/Linux-v6.1/drivers/gpu/drm/tests/
Ddrm_damage_helper_test.c102 * Round down x1/y1 and round up x2/y2. This is because damage is not in in check_damage_clip()
111 KUNIT_FAIL(test, "Cannot have damage clip with no dimension."); in check_damage_clip()
113 KUNIT_FAIL(test, "Damage cannot be outside rounded plane src."); in check_damage_clip()
115 KUNIT_FAIL(test, "Damage = %d %d %d %d, want = %d %d %d %d", in check_damage_clip()
133 KUNIT_EXPECT_EQ_MSG(test, num_hits, 1, "Should return plane src as damage."); in drm_test_damage_iter_no_damage()
154 "Should return rounded off plane src as damage."); in drm_test_damage_iter_no_damage_fractional_src()
173 KUNIT_EXPECT_EQ_MSG(test, num_hits, 1, "Should return plane src as damage."); in drm_test_damage_iter_no_damage_src_moved()
193 KUNIT_EXPECT_EQ_MSG(test, num_hits, 1, "Should return plane src as damage."); in drm_test_damage_iter_no_damage_fractional_src_moved()
212 KUNIT_EXPECT_EQ_MSG(test, num_hits, 0, "Should have no damage."); in drm_test_damage_iter_no_damage_not_visible()
230 KUNIT_EXPECT_EQ_MSG(test, num_hits, 0, "Should have no damage."); in drm_test_damage_iter_no_damage_no_crtc()
[all …]
/Linux-v6.1/drivers/gpu/drm/
Ddrm_damage_helper.c54 * drm_atomic_helper_check_plane_damage - Verify plane damage on atomic_check.
56 * @plane_state: Plane state for which to verify damage.
58 * This helper function makes sure that damage from plane state is discarded
60 * plane update rather than processing individual damage regions, then those
65 * &drm_plane_state.src as damage.
96 * A helper to implement &drm_framebuffer_funcs.dirty using damage interface
113 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()
[all …]
Ddrm_plane.c1405 * DOC: damage tracking
1408 * specify a list of damage rectangles on a plane in framebuffer coordinates of
1409 * the framebuffer attached to the plane. In current context damage is the area
1419 * ignore damage clips property and in that case driver will do a full plane
1420 * update. In case damage clips are provided then it is guaranteed that the area
1421 * inside damage clips will be updated to plane. For efficiency driver can do
1422 * full update or can update more than specified in damage clips. Since driver
1425 * provides damage clips which doesn't encompass the actual damage to
1430 * damage clips are not in 16.16 fixed point. Similar to plane src in
1431 * framebuffer, damage clips cannot be negative. In damage clip, x1/y1 are
[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 …]
/Linux-v6.1/arch/s390/include/asm/
Dnmi.h41 u64 sd : 1; /* 00 system damage */
42 u64 pd : 1; /* 01 instruction-processing damage */
45 u64 cd : 1; /* 04 timing-facility damage */
46 u64 ed : 1; /* 05 external damage */
51 u64 sp : 1; /* 10 service-processor damage */
52 u64 ck : 1; /* 11 channel-subsystem damage */
66 u64 ec : 1; /* 26 external damage code validity */
/Linux-v6.1/include/drm/
Ddrm_damage_helper.h38 * 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-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
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
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/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/arch/s390/kernel/
Dnmi.c386 #define ED_STP_ISLAND 6 /* External damage STP island check */
387 #define ED_STP_SYNC 7 /* External damage STP sync check */
450 /* Processing damage -> stopping machine */ in s390_do_machine_check()
472 /* Timing facility damage */ in s390_do_machine_check()
476 /* External damage */ in s390_do_machine_check()
496 * If there are only Channel Report Pending and External Damage in s390_do_machine_check()
523 ctl_set_bit(14, 25); /* enable external damage MCH */ in machine_check_init()
/Linux-v6.1/Documentation/devicetree/bindings/regulator/
Dregulator.yaml129 the hardware propably is malfunctional and damage prevention is requested.
149 the hardware propably is malfunctional and damage prevention is requested
171 the hardware propably is malfunctional and damage prevention is requested
192 the hardware propably is malfunctional and damage prevention is requested
/Linux-v6.1/drivers/gpu/drm/vmwgfx/
Dvmwgfx_kms.h60 * damage clips on display unit @num_hits will be passed to allocate
99 * if needed. This will be called times have damage in display unit,
100 * which is one if doing full update. @clip is the damage in destination
101 * coordinates which is crtc/DU and @src_x, @src_y is damage clip src in
147 * @fb_left: x1 for fb damage bounding box.
148 * @fb_top: y1 for fb damage bounding box.
/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/drivers/net/ethernet/amd/xgbe/
Dxgbe-ptp.c54 * THE POSSIBILITY OF SUCH DAMAGE.
82 * THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
114 * THE POSSIBILITY OF SUCH DAMAGE.
Dxgbe-dcb.c54 * THE POSSIBILITY OF SUCH DAMAGE.
82 * THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
114 * THE POSSIBILITY OF SUCH DAMAGE.
/Linux-v6.1/arch/mips/cavium-octeon/executive/
Dcvmx-helper-jtag.c44 * can cause chip damage.
127 * chain. Updating invalid values can possibly cause chip damage.
/Linux-v6.1/drivers/staging/olpc_dcon/
DTODO6 drm damage tracking and self-refresh helpers.
/Linux-v6.1/include/sound/
Dwm9090.h19 * potentially causing hardware damage.
/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/drivers/memstick/core/
DKconfig38 Driver is new and not yet well tested, thus it can damage your card
/Linux-v6.1/include/dt-bindings/pinctrl/
Ddm814x.h17 * (bit 18 set) for all 3.3V I/Os to avoid cumulative hardware damage. For
/Linux-v6.1/Documentation/devicetree/bindings/leds/backlight/
Dcommon.yaml32 that a LED can be made so bright that it gets damaged or causes damage
/Linux-v6.1/include/linux/
Dsoundcard.h22 * SUCH DAMAGE.
/Linux-v6.1/Documentation/power/regulator/
Ddesign.rst12 for the system, potentially including lasting hardware damage.
/Linux-v6.1/arch/arm/boot/dts/
Dbcm9hmidc.dtsi30 * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

12345678910>>...40