| /kernel/linux/linux-6.6/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 …]
|
| /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-6.6/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-6.6/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()
161 pr_err("ACPI call to query HDD protection failed\n"); in toshiba_haps_available()
166 pr_info("HDD protection not available or using SSD\n"); in toshiba_haps_available()
184 pr_info("Toshiba HDD Active Protection Sensor device\n"); in toshiba_haps_add()
195 /* Set the protection level, currently at level 2 (Medium) */ in toshiba_haps_add()
[all …]
|
| /kernel/linux/linux-6.6/tools/testing/selftests/kvm/s390x/ |
| 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 …]
|
| /kernel/linux/linux-6.6/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/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-6.6/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 …]
|
| /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-6.6/drivers/soc/mediatek/ |
| 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
|
| /kernel/linux/linux-6.6/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-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-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/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-6.6/Documentation/core-api/ |
| D | protection-keys.rst | 4 Memory Protection Keys
7 Memory Protection Keys provide a mechanism for enforcing page-based
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
|
| /kernel/linux/linux-6.6/drivers/accel/habanalabs/common/ |
| D | security.h | 63 * of IP block which has protection bits.
66 * @prot_map: each bit corresponds to one among 32 protection configuration regs
68 * to be written into the corresponding protection configuration reg.
70 * @data_map: each bit corresponds to one among 32 protection configuration regs
71 * (e.g., SPECIAL_GLBL_PRIV). '1' means corresponding protection
75 * to corresponding protection configuration reg(s).
79 * protection configuration registers e.g., SPECIAL GLBL PRIV regs (starting at
80 * offset 0xE80). '1' in 'data_map' means protection configuration to be done
81 * using configuration in data array. '0' in 'data_map" means protection
|
| /kernel/linux/linux-6.6/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")
|
| /kernel/linux/linux-5.10/drivers/mtd/maps/ |
| 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()
|
| /kernel/linux/linux-6.6/drivers/mtd/maps/ |
| 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()
|
| /kernel/linux/linux-6.6/drivers/net/wireless/intel/iwlwifi/fw/api/ |
| D | time-event.h | 339 * enum iwl_mvm_session_prot_conf_id - session protection's configurations
340 * @SESSION_PROTECT_CONF_ASSOC: Start a session protection for association.
356 * Only the duration is configurable for this protection.
377 * struct iwl_mvm_session_prot_cmd - configure a session protection
378 * @id_and_color: the id and color of the mac for which this session protection
383 * @duration_tu: the duration of the whole protection in TUs.
387 * Note: the session protection will always be scheduled to start as
389 * The firmware supports only one concurrent session protection per vif.
390 * Adding a new session protection will remove any currently running session.
403 * struct iwl_mvm_session_prot_notif - session protection started / ended
[all …]
|
| /kernel/linux/linux-6.6/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/linux/linux-6.6/drivers/gpu/drm/display/ |
| 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 …]
|
| /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 …]
|