Searched refs:protection (Results 1 – 25 of 294) sorted by relevance
12345678910>>...12
| /linux-6.6.21/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).
|
| /linux-6.6.21/drivers/mtd/spi-nor/ |
| D | Kconfig | 28 prompt "Software write protection at boot"
34 This option disables the software write protection on any SPI
37 Depending on the flash chip this either clears the block protection
40 Don't use this if you intent to use the software write protection
44 bool "Disable SWP on flashes w/ volatile protection bits"
46 Some SPI flashes have volatile block protection bits, ie. after a
50 This option disables the software write protection for these kind
52 which have non-volatile write protection bits.
54 If the software write protection will be disabled depending on
55 the flash either the block protection bits are cleared or a
[all …]
|
| /linux-6.6.21/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.
|
| /linux-6.6.21/tools/testing/selftests/cgroup/ |
| D | memcg_protection.m | 5 % This script simulates reclaim protection behavior on a single level of memcg
6 % hierarchy to illustrate how overcommitted protection spreads among siblings
15 % E number parent effective protection
16 % n vector nominal protection of siblings set at the given level (memory.low)
54 % recursive protection
65 % commit 1bc63fb1272b ("mm, memcg: make scan aggression always exclude protection")
|
| /linux-6.6.21/Documentation/devicetree/bindings/regulator/ |
| D | regulator.yaml | 117 regulator-over-current-protection:
118 description: Enable over current protection.
121 regulator-oc-protection-microamp:
122 description: Set over current protection limit. This is a limit where
124 protection and value '1' indicates that protection should be enabled but
140 regulator-ov-protection-microvolt:
141 description: Set over voltage protection limit. This is a limit where
143 protection and value '1' indicates that protection should be enabled but
162 regulator-uv-protection-microvolt:
163 description: Set over under voltage protection limit. This is a limit where
[all …]
|
| /linux-6.6.21/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
|
| D | dlg,da9063.yaml | 15 Using regulator-{uv,ov}-{warn,error,protection}-microvolt requires special
132 regulator-uv-protection-microvolt = <0>;
133 regulator-ov-protection-microvolt = <0>;
139 regulator-uv-protection-microvolt = <1>;
140 regulator-ov-protection-microvolt = <1>;
|
| D | st,stpmic1.yaml | 127 regulator-over-current-protection: true
149 regulator-over-current-protection: true
188 regulator-over-current-protection: true
214 regulator-over-current-protection: true
239 regulator-over-current-protection: true
255 regulator-over-current-protection: true
334 regulator-over-current-protection;
|
| /linux-6.6.21/arch/arm/boot/dts/st/ |
| D | stm32mp15xx-osd32.dtsi | 85 regulator-over-current-protection;
94 regulator-over-current-protection;
104 regulator-over-current-protection;
112 regulator-over-current-protection;
139 regulator-over-current-protection;
|
| D | stm32mp157c-odyssey-som.dtsi | 109 regulator-over-current-protection;
118 regulator-over-current-protection;
128 regulator-over-current-protection;
136 regulator-over-current-protection;
161 regulator-over-current-protection;
|
| D | stm32mp15xx-dhcor-som.dtsi | 108 regulator-over-current-protection;
117 regulator-over-current-protection;
126 regulator-over-current-protection;
134 regulator-over-current-protection;
157 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 | 195 regulator-over-current-protection;
204 regulator-over-current-protection;
214 regulator-over-current-protection;
222 regulator-over-current-protection;
245 regulator-over-current-protection;
|
| D | stm32mp157c-emstamp-argon.dtsi | 231 regulator-over-current-protection;
240 regulator-over-current-protection;
250 regulator-over-current-protection;
258 regulator-over-current-protection;
283 regulator-over-current-protection;
|
| /linux-6.6.21/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-6.6.21/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-6.6.21/Documentation/core-api/ |
| D | protection-keys.rst | 9 application changes protection domains.
17 a "protection key", giving 16 possible keys.
74 The kernel attempts to make protection keys consistent with the
80 you can expect the same effects with protection keys when doing this::
97 to SEGV_PKERR when violating protection keys versus SEGV_ACCERR when
|
| /linux-6.6.21/Documentation/ABI/removed/ |
| D | sysfs-selinux-checkreqprot | 11 to check the protection requested by userspace for mmap/mprotect
12 calls instead of the actual protection applied by the kernel.
18 actual protection), and Android and Linux distributions have been
|
| /linux-6.6.21/tools/testing/selftests/arm64/bti/ |
| D | Makefile | 11 CFLAGS_NOBTI = -mbranch-protection=none -DBTI=0
12 CFLAGS_BTI = -mbranch-protection=standard -DBTI=1
|
| /linux-6.6.21/Documentation/devicetree/bindings/leds/backlight/ |
| D | qcom-wled.yaml | 91 V; Over-voltage protection limit.
99 Over-voltage protection limit. This property is for WLED4 only.
122 protection is used. This property is supported only
135 - description: over voltage protection interrupt.
|
| /linux-6.6.21/arch/arm64/ |
| D | Makefile | 67 KBUILD_CFLAGS += -mbranch-protection=pac-ret+bti
70 KBUILD_CFLAGS += -mbranch-protection=pac-ret
75 KBUILD_CFLAGS += $(call cc-option,-mbranch-protection=none)
|
| /linux-6.6.21/Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,apr.yaml | 161 qcom,protection-domain = "avs/audio", "msm/adsp/audio_pd";
167 qcom,protection-domain = "avs/audio", "msm/adsp/audio_pd";
199 qcom,protection-domain = "avs/audio", "msm/adsp/audio_pd";
|
| /linux-6.6.21/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-6.6.21/Documentation/devicetree/bindings/leds/ |
| D | kinetic,ktd2692.yaml | 18 Flash timeout, LVP(low voltage protection).
50 description: Minimum Threshold for Timer protection
|
12345678910>>...12