Searched full:safety (Results 1 – 25 of 56) sorted by relevance
123
| /Documentation/translations/zh_CN/rust/ |
| D | coding-guidelines.rst | 53 此外，就像文档一样，注释在句子的开头要大写，并以句号结束（即使是单句）。这包括 ``// SAFETY:``,
80 一种特殊的注释是 ``// SAFETY:`` 注释。这些注释必须出现在每个 ``unsafe`` 块之前，它们
85 // SAFETY: `p` is valid by the safety requirements.
88 ``// SAFETY:`` 注释不能与代码文档中的 ``# Safety`` 部分相混淆。 ``# Safety`` 部
90 ``// SAFETY:`` 注释显示了为什么一个（函数）调用者或（特性）实现者实际上尊重了
91 ``# Safety`` 部分或语言参考中的前提条件。
111 /// # Safety
127 // SAFETY: The safety contract must be upheld by the caller.
137 - 不安全的函数必须在 ``# Safety`` 部分记录其安全前提条件。
150 - 任何 ``unsafe`` 的代码块都必须在前面加上一个 ``// SAFETY:`` 的注释，描述里面
|
| /Documentation/rust/ |
| D | coding-guidelines.rst | 58 includes ``// SAFETY:``, ``// TODO:`` and other "tagged" comments, e.g.:
88 One special kind of comments are the ``// SAFETY:`` comments. These must appear
94 // SAFETY: `p` is valid by the safety requirements.
97 ``// SAFETY:`` comments are not to be confused with the ``# Safety`` sections
98 in code documentation. ``# Safety`` sections specify the contract that callers
99 (for functions) or implementors (for traits) need to abide by. ``// SAFETY:``
101 respects the preconditions stated in a ``# Safety`` section or the language
124 /// # Safety
140 // SAFETY: The safety contract must be upheld by the caller.
151 - Unsafe functions must document their safety preconditions under
[all …]
|
| /Documentation/devicetree/bindings/misc/ |
| D | ti,j721e-esm.yaml | 15 that allows handling of safety events somewhat similar to what interrupt
16 controller would do. The safety signals have their separate paths within
|
| /Documentation/devicetree/bindings/regulator/ |
| 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.
|
| D | richtek,rtq2208.yaml | 13 RTQ2208 is a highly integrated power converter that offers functional safety dual
|
| /Documentation/devicetree/bindings/power/supply/ |
| 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;
|
| D | qcom,pm8941-charger.yaml | 47 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
|
| /Documentation/power/regulator/ |
| D | design.rst | 8 Safety chapter
|
| /Documentation/devicetree/bindings/pci/ |
| D | snps,dw-pcie-ep.yaml | 143 correctable error is detected by the automotive/safety
147 Indicates that the internal safety mechanism has detected an
|
| D | snps,dw-pcie.yaml | 152 correctable error is detected by the automotive/safety
156 Indicates that the internal safety mechanism has detected an
|
| /Documentation/devicetree/bindings/watchdog/ |
| D | ti,rti-wdt.yaml | 17 generated can be routed to either interrupt a safety controller or
|
| /Documentation/misc-devices/ |
| D | tps6594-pfsm.rst | 61 Only the power resources assigned to the MCU Safety Island are on.
|
| /Documentation/admin-guide/ |
| D | index.rst | 61 Linux kernel for safety critical applications. Documents supporting
|
| /Documentation/devicetree/bindings/mfd/ |
| D | rohm,bd9576-pmic.yaml | 15 The IC provides 6 power outputs with configurable sequencing and safety
|
| /Documentation/devicetree/bindings/remoteproc/ |
| D | xlnx,zynqmp-r5fss.yaml | 27 The RPU MPCore can operate in split mode (Dual-processor performance), Safety
|
| 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
|
| /Documentation/driver-api/driver-model/ |
| D | bus.rst | 53 type-safety.
|
| /Documentation/filesystems/ |
| D | ocfs2.rst | 83 will hurt performance, but it's good for data-safety.
|
| /Documentation/admin-guide/hw-vuln/ |
| D | srso.rst | 151 To ensure the safety of this mitigation, the kernel must ensure that the
|
| /Documentation/devicetree/bindings/eeprom/ |
| D | at24.yaml | 144 may result in data loss! If not specified, a safety value of
|
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | nvidia,tegra186-mc.yaml | 22 automotive safety applications (single bit error correction and double bit
|
| /Documentation/trace/ |
| D | kprobes.rst | 186 Safety Check
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
|
| /Documentation/filesystems/ext4/ |
| D | blockgroup.rst | 83 Without the option META_BG, for safety concerns, all block group
|
| /Documentation/bpf/ |
| D | classic_vs_extended.rst | 230 Safety of eBPF can come from the verifier.rst. In such use cases as
234 is deterministic and the kernel can easily prove that. The safety of the program
|
| /Documentation/driver-api/ |
| D | interconnect.rst | 118 any arbitrary path. Note that for safety reasons, this feature is disabled by
|
123