Searched full:damage (Results 1 – 25 of 45) sorted by relevance
12
| /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
114 report damage, should be able to work with this enabled.
|
| /Documentation/arch/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
|
| /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
|
| /Documentation/hwmon/ |
| D | drivetemp.rst | 61 this temperature may cause physical damage to the
66 this temperature may cause physical damage to the
|
| D | k10temp.rst | 119 which the processor will throttle itself to avoid damage is available in
|
| D | pc87360.rst | 115 non-zero, can stop the fan, which may cause irreversible damage to your
|
| /Documentation/devicetree/bindings/regulator/ |
| D | regulator.yaml | 134 the hardware probably is malfunctional and damage prevention is requested.
154 the hardware probably is malfunctional and damage prevention is requested
176 the hardware probably is malfunctional and damage prevention is requested
205 the hardware probably is malfunctional and damage prevention is requested
|
| /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
|
| /Documentation/devicetree/bindings/leds/backlight/ |
| D | common.yaml | 32 that a LED can be made so bright that it gets damaged or causes damage
|
| /Documentation/scsi/ |
| D | LICENSE.FlashPoint | 60 SUCH DAMAGE.
|
| D | dpti.rst | 21 of the possibility of such damage.
|
| /Documentation/devicetree/bindings/thermal/ |
| D | thermal-zones.yaml | 37 having the device in temperature ranges that may damage the silicon structures
85 By default the system will shutdown as a safe action to prevent damage
89 thus leading to infinite reboots that may cause damage to the hardware.
|
| /Documentation/gpu/ |
| D | todo.rst | 814 Buffer age or other damage accumulation algorithm for buffer damage
817 Drivers that do per-buffer uploads, need a buffer damage handling (rather than
818 frame damage like drivers that do per-plane or per-CRTC uploads), but there is
819 no support to get the buffer age or any other damage accumulation algorithm.
821 For this reason, the damage helpers just fallback to a full plane update if the
825 helpers that the damage clips should be ignored.
827 This should be improved to get damage tracking properly working on drivers that
830 More information about damage tracking and references to learning materials can
|
| D | drm-kms.rst | 392 Plane Damage Tracking Functions Reference
575 Damage Tracking Properties
579 :doc: damage tracking
|
| /Documentation/devicetree/bindings/leds/ |
| D | common.yaml | 158 damage in case an excessive current is set.
167 causes damage due to restrictions in a specific system, such as mounting
|
| /Documentation/filesystems/ |
| D | ocfs2-online-filecheck.rst | 37 may end up with more damage than before the repair attempt. So, this has to
|
| D | affs.rst | 194 If the damage is already done, the following should fix the RDB
|
| /Documentation/userspace-api/media/v4l/ |
| D | vidioc-dbg-g-register.rst | 48 security, its stability and damage the hardware, both ioctls require
|
| /Documentation/devicetree/bindings/sound/ |
| D | cs35l35.txt | 76 Serious damage can occur to the Device and surrounding components.
|
| /Documentation/sound/cards/ |
| D | maya44.rst | 137 It might damage the source and/or the maya44 card.
|
| /Documentation/usb/ |
| D | gadget_multi.rst | 106 Failing to comply may cause brain damage after wondering for hours why
|
| /Documentation/admin-guide/laptops/ |
| D | sony-laptop.rst | 167 laptop, including permanent damage.
|
| /Documentation/wmi/devices/ |
| D | msi-wmi-platform.rst | 184 .. warning:: Randomly poking the embedded controller interface can potentially cause damage
|
| /Documentation/translations/zh_CN/doc-guide/ |
| D | kernel-doc.rst | 395 * The only drawback to this gizmo is that is can sometimes damage
|
12