Searched refs:protection (Results 1 – 25 of 189) sorted by relevance
12345678
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | sysfs-devices-platform-docg3 | 6 Show whether the floor (0 to 4), protection area (0 or 1) is
7 keylocked. Each docg3 chip (or floor) has 2 protection areas,
9 The protection has information embedded whether it blocks reads,
21 Enter the protection key for the floor (0 to 4), protection area
22 (0 or 1). Each docg3 chip (or floor) has 2 protection areas,
24 The protection has information embedded whether it blocks reads,
26 The protection key is a string of 8 bytes (value 0-255).
|
| D | sysfs-block-device | 26 (RW) Hard disk shock protection
48 Documentation/admin-guide/laptops/disk-shock-protection.rst
|
| /Linux-v5.4/Documentation/admin-guide/laptops/ |
| D | toshiba_haps.rst | 26 automatic HDD protection (head unload) on sudden moves or harsh vibrations,
29 file to set the desired protection level or sensor sensibility.
40 PTLV Sets the desired protection level.
41 RSSS Shuts down the HDD protection interface for a few seconds,
48 any "protection" as well as failing during the evaluation of the _STA method
76 provides a way to let userspace query the current protection
77 level, as well as set the desired protection level, the
78 available protection levels are::
86 a reset of the protection interface.
|
| D | disk-shock-protection.rst | 2 Hard disk shock protection
25 a shock protection facility. The idea is to stop all I/O operations on
31 system in order to get disk shock protection working (see
128 protection capabilities. As manufacturers have refused to support open
130 support for shock protection varies considerably between different
133 protection on different systems. Unfortunately, I only know of a
141 active protection system as implemented in IBM/Lenovo Thinkpads.
|
| D | index.rst | 11 disk-shock-protection
|
| /Linux-v5.4/Documentation/devicetree/bindings/mfd/ |
| D | as3711.txt | 30 and one of these to select the over-voltage protection pin
31 - su2-fbprot-lx-sd4 : LX_SD4 is used for over-voltage protection
32 - su2-fbprot-gpio2 : GPIO2 is used for over-voltage protection
33 - su2-fbprot-gpio3 : GPIO3 is used for over-voltage protection
34 - su2-fbprot-gpio4 : GPIO4 is used for over-voltage protection
|
| /Linux-v5.4/Documentation/block/ |
| D | data-integrity.rst | 16 protocols (SBC Data Integrity Field, SCC protection proposal) as well
19 metadata (or protection information in SCSI terminology) includes a
22 for some protection schemes also that the I/O is written to the right
29 DIF and the other integrity extensions is that the protection format
42 the protection information to be transferred to and from their
45 The SCSI Data Integrity Field works by appending 8 bytes of protection
85 The data integrity framework in Linux enables protection information
92 disadvantage. It means that the protection information must be in a
101 protection information to send to a disk. Consequently, the very
102 concept of an end-to-end protection scheme is a layering violation.
[all …]
|
| /Linux-v5.4/Documentation/devicetree/bindings/usb/ |
| D | pxa-usb.txt | 18 - "marvell,no-oc-protection" - disable over-current protection.
19 - "marvell,oc-mode-perport" - enable per-port over-current protection.
|
| /Linux-v5.4/arch/arm/boot/dts/ |
| D | stm32mp157c-ed1.dts | 150 regulator-over-current-protection;
159 regulator-over-current-protection;
169 regulator-over-current-protection;
177 regulator-over-current-protection;
200 regulator-over-current-protection;
228 regulator-over-current-protection;
|
| D | stm32mp157a-avenger96.dts | 158 regulator-over-current-protection;
167 regulator-over-current-protection;
177 regulator-over-current-protection;
185 regulator-over-current-protection;
210 regulator-over-current-protection;
242 regulator-over-current-protection;
|
| D | stm32mp157a-dk1.dts | 233 regulator-over-current-protection;
242 regulator-over-current-protection;
252 regulator-over-current-protection;
260 regulator-over-current-protection;
285 regulator-over-current-protection;
314 regulator-over-current-protection;
|
| /Linux-v5.4/Documentation/core-api/ |
| D | protection-keys.rst | 17 when an application changes protection domains. It works by
19 "protection key", giving 16 possible keys.
75 The kernel attempts to make protection keys consistent with the
81 you can expect the same effects with protection keys when doing this::
98 to SEGV_PKERR when violating protection keys versus SEGV_ACCERR when
|
| /Linux-v5.4/drivers/gpu/drm/omapdrm/displays/ |
| D | Kconfig | 11 tristate "TPD12S015 HDMI ESD protection and level shifter"
13 Driver for TPD12S015, which offers HDMI ESD protection and level
|
| /Linux-v5.4/security/selinux/ |
| D | Kconfig | 76 that determines whether SELinux checks the protection requested
77 by the application or the protection that will be applied by the
80 SELinux will default to checking the protection that will be applied
82 default to checking the protection requested by the application.
|
| /Linux-v5.4/Documentation/devicetree/bindings/regulator/ |
| D | st,stpmic1-regulator.txt | 26 - regulator-over-current-protection:
62 regulator-over-current-protection;
|
| /Linux-v5.4/Documentation/devicetree/bindings/leds/ |
| D | leds-ktd2692.txt | 8 Flash timeout, LVP(low voltage protection).
27 - led-max-microamp : Minimum Threshold for Timer protection
|
| /Linux-v5.4/drivers/irqchip/ |
| D | irq-omap-intc.c | 59 u32 protection; member
88 intc_context.protection = in omap_intc_save_context()
108 intc_writel(INTC_PROTECTION, intc_context.protection); in omap_intc_restore_context()
|
| /Linux-v5.4/Documentation/security/ |
| D | index.rst | 15 self-protection
|
| /Linux-v5.4/Documentation/devicetree/bindings/dma/ |
| D | snps-dma.txt | 28 - snps,dma-protection-control: AHB HPROT[3:1] protection setting.
|
| /Linux-v5.4/drivers/video/fbdev/omap2/omapfb/displays/ |
| D | Kconfig | 17 tristate "TPD12S015 HDMI ESD protection and level shifter"
19 Driver for TPD12S015, which offers HDMI ESD protection and level
|
| /Linux-v5.4/Documentation/x86/ |
| D | intel_txt.rst | 14 - Data protection in case of improper shutdown
78 protection, memory configuration/alias checks and locks, crash
79 protection, or policy support.
84 protection is provided to all launched components, a large number
86 protection is provided for any data in the event of an improper
142 in order to remove this blanket protection and use VT-d's
143 page-level protection.
|
| /Linux-v5.4/fs/verity/ |
| D | Kconfig | 4 bool "FS Verity (read-only file-based authenticity protection)"
28 protection against malicious disks vs. an ahead-of-time hash.
|
| /Linux-v5.4/Documentation/devicetree/bindings/power/supply/ |
| D | max8925_battery.txt | 8 - no-temp-support: whether support temperature protection detect
|
| /Linux-v5.4/Documentation/admin-guide/hw-vuln/ |
| D | mds.rst | 134 the CPUID to the guest. If the host has updated microcode the protection
171 The protection for host to guest transition depends on the L1TF
191 The resulting MDS protection matrix for the host to guest transition:
226 either disabling SMT is not required for full protection.
235 disable SMT for full protection. These are most of the affected CPUs; the
290 The protection depends on the state of the L1TF mitigations.
|
| /Linux-v5.4/Documentation/features/debug/stackprotector/ |
| D | arch-support.txt | 4 # description: arch supports compiler driven stack overflow protection
|
12345678
