Searched refs:protection (Results 1 – 25 of 220) sorted by relevance
123456789
| /kernel/linux/linux-5.10/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,
23 Enter the protection key for the floor (0 to 4), protection area
24 (0 or 1). Each docg3 chip (or floor) has 2 protection areas,
26 The protection has information embedded whether it blocks reads,
28 The protection key is a string of 8 bytes (value 0-255).
|
| D | sysfs-block-device | 28 (RW) Hard disk shock protection
50 Documentation/admin-guide/laptops/disk-shock-protection.rst
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,apr.txt | 48 - qcom,protection-domain
51 Definition: Must list the protection domain service name and path
99 The following example represents a QDSP based sound card with protection domain
101 running on protection domain hosted on ADSP/SLPI remote processors while others
117 qcom,protection-domain = "avs/audio", "msm/adsp/audio_pd";
124 qcom,protection-domain = "tms/servreg", "msm/slpi/sensor_pd";
131 qcom,protection-domain = "avs/audio", "msm/adsp/audio_pd";
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/arch/arm/boot/dts/ |
| D | stm32mp15xx-dhcor-som.dtsi | 62 regulator-over-current-protection;
71 regulator-over-current-protection;
80 regulator-over-current-protection;
88 regulator-over-current-protection;
111 regulator-over-current-protection;
|
| D | stm32mp15xx-osd32.dtsi | 90 regulator-over-current-protection;
99 regulator-over-current-protection;
109 regulator-over-current-protection;
117 regulator-over-current-protection;
144 regulator-over-current-protection;
|
| D | stm32mp157c-odyssey-som.dtsi | 119 regulator-over-current-protection;
128 regulator-over-current-protection;
138 regulator-over-current-protection;
146 regulator-over-current-protection;
171 regulator-over-current-protection;
|
| D | stm32mp157a-stinger96.dtsi | 130 regulator-over-current-protection;
139 regulator-over-current-protection;
149 regulator-over-current-protection;
157 regulator-over-current-protection;
182 regulator-over-current-protection;
|
| D | stm32mp157c-ed1.dts | 182 regulator-over-current-protection;
191 regulator-over-current-protection;
201 regulator-over-current-protection;
209 regulator-over-current-protection;
232 regulator-over-current-protection;
|
| D | stm32mp15xx-dhcom-som.dtsi | 182 regulator-over-current-protection;
191 regulator-over-current-protection;
201 regulator-over-current-protection;
209 regulator-over-current-protection;
233 regulator-over-current-protection;
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-5.10/Documentation/ABI/obsolete/ |
| D | sysfs-selinux-checkreqprot | 8 to check the protection requested by userspace for mmap/mprotect
9 calls instead of the actual protection applied by the kernel.
15 actual protection), and Android and Linux distributions have been
|
| /kernel/linux/linux-5.10/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.
|
| /kernel/linux/linux-5.10/Documentation/core-api/ |
| D | protection-keys.rst | 18 when an application changes protection domains. It works by
20 "protection key", giving 16 possible keys.
76 The kernel attempts to make protection keys consistent with the
82 you can expect the same effects with protection keys when doing this::
99 to SEGV_PKERR when violating protection keys versus SEGV_ACCERR when
|
| /kernel/linux/linux-5.10/arch/arm64/ |
| D | Makefile | 71 branch-prot-flags-y += $(call cc-option,-mbranch-protection=none)
79 branch-prot-flags-$(CONFIG_CC_HAS_BRANCH_PROT_PAC_RET_BTI) := -mbranch-protection=pac-ret+leaf+bti
81 branch-prot-flags-$(CONFIG_CC_HAS_BRANCH_PROT_PAC_RET) := -mbranch-protection=pac-ret+leaf
|
| /kernel/linux/linux-5.10/security/selinux/ |
| D | Kconfig | 80 that determines whether SELinux checks the protection requested
81 by the application or the protection that will be applied by the
84 SELinux will default to checking the protection that will be applied
86 default to checking the protection requested by the application.
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/leds/ |
| D | leds-ktd2692.txt | 8 Flash timeout, LVP(low voltage protection).
27 - led-max-microamp : Minimum Threshold for Timer protection
|
| /kernel/linux/linux-5.10/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()
|
| /kernel/linux/linux-5.10/Documentation/security/ |
| D | index.rst | 15 self-protection
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/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.
|
| /kernel/linux/linux-5.10/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.
|
123456789