| /Linux-v5.4/arch/arm/mm/ |
| D | proc-sa110.S | 95 mov r0, r0 @ safety
96 mov r0, r0 @ safety
97 mov r0, r0 @ safety
99 mov r0, r0 @ safety
100 mov r0, r0 @ safety
101 mov r0, r0 @ safety
|
| D | proc-sa1100.S | 111 mov r0, r0 @ safety
|
| /Linux-v5.4/Documentation/devicetree/bindings/power/supply/ |
| D | act8945a-charger.txt | 18 Specifies the charger's PRECONDITION safety timer setting value;
22 Specifies the charger's total safety timer setting value;
|
| D | qcom_smbb.txt | 46 Description: Maximum charge current; May be clamped to safety limits.
60 voltage. May be clamped to safety limits.
106 the JEITA safety guidelines if this flag is set.
|
| /Linux-v5.4/arch/x86/include/asm/ |
| D | suspend_32.h | 31 unsigned long safety; member
|
| D | suspend_64.h | 49 unsigned long safety; member
|
| /Linux-v5.4/arch/powerpc/boot/dts/ |
| D | ac14xx.dts | 45 0x5 0x0 0xe0400000 0x00010000 /* CS5: safety */
125 safety@5,0 {
126 compatible = "ifm,safety";
|
| /Linux-v5.4/net/hsr/ |
| D | Kconfig | 27 relying on this code in a safety critical system!
|
| /Linux-v5.4/drivers/thermal/intel/int340x_thermal/ |
| D | Kconfig | 16 CPU/SOC, for thermal safety reasons.
|
| /Linux-v5.4/Documentation/devicetree/bindings/eeprom/ |
| D | at24.txt | 63 may result in data loss! If not specified, a safety value of
|
| /Linux-v5.4/drivers/media/pci/saa7164/ |
| D | saa7164-cmd.c | 337 int safety = 0; in saa7164_cmd_send() local
445 if (safety++ > 16) { in saa7164_cmd_send()
|
| /Linux-v5.4/Documentation/driver-api/driver-model/ |
| D | bus.rst | 53 type-safety.
|
| D | driver.rst | 50 sacrifice type-safety, so we keep bus-specific structures around.
|
| D | porting.rst | 121 This allows the compiler to verify type-safety of the operations
|
| /Linux-v5.4/arch/arm/boot/dts/ |
| D | arm-realview-eb-mp.dtsi | 74 * up by boot loader(s), probably for safety
|
| D | arm-realview-pb11mp.dts | 107 * up by boot loader(s), probably for safety
|
| /Linux-v5.4/drivers/net/wan/ |
| D | farsync.c | 941 int safety; in fst_issue_cmd() local
947 safety = 0; in fst_issue_cmd()
954 if (++safety > 2000) { in fst_issue_cmd()
961 if (safety > 0) { in fst_issue_cmd()
962 dbg(DBG_CMD, "Mailbox clear after %d jiffies\n", safety); in fst_issue_cmd()
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | ocfs2.txt | 73 will hurt performance, but it's good for data-safety.
|
| /Linux-v5.4/Documentation/i2c/busses/ |
| D | i2c-parport.rst | 94 the i2c-parport module might be a good safety since data line state
|
| /Linux-v5.4/Documentation/admin-guide/laptops/ |
| D | thinkpad-acpi.rst | 579 wake up caused by the firmware will have negated most safety nets...
669 CAP_SYS_ADMIN capability for safety reasons, as it can interact badly
1207 safety reasons. To enable them, the module parameter "fan_control=1"
1266 120 seconds. This functionality is called fan safety watchdog.
1308 To program the safety watchdog, use the "watchdog" command::
1318 part, and the exception is the fan safety watchdog.
1358 Fan safety watchdog timer interval, in seconds. Minimum is
|
| /Linux-v5.4/Documentation/filesystems/ext4/ |
| D | blockgroup.rst | 83 Without the option META\_BG, for safety concerns, all block group
|
| /Linux-v5.4/arch/arm64/boot/dts/rockchip/ |
| D | rk3399-gru-scarlet.dtsi | 37 * rounding up to 1ms for safety.
|
| /Linux-v5.4/Documentation/ |
| D | kprobes.txt | 189 Before optimizing a probe, Kprobes performs the following safety checks:
246 rather, it calls synchronize_rcu() for safety first, because it's
273 .. [4] This optimization-safety checking may be replaced with the
|
| /Linux-v5.4/arch/sh/kernel/cpu/sh5/ |
| D | entry.S | 616 ori r18, 1, r18 ! for safety (do we need this?)
633 synco ! for safety
|
| /Linux-v5.4/Documentation/ioctl/ |
| D | botching-up-ioctls.rst | 119 still too tricky have a timeout or hangcheck safety net as a last-ditch
|
