| /Linux-v4.19/arch/arm/mm/ |
| D | proc-sa110.S | 98 mov r0, r0 @ safety
99 mov r0, r0 @ safety
100 mov r0, r0 @ safety
102 mov r0, r0 @ safety
103 mov r0, r0 @ safety
104 mov r0, r0 @ safety
|
| D | proc-sa1100.S | 114 mov r0, r0 @ safety
|
| /Linux-v4.19/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-v4.19/arch/x86/include/asm/ |
| D | suspend_32.h | 31 unsigned long safety; member
|
| D | suspend_64.h | 49 unsigned long safety; member
|
| /Linux-v4.19/arch/powerpc/boot/dts/ |
| D | ac14xx.dts | 49 0x5 0x0 0xe0400000 0x00010000 /* CS5: safety */
129 safety@5,0 {
130 compatible = "ifm,safety";
|
| /Linux-v4.19/net/hsr/ |
| D | Kconfig | 26 relying on this code in a safety critical system!
|
| /Linux-v4.19/drivers/thermal/int340x_thermal/ |
| D | Kconfig | 15 CPU/SOC, for thermal safety reasons.
|
| /Linux-v4.19/Documentation/devicetree/bindings/eeprom/ |
| D | at24.txt | 61 may result in data loss! If not specified, a safety value of
|
| /Linux-v4.19/drivers/media/pci/saa7164/ |
| D | saa7164-cmd.c | 347 int safety = 0; in saa7164_cmd_send() local
455 if (safety++ > 16) { in saa7164_cmd_send()
|
| /Linux-v4.19/arch/arm/boot/dts/ |
| D | arm-realview-eb-mp.dtsi | 74 * up by boot loader(s), probably for safety
|
| D | arm-realview-pb11mp.dts | 105 * up by boot loader(s), probably for safety
|
| /Linux-v4.19/Documentation/driver-model/ |
| D | bus.txt | 52 type-safety.
|
| D | driver.txt | 49 sacrifice type-safety, so we keep bus-specific structures around.
|
| D | porting.txt | 119 This allows the compiler to verify type-safety of the operations
|
| /Linux-v4.19/drivers/net/wan/ |
| D | farsync.c | 945 int safety; in fst_issue_cmd() local
951 safety = 0; in fst_issue_cmd()
958 if (++safety > 2000) { in fst_issue_cmd()
965 if (safety > 0) { in fst_issue_cmd()
966 dbg(DBG_CMD, "Mailbox clear after %d jiffies\n", safety); in fst_issue_cmd()
|
| /Linux-v4.19/Documentation/filesystems/ |
| D | ocfs2.txt | 73 will hurt performance, but it's good for data-safety.
|
| /Linux-v4.19/Documentation/i2c/busses/ |
| D | i2c-parport | 86 the i2c-parport module might be a good safety since data line state
|
| /Linux-v4.19/Documentation/filesystems/ext4/ondisk/ |
| D | blockgroup.rst | 83 Without the option META\_BG, for safety concerns, all block group
|
| /Linux-v4.19/Documentation/laptops/ |
| D | thinkpad-acpi.txt | 551 wake up caused by the firmware will have negated most safety nets...
634 CAP_SYS_ADMIN capability for safety reasons, as it can interact badly
1145 safety reasons. To enable them, the module parameter "fan_control=1"
1203 120 seconds. This functionality is called fan safety watchdog.
1244 To program the safety watchdog, use the "watchdog" command.
1253 part, and the exception is the fan safety watchdog.
1293 Fan safety watchdog timer interval, in seconds. Minimum is
|
| /Linux-v4.19/Documentation/ |
| D | kprobes.txt | 189 Before optimizing a probe, Kprobes performs the following safety checks:
246 rather, it calls synchronize_sched() for safety first, because it's
273 .. [4] This optimization-safety checking may be replaced with the
|
| /Linux-v4.19/arch/sh/kernel/cpu/sh5/ |
| D | entry.S | 619 ori r18, 1, r18 ! for safety (do we need this?)
636 synco ! for safety
|
| /Linux-v4.19/Documentation/ioctl/ |
| D | botching-up-ioctls.txt | 118 still too tricky have a timeout or hangcheck safety net as a last-ditch
|
| /Linux-v4.19/Documentation/networking/ |
| D | filter.txt | 837 is deterministic and the kernel can easily prove that. The safety of the program
1016 The safety of the eBPF program is determined in two steps.
1097 from safety point of view. The verifier will guarantee that the function is
1109 In order to determine the safety of an eBPF program, the verifier must track
|
