| /kernel/liteos_m/targets/riscv_nuclei_gd32vf103_soc_gcc/SoC/gd32vf103/Common/Include/ |
| D | gd32vf103_fmc.h | 55 …P REG32((FMC) + 0x20U) /*!< FMC erase/program protection register */
58 …C REG16((OB) + 0x00U) /*!< option byte security protection value */
60 …e OB_WP0 REG16((OB) + 0x08U) /*!< option byte write protection 0 */
61 …e OB_WP1 REG16((OB) + 0x0AU) /*!< option byte write protection 1 */
62 …e OB_WP2 REG16((OB) + 0x0CU) /*!< option byte write protection 2 */
63 …e OB_WP3 REG16((OB) + 0x0EU) /*!< option byte write protection 3 */
78 #define FMC_STAT0_WPERR BIT(4) /*!< erase/program protection er…
98 …BSTAT_SPC BIT(1) /*!< option bytes security protection code */
133 …FMC_WPERR, /*!< erase/program protection error …
149 …BIT(FMC_STAT0_REG_OFFSET, 4U), /*!< FMC erase/program protection error flag bit */
[all …]
|
| /kernel/linux/linux-4.19/Documentation/laptops/ |
| D | toshiba_haps.txt | 2 Toshiba HDD Active Protection Sensor
22 laptops, being called "Toshiba HDD Protection - Shock Sensor" officially,
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:
[all …]
|
| /kernel/linux/linux-4.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).
|
| /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).
|
| /kernel/linux/linux-5.10/drivers/platform/x86/ |
| 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 …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/laptops/ |
| 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 …]
|
| /kernel/linux/linux-5.10/drivers/soc/mediatek/ |
| 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
|
| /kernel/linux/linux-4.19/drivers/platform/x86/ |
| D | toshiba_haps.c | 2 * Toshiba HDD Active Protection Sensor (HAPS) driver
27 MODULE_DESCRIPTION("Toshiba HDD Active Protection Sensor");
45 pr_err("Unable to reset the HDD protection\n"); in toshiba_haps_reset_protection()
58 pr_err("Error while setting the protection level\n"); in toshiba_haps_protection_level()
62 pr_debug("HDD protection level set to: %d\n", level); in toshiba_haps_protection_level()
120 /* Reset the protection interface */ in reset_protection_store()
173 pr_err("ACPI call to query HDD protection failed\n"); in toshiba_haps_available()
178 pr_info("HDD protection not available or using SSD\n"); in toshiba_haps_available()
196 pr_info("Toshiba HDD Active Protection Sensor device\n"); in toshiba_haps_add()
207 /* Set the protection level, currently at level 2 (Medium) */ in toshiba_haps_add()
[all …]
|
| /kernel/linux/linux-4.19/drivers/soc/mediatek/ |
| D | mtk-infracfg.c | 29 * mtk_infracfg_set_bus_protection - enable bus protection
31 * @mask: The mask containing the protection bits to be enabled.
32 * @reg_update: The boolean flag determines to set the protection bits
36 * This function enables the bus protection bits for disabled power
60 * mtk_infracfg_clear_bus_protection - disable bus protection
62 * @mask: The mask containing the protection bits to be disabled.
63 * @reg_update: The boolean flag determines to clear the protection bits
67 * This function disables the bus protection bits previously enabled with
|
| /kernel/linux/linux-5.10/Documentation/core-api/ |
| 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
|
| /kernel/linux/linux-5.10/Documentation/block/ |
| 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 …]
|
| /kernel/linux/linux-4.19/Documentation/block/ |
| D | data-integrity.txt | 12 protocols (SBC Data Integrity Field, SCC protection proposal) as well
13 as SATA/T13 (External Path Protection) try to remedy this by adding
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
[all …]
|
| /kernel/linux/linux-4.19/Documentation/x86/ |
| D | protection-keys.txt | 1 Memory Protection Keys for Userspace (PKU aka PKEYs) is a feature
9 Memory Protection Keys provides a mechanism for enforcing page-based
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
|
| /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/drivers/mtd/maps/ |
| D | physmap-versatile.c | 65 * Flash protection handling for the Integrator/AP
99 /* Clear VPP and write protection bits */ in ap_flash_init()
141 * Flash protection handling for the Integrator/CP
171 * Flash protection handling for the Versatiles and RealViews
196 /* Not all flash chips use this protection line */ in of_flash_probe_versatile()
222 dev_info(&pdev->dev, "Integrator/AP flash protection\n"); in of_flash_probe_versatile()
226 dev_info(&pdev->dev, "Integrator/CP flash protection\n"); in of_flash_probe_versatile()
231 dev_info(&pdev->dev, "versatile/realview flash protection\n"); in of_flash_probe_versatile()
|
| /kernel/linux/linux-4.19/drivers/mtd/maps/ |
| D | physmap_of_versatile.c | 79 * Flash protection handling for the Integrator/AP
113 /* Clear VPP and write protection bits */ in ap_flash_init()
155 * Flash protection handling for the Integrator/CP
185 * Flash protection handling for the Versatiles and RealViews
210 /* Not all flash chips use this protection line */ in of_flash_probe_versatile()
236 dev_info(&pdev->dev, "Integrator/AP flash protection\n"); in of_flash_probe_versatile()
240 dev_info(&pdev->dev, "Integrator/CP flash protection\n"); in of_flash_probe_versatile()
245 dev_info(&pdev->dev, "versatile/realview flash protection\n"); in of_flash_probe_versatile()
|
| /kernel/linux/linux-4.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
|
| /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/liteos_m/targets/riscv_nuclei_gd32vf103_soc_gcc/SoC/gd32vf103/Common/Source/Drivers/ |
| D | gd32vf103_fmc.c | 225 /* check the option byte security protection value */ in ob_erase()
244 /* no security protection */ in ob_erase()
264 \brief enable write protection
325 \brief configure security protection
326 \param[in] ob_spc: specify security protection
328 \arg FMC_NSPC: no security protection
329 \arg FMC_USPC: under security protection
465 \brief get the FMC option byte write protection
468 \retval the FMC write protection option byte value
472 /* return the FMC write protection option byte value */ in ob_write_protection_get()
[all …]
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/ |
| 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 …]
|
| /kernel/linux/linux-4.19/arch/x86/mm/ |
| 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()
|
| /kernel/linux/linux-5.10/arch/x86/mm/ |
| 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()
|
| /kernel/linux/linux-5.10/drivers/mtd/chips/ |
| D | Kconfig | 154 bool "Protection Registers aka one-time programmable (OTP) bits"
159 "Protection Registers" present on some flash chips.
163 The user-programmable Protection Registers contain one-time
165 erased. Each Protection Register can be accessed multiple times to
168 Each Protection Register has an associated Lock Register bit. When a
169 Lock Register bit is programmed, the associated Protection Register
172 Lock Register bits cannot be erased. Therefore, when a Protection
|
| /kernel/linux/linux-4.19/drivers/mtd/chips/ |
| D | Kconfig | 153 bool "Protection Registers aka one-time programmable (OTP) bits"
158 "Protection Registers" present on some flash chips.
162 The user-programmable Protection Registers contain one-time
164 erased. Each Protection Register can be accessed multiple times to
167 Each Protection Register has an associated Lock Register bit. When a
168 Lock Register bit is programmed, the associated Protection Register
171 Lock Register bits cannot be erased. Therefore, when a Protection
|
| /kernel/linux/linux-5.10/drivers/net/wireless/intel/iwlwifi/fw/api/ |
| 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 …]
|