forked from torvalds/linux
-
Notifications
You must be signed in to change notification settings - Fork 132
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #3576 from plbossart/merge/sound-upstream-20220408
Merge/sound upstream 20220408
- Loading branch information
Showing
13,517 changed files
with
1,064,495 additions
and
327,030 deletions.
The diff you're trying to view is too large. We only load the first 3000 changed files.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -895,6 +895,12 @@ S: 3000 FORE Drive | |
| S: Warrendale, Pennsylvania 15086 | ||
| S: USA | ||
|
|
||
| N: Ludovic Desroches | ||
| E: [email protected] | ||
| D: Maintainer for ARM/Microchip (AT91) SoC support | ||
| D: Author of ADC, pinctrl, XDMA and SDHCI drivers for this platform | ||
| S: France | ||
|
|
||
| N: Martin Devera | ||
| E: [email protected] | ||
| W: http://luxik.cdi.cz/~devik/qos/ | ||
|
|
||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,10 @@ | ||
| What: /proc/i8k | ||
| Date: November 2001 | ||
| KernelVersion: 2.4.14 | ||
| Contact: Pali Rohár <[email protected]> | ||
| Description: Legacy interface for getting/setting sensor information like | ||
| fan speed, temperature, serial number, hotkey status etc | ||
| on Dell Laptops. | ||
| Since the driver is now using the standard hwmon sysfs interface, | ||
| the procfs interface is deprecated. | ||
| Users: https://github.com/vitorafsr/i8kutils |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,37 @@ | ||
| What: /sys/devices/system/machinecheck/machinecheckX/tolerant | ||
| Contact: Borislav Petkov <[email protected]> | ||
| Date: Dec, 2021 | ||
| Description: | ||
| Unused and obsolete after the advent of recoverable machine | ||
| checks (see last sentence below) and those are present since | ||
| 2010 (Nehalem). | ||
|
|
||
| Original description: | ||
|
|
||
| The entries appear for each CPU, but they are truly shared | ||
| between all CPUs. | ||
|
|
||
| Tolerance level. When a machine check exception occurs for a | ||
| non corrected machine check the kernel can take different | ||
| actions. | ||
|
|
||
| Since machine check exceptions can happen any time it is | ||
| sometimes risky for the kernel to kill a process because it | ||
| defies normal kernel locking rules. The tolerance level | ||
| configures how hard the kernel tries to recover even at some | ||
| risk of deadlock. Higher tolerant values trade potentially | ||
| better uptime with the risk of a crash or even corruption | ||
| (for tolerant >= 3). | ||
|
|
||
| == =========================================================== | ||
| 0 always panic on uncorrected errors, log corrected errors | ||
| 1 panic or SIGBUS on uncorrected errors, log corrected errors | ||
| 2 SIGBUS or log uncorrected errors, log corrected errors | ||
| 3 never panic or SIGBUS, log all errors (for testing only) | ||
| == =========================================================== | ||
|
|
||
| Default: 1 | ||
|
|
||
| Note this only makes a difference if the CPU allows recovery | ||
| from a machine check exception. Current x86 CPUs generally | ||
| do not. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -155,6 +155,55 @@ Description: | |
| last zone of the device which may be smaller. | ||
|
|
||
|
|
||
| What: /sys/block/<disk>/queue/crypto/ | ||
| Date: February 2022 | ||
| Contact: [email protected] | ||
| Description: | ||
| The presence of this subdirectory of /sys/block/<disk>/queue/ | ||
| indicates that the device supports inline encryption. This | ||
| subdirectory contains files which describe the inline encryption | ||
| capabilities of the device. For more information about inline | ||
| encryption, refer to Documentation/block/inline-encryption.rst. | ||
|
|
||
|
|
||
| What: /sys/block/<disk>/queue/crypto/max_dun_bits | ||
| Date: February 2022 | ||
| Contact: [email protected] | ||
| Description: | ||
| [RO] This file shows the maximum length, in bits, of data unit | ||
| numbers accepted by the device in inline encryption requests. | ||
|
|
||
|
|
||
| What: /sys/block/<disk>/queue/crypto/modes/<mode> | ||
| Date: February 2022 | ||
| Contact: [email protected] | ||
| Description: | ||
| [RO] For each crypto mode (i.e., encryption/decryption | ||
| algorithm) the device supports with inline encryption, a file | ||
| will exist at this location. It will contain a hexadecimal | ||
| number that is a bitmask of the supported data unit sizes, in | ||
| bytes, for that crypto mode. | ||
|
|
||
| Currently, the crypto modes that may be supported are: | ||
|
|
||
| * AES-256-XTS | ||
| * AES-128-CBC-ESSIV | ||
| * Adiantum | ||
|
|
||
| For example, if a device supports AES-256-XTS inline encryption | ||
| with data unit sizes of 512 and 4096 bytes, the file | ||
| /sys/block/<disk>/queue/crypto/modes/AES-256-XTS will exist and | ||
| will contain "0x1200". | ||
|
|
||
|
|
||
| What: /sys/block/<disk>/queue/crypto/num_keyslots | ||
| Date: February 2022 | ||
| Contact: [email protected] | ||
| Description: | ||
| [RO] This file shows the number of keyslots the device has for | ||
| use with inline encryption. | ||
|
|
||
|
|
||
| What: /sys/block/<disk>/queue/dax | ||
| Date: June 2016 | ||
| Contact: [email protected] | ||
|
|
||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -113,3 +113,144 @@ Description: | |
| # echo 0 > /sys/devices/platform/firmware\:zynqmp-firmware/health_status | ||
|
|
||
| Users: Xilinx | ||
|
|
||
| What: /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id | ||
| Date: Feb 2022 | ||
| KernelVersion: 5.18 | ||
| Contact: "Ronak Jain" <[email protected]> | ||
| Description: | ||
| This sysfs interface allows user to configure features at | ||
| runtime. The user can enable or disable features running at | ||
| firmware as well as the user can configure the parameters of | ||
| the features at runtime. The supported features are over | ||
| temperature and external watchdog. Here, the external watchdog | ||
| is completely different than the /dev/watchdog as the external | ||
| watchdog is running on the firmware and it is used to monitor | ||
| the health of firmware not APU(Linux). Also, the external | ||
| watchdog is interfaced outside of the zynqmp soc. | ||
|
|
||
| The supported config ids are for the feature configuration is, | ||
| 1. PM_FEATURE_OVERTEMP_STATUS = 1, the user can enable or | ||
| disable the over temperature feature. | ||
| 2. PM_FEATURE_OVERTEMP_VALUE = 2, the user can configure the | ||
| over temperature limit in Degree Celsius. | ||
| 3. PM_FEATURE_EXTWDT_STATUS = 3, the user can enable or disable | ||
| the external watchdog feature. | ||
| 4. PM_FEATURE_EXTWDT_VALUE = 4, the user can configure the | ||
| external watchdog feature. | ||
|
|
||
| Usage: | ||
|
|
||
| Select over temperature config ID to enable/disable feature | ||
| # echo 1 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id | ||
|
|
||
| Check over temperature config ID is selected or not | ||
| # cat /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id | ||
| The expected result is 1. | ||
|
|
||
| Select over temperature config ID to configure OT limit | ||
| # echo 2 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id | ||
|
|
||
| Check over temperature config ID is selected or not | ||
| # cat /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id | ||
| The expected result is 2. | ||
|
|
||
| Select external watchdog config ID to enable/disable feature | ||
| # echo 3 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id | ||
|
|
||
| Check external watchdog config ID is selected or not | ||
| # cat /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id | ||
| The expected result is 3. | ||
|
|
||
| Select external watchdog config ID to configure time interval | ||
| # echo 4 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id | ||
|
|
||
| Check external watchdog config ID is selected or not | ||
| # cat /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id | ||
| The expected result is 4. | ||
|
|
||
| Users: Xilinx | ||
|
|
||
| What: /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value | ||
| Date: Feb 2022 | ||
| KernelVersion: 5.18 | ||
| Contact: "Ronak Jain" <[email protected]> | ||
| Description: | ||
| This sysfs interface allows to configure features at runtime. | ||
| The user can enable or disable features running at firmware. | ||
| Also, the user can configure the parameters of the features | ||
| at runtime. The supported features are over temperature and | ||
| external watchdog. Here, the external watchdog is completely | ||
| different than the /dev/watchdog as the external watchdog is | ||
| running on the firmware and it is used to monitor the health | ||
| of firmware not APU(Linux). Also, the external watchdog is | ||
| interfaced outside of the zynqmp soc. | ||
|
|
||
| By default the features are disabled in the firmware. The user | ||
| can enable features by querying appropriate config id of the | ||
| features. | ||
|
|
||
| The default limit for the over temperature is 90 Degree Celsius. | ||
| The default timer interval for the external watchdog is 570ms. | ||
|
|
||
| The supported config ids are for the feature configuration is, | ||
| 1. PM_FEATURE_OVERTEMP_STATUS = 1, the user can enable or | ||
| disable the over temperature feature. | ||
| 2. PM_FEATURE_OVERTEMP_VALUE = 2, the user can configure the | ||
| over temperature limit in Degree Celsius. | ||
| 3. PM_FEATURE_EXTWDT_STATUS = 3, the user can enable or disable | ||
| the external watchdog feature. | ||
| 4. PM_FEATURE_EXTWDT_VALUE = 4, the user can configure the | ||
| external watchdog feature. | ||
|
|
||
| Usage: | ||
|
|
||
| Enable over temperature feature | ||
| # echo 1 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id | ||
| # echo 1 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value | ||
|
|
||
| Check whether the over temperature feature is enabled or not | ||
| # cat /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value | ||
| The expected result is 1. | ||
|
|
||
| Disable over temperature feature | ||
| # echo 1 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id | ||
| # echo 0 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value | ||
|
|
||
| Check whether the over temperature feature is disabled or not | ||
| # cat /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value | ||
| The expected result is 0. | ||
|
|
||
| Configure over temperature limit to 50 Degree Celsius | ||
| # echo 2 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id | ||
| # echo 50 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value | ||
|
|
||
| Check whether the over temperature limit is configured or not | ||
| # cat /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value | ||
| The expected result is 50. | ||
|
|
||
| Enable external watchdog feature | ||
| # echo 3 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id | ||
| # echo 1 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value | ||
|
|
||
| Check whether the external watchdog feature is enabled or not | ||
| # cat /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value | ||
| The expected result is 1. | ||
|
|
||
| Disable external watchdog feature | ||
| # echo 3 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id | ||
| # echo 0 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value | ||
|
|
||
| Check whether the external watchdog feature is disabled or not | ||
| # cat /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value | ||
| The expected result is 0. | ||
|
|
||
| Configure external watchdog timer interval to 500ms | ||
| # echo 4 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_id | ||
| # echo 500 > /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value | ||
|
|
||
| Check whether the external watchdog timer interval is configured or not | ||
| # cat /sys/devices/platform/firmware\:zynqmp-firmware/feature_config_value | ||
| The expected result is 500. | ||
|
|
||
| Users: Xilinx | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.