| /linux/drivers/net/wireless/intel/iwlwifi/mld/ |
| H A D | session-protect.h | 15 * DOC: session protection
17 * Session protection is an API from the firmware that allows the driver to
21 * needed a session protection.
29 * struct iwl_mld_session_protect - session protection parameters
30 * @end_jiffies: expected end_jiffies of current session protection.
33 * @session_requested: A session protection command was sent and wasn't yet
54 * iwl_mld_schedule_session_protection - schedule a session protection
56 * @vif: the virtual interface for which the protection issued
57 * @duration: the requested duration of the protection
58 * @min_duration: the minimum duration of the protection
[all …]
|
| /linux/Documentation/ABI/testing/ |
| H A 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/tools/testing/selftests/kvm/s390/ |
| H A D | tprot.c | 3 * Test TEST PROTECTION emulation.
79 * We perform each test in the array by executing TEST PROTECTION on
85 * TEST PROTECTION instruction.
91 * See Enhanced Suppression-on-Protection Facilities in the
97 * protection for it
105 /* mismatched keys, but no fetch protection -> RO */
111 /* mismatched keys, fetch protection -> inaccessible */
117 * guest: set storage key of page 0 to 9 and enable fetch protection
120 * enable fetch protection override
122 /* mismatched keys, fetch protection, but override applies -> RO */
[all …]
|
| /linux/Documentation/core-api/ |
| H A D | protection-keys.rst | 4 Memory Protection Keys
7 Memory Protection Keys provide a mechanism for enforcing page-based
9 application changes protection domains.
20 a "protection key", giving 16 possible keys.
37 Pkeys use 3 bits in each page table entry, to encode a "protection key index",
42 overlay permissions for each protection key index.
47 Unlike x86_64, the protection key permissions also apply to instruction
92 The kernel attempts to make protection keys consistent with the
98 you can expect the same effects with protection keys when doing this::
115 to SEGV_PKERR when violating protection keys versus SEGV_ACCERR when
[all …]
|
| /linux/Documentation/devicetree/bindings/regulator/ |
| H A D | regulator.yaml | 125 regulator-over-current-protection:
126 description: Enable over current protection.
129 regulator-oc-protection-microamp:
130 description: Set over current protection limit. This is a limit where
132 protection and value '1' indicates that protection should be enabled but
148 regulator-ov-protection-microvolt:
149 description: Set over voltage protection limit. This is a limit where
151 protection and value '1' indicates that protection should be enabled but
170 regulator-uv-protection-microvolt:
171 description: Set under voltage protection limit. This is a limit where
[all …]
|
| /linux/drivers/soc/mediatek/ |
| H A D | mtk-infracfg.c | 17 * mtk_infracfg_set_bus_protection - enable bus protection
19 * @mask: The mask containing the protection bits to be enabled.
20 * @reg_update: The boolean flag determines to set the protection bits
24 * This function enables the bus protection bits for disabled power
48 * mtk_infracfg_clear_bus_protection - disable bus protection
50 * @mask: The mask containing the protection bits to be disabled.
51 * @reg_update: The boolean flag determines to clear the protection bits
55 * This function disables the bus protection bits previously enabled with
|
| /linux/drivers/platform/x86/ |
| H A D | toshiba_haps.c | 3 * Toshiba HDD Active Protection Sensor (HAPS) driver
18 MODULE_DESCRIPTION("Toshiba HDD Active Protection Sensor");
36 pr_err("Unable to reset the HDD protection\n"); in toshiba_haps_reset_protection()
49 pr_err("Error while setting the protection level\n"); in toshiba_haps_protection_level()
53 pr_debug("HDD protection level set to: %d\n", level); in toshiba_haps_protection_level()
111 /* Reset the protection interface */ in reset_protection_store()
171 pr_err("ACPI call to query HDD protection failed\n"); in toshiba_haps_available()
176 pr_info("HDD protection not available or using SSD\n"); in toshiba_haps_available()
199 pr_info("Toshiba HDD Active Protection Sensor device\n"); in toshiba_haps_probe()
211 /* Set the protection level, currently at level 2 (Medium) */ in toshiba_haps_probe()
[all …]
|
| /linux/tools/testing/selftests/cgroup/ |
| H A 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/drivers/accel/habanalabs/common/ |
| H A D | security.h | 62 * of IP block which has protection bits.
65 * @prot_map: each bit corresponds to one among 32 protection configuration regs
67 * to be written into the corresponding protection configuration reg.
69 * @data_map: each bit corresponds to one among 32 protection configuration regs
70 * (e.g., SPECIAL_GLBL_PRIV). '1' means corresponding protection
74 * to corresponding protection configuration reg(s).
78 * protection configuration registers e.g., SPECIAL GLBL PRIV regs (starting at
79 * offset 0xE80). '1' in 'data_map' means protection configuration to be done
80 * using configuration in data array. '0' in 'data_map" means protection
|
| /linux/drivers/mtd/maps/ |
| H A D | physmap-versatile.c | 65 * Flash protection handling for the Integrator/AP
100 /* Clear VPP and write protection bits */ in ap_flash_init()
142 * Flash protection handling for the Integrator/CP
172 * Flash protection handling for the Versatiles and RealViews
197 /* Not all flash chips use this protection line */ in of_flash_probe_versatile()
224 dev_info(&pdev->dev, "Integrator/AP flash protection\n"); in of_flash_probe_versatile()
228 dev_info(&pdev->dev, "Integrator/CP flash protection\n"); in of_flash_probe_versatile()
233 dev_info(&pdev->dev, "versatile/realview flash protection\n"); in of_flash_probe_versatile()
|
| /linux/Documentation/devicetree/bindings/mfd/ |
| H A D | rohm,bd96801-pmic.yaml | 106 regulator-temp-protection-kelvin = <1>;
117 regulator-temp-protection-kelvin = <1>;
128 regulator-temp-protection-kelvin = <1>;
139 regulator-temp-protection-kelvin = <1>;
150 regulator-temp-protection-kelvin = <1>;
161 regulator-temp-protection-kelvin = <1>;
172 regulator-temp-protection-kelvin = <1>;
|
| /linux/drivers/gpu/drm/display/ |
| H A D | drm_hdcp_helper.c | 326 * drm_connector_attach_content_protection_property - attach content protection in DRM_ENUM_NAME_FN()
332 * This is used to add support for content protection on select connectors. in DRM_ENUM_NAME_FN()
333 * Content Protection is intentionally vague to allow for different underlying in DRM_ENUM_NAME_FN()
346 * The content protection will be set to &drm_connector_state.content_protection in DRM_ENUM_NAME_FN()
348 * When kernel triggered content protection state change like DESIRED->ENABLED in DRM_ENUM_NAME_FN()
350 * the content protection state of a connector. in DRM_ENUM_NAME_FN()
363 prop = drm_property_create_enum(dev, 0, "Content Protection", in DRM_ENUM_NAME_FN()
394 * drm_hdcp_update_content_protection - Updates the content protection state
397 * @connector: drm_connector on which content protection state needs an update
398 * @val: New state of the content protection property
[all …]
|
| /linux/include/dt-bindings/dma/ |
| H A D | dw-dmac.h | 7 * Protection Control bits provide protection against illegal transactions.
8 * The protection bits[0:2] are one-to-one mapped to AHB HPROT[3:1] signals.
|
| /linux/drivers/net/wireless/intel/iwlwifi/fw/api/ |
| H A D | time-event.h | 432 * enum iwl_session_prot_conf_id - session protection's configurations
433 * @SESSION_PROTECT_CONF_ASSOC: Start a session protection for association.
449 * Only the duration is configurable for this protection.
470 * struct iwl_session_prot_cmd - configure a session protection
472 * for which this session protection is sent
476 * @duration_tu: the duration of the whole protection in TUs.
480 * Note: the session protection will always be scheduled to start as
482 * The firmware supports only one concurrent session protection per vif.
483 * Adding a new session protection will remove any currently running session.
499 * struct iwl_session_prot_notif - session protection started / ended
[all …]
|
| /linux/Documentation/admin-guide/laptops/ |
| H A 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/drivers/mtd/chips/ |
| H A D | Kconfig | 156 bool "Protection Registers aka one-time programmable (OTP) bits"
161 "Protection Registers" present on some flash chips.
165 The user-programmable Protection Registers contain one-time
167 erased. Each Protection Register can be accessed multiple times to
170 Each Protection Register has an associated Lock Register bit. When a
171 Lock Register bit is programmed, the associated Protection Register
174 Lock Register bits cannot be erased. Therefore, when a Protection
|
| /linux/Documentation/ABI/removed/ |
| H A 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/Documentation/devicetree/bindings/usb/ |
| H A 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/include/linux/mfd/ |
| H A D | rohm-bd957x.h | 19 * - Over voltage protection
20 * - Short-circuit protection
21 * - Over current protection
24 * - Under voltage protection
|
| /linux/arch/arm/boot/dts/st/ |
| H A D | stm32mp15xx-osd32.dtsi | 85 regulator-over-current-protection;
94 regulator-over-current-protection;
104 regulator-over-current-protection;
112 regulator-over-current-protection;
135 regulator-over-current-protection;
|
| H A 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;
|
| /linux/Documentation/devicetree/bindings/leds/backlight/ |
| H A D | mps,mp3309c.yaml | 41 mps,overvoltage-protection-microvolt:
42 description: Overvoltage protection (13.5V, 24V or 35.5V).
69 mps,overvoltage-protection-microvolt = <24000000>;
|
| /linux/include/uapi/linux/ |
| H A D | userfaultfd.h | 218 * write-protection mode is supported on both shmem and hugetlbfs.
221 * write-protection mode will always apply to unpopulated pages
224 * when userfault write-protection mode is registered.
226 * UFFD_FEATURE_WP_ASYNC indicates that userfaultfd write-protection
228 * automatically resolved and write-protection is un-set.
312 * unset the flag to undo protection of a range which was previously
320 * protection (WP=0) in response to a page fault wakes the faulting
|
| /linux/Documentation/arch/x86/ |
| H A 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/tools/perf/util/ |
| H A D | setup.py | 45 if not clang_has_option("-fcf-protection"):
46 vars[var] = sub("-fcf-protection", "", vars[var])
47 if not clang_has_option("-fstack-clash-protection"):
48 vars[var] = sub("-fstack-clash-protection", "", vars[var])
|