Home
last modified time | relevance | path

Searched refs:safety (Results 1 – 25 of 62) sorted by relevance

123

/linux-6.1.9/arch/arm/mm/
Dproc-sa110.S95 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
Dproc-sa1100.S111 mov r0, r0 @ safety
/linux-6.1.9/Documentation/devicetree/bindings/regulator/
Drichtek,rtmv20-regulator.yaml79 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-6.1.9/Documentation/devicetree/bindings/power/supply/
Dactive-semi,act8945a-charger.yaml40 Specifies the charger's PRECONDITION safety timer setting value in minutes.
48 Specifies the charger's total safety timer setting value in hours;
Dqcom,pm8941-charger.yaml47 description: Maximum charge current in uA; May be clamped to safety limits; Defaults to 1A
64 May be clamped to safety limits.
117 be done externally to fully comply with the JEITA safety guidelines if this flag
/linux-6.1.9/arch/x86/include/asm/
Dsuspend_32.h28 unsigned long safety; member
Dsuspend_64.h52 unsigned long safety; member
/linux-6.1.9/arch/powerpc/boot/dts/
Dac14xx.dts45 0x5 0x0 0xe0400000 0x00010000 /* CS5: safety */
125 safety@5,0 {
126 compatible = "ifm,safety";
/linux-6.1.9/Documentation/devicetree/bindings/watchdog/
Dti,rti-wdt.yaml17 generated can be routed to either interrupt a safety controller or
/linux-6.1.9/Documentation/rust/
Dcoding-guidelines.rst94 // SAFETY: `p` is valid by the safety requirements.
140 // SAFETY: The safety contract must be upheld by the caller.
151 - Unsafe functions must document their safety preconditions under
/linux-6.1.9/drivers/thermal/intel/int340x_thermal/
DKconfig17 CPU/SOC, for thermal safety reasons.
/linux-6.1.9/net/hsr/
DKconfig38 relying on this code in a safety critical system!
/linux-6.1.9/lib/
DKconfig.kasan35 bool "KASAN: dynamic memory safety error detector"
43 Enables KASAN (Kernel Address Sanitizer) - a dynamic memory safety
DKconfig.kfence7 bool "KFENCE: low-overhead sampling-based memory safety error detector"
/linux-6.1.9/drivers/media/pci/saa7164/
Dsaa7164-cmd.c336 int safety = 0; in saa7164_cmd_send() local
444 if (safety++ > 16) { in saa7164_cmd_send()
/linux-6.1.9/Documentation/devicetree/bindings/mfd/
Drohm,bd9576-pmic.yaml15 The IC provides 6 power outputs with configurable sequencing and safety
/linux-6.1.9/Documentation/devicetree/bindings/remoteproc/
Dti,k3-r5f-rproc.yaml15 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-6.1.9/Documentation/devicetree/bindings/eeprom/
Dat24.yaml138 may result in data loss! If not specified, a safety value of
/linux-6.1.9/Documentation/driver-api/driver-model/
Dbus.rst53 type-safety.
/linux-6.1.9/arch/arm/boot/dts/
Darm-realview-eb-mp.dtsi74 * up by boot loader(s), probably for safety
/linux-6.1.9/drivers/net/wan/
Dfarsync.c911 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-6.1.9/Documentation/devicetree/bindings/memory-controllers/
Dnvidia,tegra186-mc.yaml22 automotive safety applications (single bit error correction and double bit
/linux-6.1.9/Documentation/filesystems/
Docfs2.rst83 will hurt performance, but it's good for data-safety.
/linux-6.1.9/Documentation/bpf/
Dverifier.rst6 The safety of the eBPF program is determined in two steps.
100 from safety point of view. The verifier will guarantee that the function is
113 In order to determine the safety of an eBPF program, the verifier must track
/linux-6.1.9/Documentation/i2c/busses/
Di2c-parport.rst94 the i2c-parport module might be a good safety since data line state

123