| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/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.
|
| /kernel/linux/linux-5.10/arch/x86/include/asm/ |
| D | suspend_32.h | 30 unsigned long safety; member
|
| D | suspend_64.h | 52 unsigned long safety; member
|
| /kernel/linux/linux-5.10/arch/powerpc/boot/dts/ |
| D | ac14xx.dts | 45 0x5 0x0 0xe0400000 0x00010000 /* CS5: safety */
125 safety@5,0 {
126 compatible = "ifm,safety";
|
| /kernel/linux/linux-5.10/drivers/thermal/intel/int340x_thermal/ |
| D | Kconfig | 16 CPU/SOC, for thermal safety reasons.
|
| /kernel/linux/linux-5.10/net/hsr/ |
| D | Kconfig | 38 relying on this code in a safety critical system!
|
| /kernel/linux/linux-5.10/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()
|
| /kernel/linux/linux-5.10/Documentation/driver-api/driver-model/ |
| D | bus.rst | 53 type-safety.
|
| D | driver.rst | 49 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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/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()
|
| /kernel/linux/linux-5.10/Documentation/filesystems/ |
| D | ocfs2.rst | 83 will hurt performance, but it's good for data-safety.
|
| /kernel/linux/linux-5.10/Documentation/i2c/busses/ |
| D | i2c-parport.rst | 94 the i2c-parport module might be a good safety since data line state
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/laptops/ |
| D | thinkpad-acpi.rst | 580 wake up caused by the firmware will have negated most safety nets...
670 CAP_SYS_ADMIN capability for safety reasons, as it can interact badly
1208 safety reasons. To enable them, the module parameter "fan_control=1"
1267 120 seconds. This functionality is called fan safety watchdog.
1309 To program the safety watchdog, use the "watchdog" command::
1319 part, and the exception is the fan safety watchdog.
1359 Fan safety watchdog timer interval, in seconds. Minimum is
|
| /kernel/linux/linux-5.10/Documentation/filesystems/ext4/ |
| D | blockgroup.rst | 83 Without the option META\_BG, for safety concerns, all block group
|
| /kernel/linux/linux-5.10/arch/arm64/boot/dts/rockchip/ |
| D | rk3399-gru-scarlet.dtsi | 37 * rounding up to 1ms for safety.
|
| /kernel/linux/linux-5.10/Documentation/trace/ |
| D | kprobes.rst | 190 Before optimizing a probe, Kprobes performs the following safety checks:
247 rather, it calls synchronize_rcu() for safety first, because it's
274 .. [4] This optimization-safety checking may be replaced with the
|
| /kernel/linux/linux-5.10/Documentation/process/ |
| D | botching-up-ioctls.rst | 119 still too tricky have a timeout or hangcheck safety net as a last-ditch
|
| /kernel/linux/linux-5.10/Documentation/networking/ |
| D | filter.rst | 875 is deterministic and the kernel can easily prove that. The safety of the program
1061 The safety of the eBPF program is determined in two steps.
1155 from safety point of view. The verifier will guarantee that the function is
1167 In order to determine the safety of an eBPF program, the verifier must track
|
| /kernel/linux/linux-5.10/Documentation/locking/ |
| D | ww-mutex-design.rst | 88 interface safety:
|