Searched refs:protection (Results 1 – 25 of 166) sorted by relevance
1234567
| /Linux-v4.19/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/laptops/disk-shock-protection.txt
|
| D | sysfs-driver-toshiba_haps | 5 Description: This file controls the built-in accelerometer protection level,
|
| /Linux-v4.19/Documentation/laptops/ |
| D | toshiba_haps.txt | 25 automatic HDD protection (head unload) on sudden moves or harsh vibrations,
28 file to set the desired protection level or sensor sensibility.
37 PTLV - Sets the desired protection level.
38 RSSS - Shuts down the HDD protection interface for a few seconds,
44 any "protection" as well as failing during the evaluation of the _STA method
70 provides a way to let userspace query the current protection
71 level, as well as set the desired protection level, the
72 available protection levels are:
76 a reset of the protection interface.
|
| D | 00-INDEX | 5 disk-shock-protection.txt
6 - information on hard disk shock protection.
|
| D | disk-shock-protection.txt | 1 Hard disk shock protection
24 a shock protection facility. The idea is to stop all I/O operations on
30 system in order to get disk shock protection working (see
127 protection capabilities. As manufacturers have refused to support open
129 support for shock protection varies considerably between different
132 protection on different systems. Unfortunately, I only know of a
139 active protection system as implemented in IBM/Lenovo Thinkpads.
|
| /Linux-v4.19/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-v4.19/Documentation/block/ |
| D | data-integrity.txt | 12 protocols (SBC Data Integrity Field, SCC protection proposal) as well
15 metadata (or protection information in SCSI terminology) includes a
18 for some protection schemes also that the I/O is written to the right
25 DIF and the other integrity extensions is that the protection format
38 the protection information to be transferred to and from their
41 The SCSI Data Integrity Field works by appending 8 bytes of protection
81 The data integrity framework in Linux enables protection information
88 disadvantage. It means that the protection information must be in a
97 protection information to send to a disk. Consequently, the very
98 concept of an end-to-end protection scheme is a layering violation.
[all …]
|
| /Linux-v4.19/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-v4.19/Documentation/x86/ |
| D | protection-keys.txt | 11 when an application changes protection domains. It works by
13 "protection key", giving 16 possible keys.
66 The kernel attempts to make protection keys consistent with the
72 you can expect the same effects with protection keys when doing this:
89 to SEGV_PKERR when violating protection keys versus SEGV_ACCERR when
|
| /Linux-v4.19/security/selinux/ |
| D | Kconfig | 90 that determines whether SELinux checks the protection requested
91 by the application or the protection that will be applied by the
94 SELinux will default to checking the protection that will be applied
96 default to checking the protection requested by the application.
|
| /Linux-v4.19/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-v4.19/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-v4.19/Documentation/security/ |
| D | index.rst | 14 self-protection
|
| /Linux-v4.19/drivers/video/fbdev/omap2/omapfb/displays/ |
| D | Kconfig | 16 tristate "TPD12S015 HDMI ESD protection and level shifter"
18 Driver for TPD12S015, which offers HDMI ESD protection and level
|
| /Linux-v4.19/drivers/gpu/drm/omapdrm/displays/ |
| D | Kconfig | 15 tristate "TPD12S015 HDMI ESD protection and level shifter"
17 Driver for TPD12S015, which offers HDMI ESD protection and level
|
| /Linux-v4.19/Documentation/ |
| D | intel_txt.txt | 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.
|
| D | digsig.txt | 20 Currently digital signatures are used by the IMA/EVM integrity protection subsystem.
51 protection.
|
| /Linux-v4.19/Documentation/devicetree/bindings/power/supply/ |
| D | max8925_battery.txt | 8 - no-temp-support: whether support temperature protection detect
|
| /Linux-v4.19/Documentation/features/debug/stackprotector/ |
| D | arch-support.txt | 4 # description: arch supports compiler driven stack overflow protection
|
| /Linux-v4.19/Documentation/devicetree/bindings/display/ti/ |
| D | ti,tpd12s015.txt | 1 TPD12S015 HDMI level shifter and ESD protection chip
|
| /Linux-v4.19/Documentation/admin-guide/ |
| D | l1tf.rst | 58 While Meltdown breaks the user space to kernel space protection, L1TF
60 works across all protection domains. It allows an attack of SGX and also
62 extended page table (EPT) protection mechanism.
111 deployment scenario. The mitigations, their protection scope and impact
132 'Mitigation: PTE Inversion' The host protection is active
155 The resulting grade of protection is discussed in the following sections.
198 maximum protection. It has a higher overhead than the conditional
497 L1D flushing on VMENTER is the minimal protection requirement, but it
522 The above three mitigation methods combined can provide protection to a
524 carefully analyzed. For full protection the following methods are
[all …]
|
| D | bug-hunting.rst | 294 substantial support incorporated into ``klogd`` for processing protection
298 When a protection fault occurs the ``klogd`` daemon automatically
302 protection fault message can be simply cut out of the message files
321 to debug a protection fault which occurs in a loadable kernel module.
324 generated the protection fault. There may be additional symbolic
338 seamless support for debugging protection faults which occur with
341 The following is an example of a protection fault in a loadable module
|
| /Linux-v4.19/Documentation/mtd/ |
| D | intel-spi.txt | 7 it is typically protected by different hardware protection mechanisms to
14 flash, if certain protection bits are not set and locked. If it finds
|
| /Linux-v4.19/Documentation/devicetree/bindings/mtd/ |
| D | mtd-physmap.txt | 29 - use-advanced-sector-protection: boolean to enable support for the
30 advanced sector protection (Spansion: PPB - Persistent Protection
|
1234567
