/linux/arch/arm/mm/ |
A 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
|
A D | proc-sa1100.S | 111 mov r0, r0 @ safety
|
/linux/Documentation/devicetree/bindings/regulator/ |
A D | richtek,rtmv20-regulator.yaml | 79 description: Eye safety function pulse width limit in microsecond. 85 description: Eye safety function load current limit in microamp. 117 description: Eye safety function enable control.
|
/linux/Documentation/devicetree/bindings/power/supply/ |
A D | active-semi,act8945a-charger.yaml | 40 Specifies the charger's PRECONDITION safety timer setting value in minutes. 48 Specifies the charger's total safety timer setting value in hours;
|
A D | qcom,pm8941-charger.yaml | 45 description: Maximum charge current in uA; May be clamped to safety limits; Defaults to 1A 62 May be clamped to safety limits. 115 be done externally to fully comply with the JEITA safety guidelines if this flag
|
/linux/arch/x86/include/asm/ |
A D | suspend_32.h | 29 unsigned long safety; member
|
A D | suspend_64.h | 49 unsigned long safety; member
|
/linux/arch/powerpc/boot/dts/ |
A D | ac14xx.dts | 45 0x5 0x0 0xe0400000 0x00010000 /* CS5: safety */ 125 safety@5,0 { 126 compatible = "ifm,safety";
|
/linux/Documentation/devicetree/bindings/watchdog/ |
A D | ti,rti-wdt.yaml | 17 generated can be routed to either interrupt a safety controller or
|
/linux/drivers/thermal/intel/int340x_thermal/ |
A D | Kconfig | 17 CPU/SOC, for thermal safety reasons.
|
/linux/net/hsr/ |
A D | Kconfig | 38 relying on this code in a safety critical system!
|
/linux/drivers/media/pci/saa7164/ |
A D | saa7164-cmd.c | 337 int safety = 0; in saa7164_cmd_send() local 445 if (safety++ > 16) { in saa7164_cmd_send()
|
/linux/Documentation/devicetree/bindings/memory-controllers/ |
A D | nvidia,tegra186-mc.yaml | 22 automotive safety applications (single bit error correction and double bit
|
/linux/Documentation/devicetree/bindings/mfd/ |
A D | rohm,bd9576-pmic.yaml | 15 The IC provides 6 power outputs with configurable sequencing and safety
|
/linux/Documentation/devicetree/bindings/remoteproc/ |
A D | ti,k3-r5f-rproc.yaml | 15 either in a LockStep mode providing safety/fault tolerance features or in a 20 AM64x SoCs do not support LockStep mode, but rather a new non-safety mode
|
/linux/lib/ |
A D | Kconfig.kfence | 7 bool "KFENCE: low-overhead sampling-based memory safety error detector"
|
/linux/Documentation/devicetree/bindings/eeprom/ |
A D | at24.yaml | 135 may result in data loss! If not specified, a safety value of
|
/linux/arch/arm/boot/dts/ |
A D | arm-realview-eb-mp.dtsi | 74 * up by boot loader(s), probably for safety
|
/linux/Documentation/driver-api/driver-model/ |
A D | bus.rst | 53 type-safety.
|
/linux/drivers/net/wan/ |
A D | farsync.c | 911 int safety; in fst_issue_cmd() local 917 safety = 0; in fst_issue_cmd() 924 if (++safety > 2000) { in fst_issue_cmd() 931 if (safety > 0) in fst_issue_cmd() 932 dbg(DBG_CMD, "Mailbox clear after %d jiffies\n", safety); in fst_issue_cmd()
|
/linux/Documentation/filesystems/ |
A D | ocfs2.rst | 83 will hurt performance, but it's good for data-safety.
|
/linux/Documentation/i2c/busses/ |
A D | i2c-parport.rst | 94 the i2c-parport module might be a good safety since data line state
|
/linux/Documentation/admin-guide/laptops/ |
A D | thinkpad-acpi.rst | 582 wake up caused by the firmware will have negated most safety nets... 672 CAP_SYS_ADMIN capability for safety reasons, as it can interact badly 1210 safety reasons. To enable them, the module parameter "fan_control=1" 1269 120 seconds. This functionality is called fan safety watchdog. 1311 To program the safety watchdog, use the "watchdog" command:: 1321 part, and the exception is the fan safety watchdog. 1361 Fan safety watchdog timer interval, in seconds. Minimum is
|
/linux/Documentation/filesystems/ext4/ |
A D | blockgroup.rst | 83 Without the option META\_BG, for safety concerns, all block group
|
/linux/Documentation/trace/ |
A 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
|