Home
last modified time | relevance | path

Searched refs:damage (Results 1 – 46 of 46) sorted by relevance

/linux-4.1.27/Documentation/fb/
Dudlfb.txt47 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 notifcations 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
106 report damage, should be able to work with this enabled.
/linux-4.1.27/Documentation/x86/
Dtlb.txt4 a quick operation, but it causes collateral damage: TLB entries
10 damage to other TLB entries.
17 be no collateral damage caused by doing the global flush, and
21 damage we do with a full flush. So, the larger the TLB, the
/linux-4.1.27/Documentation/power/regulator/
Ddesign.txt11 for the system, potentially including lasting hardware damage.
Doverview.txt158 provide regulator constraints that will prevent device damage through
/linux-4.1.27/drivers/memstick/core/
DKconfig37 Driver is new and not yet well tested, thus it can damage your card
/linux-4.1.27/drivers/regulator/
Dmax8997.c639 int new_val, new_idx, damage, tmp_val, tmp_idx, tmp_dmg; in max8997_set_voltage_buck() local
673 damage = max8997_assess_side_effect(rdev, new_val, &new_idx); in max8997_set_voltage_buck()
674 if (damage == 0) in max8997_set_voltage_buck()
677 if (tmp_dmg > damage) { in max8997_set_voltage_buck()
680 tmp_dmg = damage; in max8997_set_voltage_buck()
/linux-4.1.27/arch/powerpc/boot/dts/
Db4420qds.dts32 * this software, even if advised of the possibility of such damage.
Db4qds.dtsi32 * this software, even if advised of the possibility of such damage.
Dp5040ds.dts32 * software, even if advised of the possibility of such damage.
/linux-4.1.27/arch/powerpc/boot/dts/fsl/
Db4420si-pre.dtsi32 * this software, even if advised of the possibility of such damage.
Dp5040si-pre.dtsi32 * software, even if advised of the possibility of such damage.
Db4420si-post.dtsi32 * this software, even if advised of the possibility of such damage.
Db4si-post.dtsi32 * this software, even if advised of the possibility of such damage.
Dp5040si-post.dtsi32 * software, even if advised of the possibility of such damage.
/linux-4.1.27/include/uapi/linux/
Dcdrom.h862 __u8 damage : 1; member
876 __u8 damage : 1; member
/linux-4.1.27/drivers/staging/iio/
DTODO24 by a driver of the SoC's battery charging unit to avoid any damage to the
/linux-4.1.27/drivers/scsi/mpt3sas/
DKconfig26 # the risks and costs of program errors, damage to or loss of data,
/linux-4.1.27/drivers/scsi/mpt2sas/
DKconfig26 # the risks and costs of program errors, damage to or loss of data,
/linux-4.1.27/Documentation/filesystems/
Dntfs.txt373 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
Daffs.txt171 If the damage is already done, the following should fix the RDB
Dhpfs.txt26 text file than to damage binary file). If you want to change that list,
/linux-4.1.27/Documentation/sound/oss/
DREADME.ymfsb19 damage to your computer when used.
DREADME.OSS1248 answering 'y' doesn't cause damage your computer so don't panic.
/linux-4.1.27/drivers/scsi/ufs/
DKconfig29 # program errors, damage to or loss of data, programs or equipment,
/linux-4.1.27/Documentation/scsi/
Ddpti.txt17 * of the possibility of such damage.
/linux-4.1.27/fs/ntfs/
DKconfig63 While we cannot guarantee that it will not damage any data, we have
/linux-4.1.27/Documentation/hwmon/
Dk10temp76 which the processor will throttle itself to avoid damage is available in
Dpc87360101 non-zero, can stop the fan, which may cause irreversible damage to your
/linux-4.1.27/Documentation/usb/
Drio.txt23 are in no way responsible for any damage that may occur, no matter how
Dgadget_multi.txt95 Failing to comply may cause brain damage after wondering for hours why
Dpower-management.txt282 that can't handle it. It is even possible in theory to damage a
/linux-4.1.27/arch/arm/boot/dts/
Dam335x-bone-common.dtsi229 * mode and risk hardware damage if this mode is entered.
/linux-4.1.27/Documentation/laptops/
Dsony-laptop.txt137 laptop, including permanent damage.
/linux-4.1.27/Documentation/sound/alsa/
DREADME.maya44121 It might damage the source and/or the maya44 card.
DCMIPCI.txt36 This might damage your audio equipment. Please disconnect speakers
/linux-4.1.27/Documentation/input/
Diforce-protocol.txt10 I shall not be held responsible for any damage or harm caused if you try to
/linux-4.1.27/Documentation/networking/
DPLIP.txt163 conflicts and the (unlikely) possibility of damage.
Dcxgb.txt104 of data or damage to equipment.
/linux-4.1.27/Documentation/frv/
Dfeatures.txt128 userspace damage - but this is uClinux.
/linux-4.1.27/Documentation/
Dkernel-doc-nano-HOWTO.txt325 * The only drawback to this gizmo is that is can sometimes damage
Dsvga.txt92 `ghost modes'). If you are afraid this could damage your monitor, don't use this
DManagementStyle58 you _will_ be wrong), you can always undo the damage later by
Dkernel-parameters.txt1924 unlikely, in the extreme case this might damage your
/linux-4.1.27/drivers/mtd/nand/
DKconfig274 The only reason not to enable this option is to prevent damage to
/linux-4.1.27/Documentation/devicetree/bindings/thermal/
Dthermal.txt180 device in temperature ranges that may damage the silicon structures and
/linux-4.1.27/arch/s390/kernel/
Dentry.S703 tm __LC_MCCK_CODE,0x80 # system damage?