| /OK3568_Linux_fs/u-boot/arch/arm/include/asm/arch-sunxi/ |
| H A D | tzpc.h | 13 u32 decport0_status; /* 0x04 Status of decode protection port 0 */
14 u32 decport0_set; /* 0x08 Set decode protection port 0 */
15 u32 decport0_clear; /* 0x0c Clear decode protection port 0 */
17 u32 decport1_status; /* 0x10 Status of decode protection port 1 */
18 u32 decport1_set; /* 0x14 Set decode protection port 1 */
19 u32 decport1_clear; /* 0x18 Clear decode protection port 1 */
20 u32 decport2_status; /* 0x1c Status of decode protection port 2 */
21 u32 decport2_set; /* 0x20 Set decode protection port 2 */
22 u32 decport2_clear; /* 0x24 Clear decode protection port 2 */
|
| /OK3568_Linux_fs/kernel/drivers/platform/x86/ |
| H A D | toshiba_haps.c | 3 * Toshiba HDD Active Protection Sensor (HAPS) driver
17 MODULE_DESCRIPTION("Toshiba HDD Active Protection Sensor");
35 pr_err("Unable to reset the HDD protection\n"); in toshiba_haps_reset_protection()
48 pr_err("Error while setting the protection level\n"); in toshiba_haps_protection_level()
52 pr_debug("HDD protection level set to: %d\n", level); in toshiba_haps_protection_level()
110 /* Reset the protection interface */ in reset_protection_store()
163 pr_err("ACPI call to query HDD protection failed\n"); in toshiba_haps_available()
168 pr_info("HDD protection not available or using SSD\n"); in toshiba_haps_available()
186 pr_info("Toshiba HDD Active Protection Sensor device\n"); in toshiba_haps_add()
197 /* Set the protection level, currently at level 2 (Medium) */ in toshiba_haps_add()
[all …]
|
| /OK3568_Linux_fs/kernel/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).
|
| /OK3568_Linux_fs/kernel/Documentation/admin-guide/laptops/ |
| H A D | toshiba_haps.rst | 2 Toshiba HDD Active Protection Sensor
23 laptops, being called "Toshiba HDD Protection - Shock Sensor" officially,
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::
[all …]
|
| 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.
|
| /OK3568_Linux_fs/kernel/drivers/soc/mediatek/ |
| H A D | mtk-infracfg.c | 21 * mtk_infracfg_set_bus_protection - enable bus protection
23 * @mask: The mask containing the protection bits to be enabled.
24 * @reg_update: The boolean flag determines to set the protection bits
28 * This function enables the bus protection bits for disabled power
52 * mtk_infracfg_clear_bus_protection - disable bus protection
54 * @mask: The mask containing the protection bits to be disabled.
55 * @reg_update: The boolean flag determines to clear the protection bits
59 * This function disables the bus protection bits previously enabled with
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/power/supply/ |
| H A D | sc8551_charger.txt | 16 - sc,sc8551,bat-ovp-disable: enable the battery over voltage protection
17 - sc,sc8551,bat-ocp-disable: enable the battery over current protection
18 - sc,sc8551,bus-ocp-disable: enable the bus over voltage protection
19 - sc,sc8551,bat-ovp-threshold: Configures the battery over voltage protection voltage (in uV).
20 - sc,sc8551,bat-ocp-threshold: Configures the battery over current protection voltage (in uA).
21 - sc,sc8551,bus-ovp-threshold: Configures the bus over voltage protection voltage (in uV).
22 - sc,sc8551,bus-ocp-threshold: Configures the bus over current protection voltage (in uA).
23 - sc,sc8551,ac-ovp-threshold: Configures the AC voltage protection voltage (in uV).
|
| /OK3568_Linux_fs/kernel/Documentation/block/ |
| H A D | data-integrity.rst | 16 protocols (SBC Data Integrity Field, SCC protection proposal) as well
17 as SATA/T13 (External Path Protection) try to remedy this by adding
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
[all …]
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/recipes-support/exiv2/exiv2/ |
| H A D | 0001-Use-compiler-fcf-protection-only-if-compiler-arch-su.patch | 4 Subject: [PATCH] Use compiler -fcf-protection only if compiler/arch supports
28 - add_compile_options(-fstack-clash-protection -fcf-protection)
29 + # Gcc does support -fcf-protection on few arches only
30 + CHECK_CXX_COMPILER_FLAG(-fcf-protection COMPILER_SUPPORTS_FCF_PROTECTION)
32 + add_compile_options(-fcf-protection)
34 + add_compile_options(-fstack-clash-protection)
|
| /OK3568_Linux_fs/kernel/Documentation/core-api/ |
| H A D | protection-keys.rst | 4 Memory Protection Keys
7 Memory Protection Keys for Userspace (PKU aka PKEYs) is a feature
16 Memory Protection Keys provides a mechanism for enforcing page-based
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
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/soc/qcom/ |
| H A 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";
|
| /OK3568_Linux_fs/kernel/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()
|
| /OK3568_Linux_fs/kernel/drivers/gpu/drm/ |
| H A D | drm_hdcp.c | 328 * drm_connector_attach_content_protection_property - attach content protection in DRM_ENUM_NAME_FN()
334 * This is used to add support for content protection on select connectors. in DRM_ENUM_NAME_FN()
335 * Content Protection is intentionally vague to allow for different underlying in DRM_ENUM_NAME_FN()
348 * The content protection will be set to &drm_connector_state.content_protection in DRM_ENUM_NAME_FN()
350 * When kernel triggered content protection state change like DESIRED->ENABLED in DRM_ENUM_NAME_FN()
352 * the content protection state of a connector. in DRM_ENUM_NAME_FN()
365 prop = drm_property_create_enum(dev, 0, "Content Protection", in DRM_ENUM_NAME_FN()
396 * drm_hdcp_update_content_protection - Updates the content protection state
399 * @connector: drm_connector on which content protection state needs an update
400 * @val: New state of the content protection property
[all …]
|
| /OK3568_Linux_fs/kernel/drivers/net/wireless/intel/iwlwifi/fw/api/ |
| H A D | time-event.h | 397 * enum iwl_mvm_session_prot_conf_id - session protection's configurations
398 * @SESSION_PROTECT_CONF_ASSOC: Start a session protection for association.
414 * Only the duration is configurable for this protection.
435 * struct iwl_mvm_session_prot_cmd - configure a session protection
436 * @id_and_color: the id and color of the mac for which this session protection
440 * @duration_tu: the duration of the whole protection in TUs.
444 * Note: the session protection will always be scheduled to start as
446 * The firmware supports only one concurrent session protection per vif.
447 * Adding a new session protection will remove any currently running session.
460 * struct iwl_mvm_session_prot_notif - session protection started / ended
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/mfd/ |
| H A 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
|
| H A D | st,stpmic1.yaml | 126 regulator-over-current-protection: true
145 regulator-over-current-protection: true
182 regulator-over-current-protection: true
210 regulator-over-current-protection: true
234 regulator-over-current-protection: true
249 regulator-over-current-protection: true
328 regulator-over-current-protection;
|
| /OK3568_Linux_fs/kernel/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
|
| /OK3568_Linux_fs/kernel/arch/x86/mm/ |
| H A D | setup_nx.c | 45 printk(KERN_NOTICE "Notice: NX (Execute Disable) protection " in x86_report_nx()
50 printk(KERN_INFO "NX (Execute Disable) protection: " in x86_report_nx()
53 printk(KERN_INFO "NX (Execute Disable) protection: " in x86_report_nx()
58 printk(KERN_NOTICE "Notice: NX (Execute Disable) protection " in x86_report_nx()
|
| /OK3568_Linux_fs/kernel/drivers/net/wireless/intel/iwlwifi/mvm/ |
| H A D | time-event.h | 119 * iwl_mvm_protect_session - start / extend the session protection.
129 * This function can be used to start a session protection which means that the
142 * iwl_mvm_stop_session_protection - cancel the session protection.
146 * This functions cancels the session protection which is an act of good
252 * iwl_mvm_schedule_session_protection - schedule a session protection
254 * @vif: the virtual interface for which the protection issued
255 * @duration: the duration of the protection
256 * @wait_for_notif: if true, will block until the start of the protection
|
| /OK3568_Linux_fs/kernel/arch/arm64/ |
| H A D | Makefile | 69 # Ensure that if the compiler supports branch protection we default it
70 # off, this will be overridden if we are using branch protection.
71 branch-prot-flags-y += $(call cc-option,-mbranch-protection=none)
75 # We enable additional protection for leaf functions as there is some
76 # narrow potential for ROP protection benefits and no substantial
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
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/aarch64-none-linux-gnu/libc/usr/include/bits/ |
| H A D | mman-shared.h | 57 /* Allocate a new protection key, with the PKEY_DISABLE_* bits
58 specified in ACCESS_RIGHTS. The protection key mask for the
71 /* Free an allocated protection key, which must have been allocated
75 /* Apply memory protection flags for KEY to the specified address
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/arm-none-linux-gnueabihf/libc/usr/include/bits/ |
| H A D | mman-shared.h | 57 /* Allocate a new protection key, with the PKEY_DISABLE_* bits
58 specified in ACCESS_RIGHTS. The protection key mask for the
71 /* Free an allocated protection key, which must have been allocated
75 /* Apply memory protection flags for KEY to the specified address
|
| /OK3568_Linux_fs/u-boot/arch/arm/dts/ |
| H A D | stm32mp157a-dk1.dts | 114 regulator-over-current-protection;
123 regulator-over-current-protection;
133 regulator-over-current-protection;
141 regulator-over-current-protection;
166 regulator-over-current-protection;
196 regulator-over-current-protection;
|
| /OK3568_Linux_fs/kernel/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.
|
| /OK3568_Linux_fs/kernel/arch/s390/kvm/ |
| H A D | gaccess.h | 96 * guest memory access protection facilities, like key or low address
97 * protection, are applicable.
217 * In addition also low address and DAT protection are inspected before
218 * copying any data (key protection is currently not implemented).
221 * In case of an access exception (e.g. protection exception) pgm will contain
303 * Guest low address and key protection are not checked.
326 * Guest key protection is not checked.
349 * Guest low address and key protection are not checked.
372 * Guest key protection is not checked.
|