forked from torvalds/linux
-
Notifications
You must be signed in to change notification settings - Fork 21
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Changes representative of linux-4.18.0-147.el8.tar.xz
- Loading branch information
Showing
8,499 changed files
with
830,277 additions
and
254,760 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 was deleted.
Oops, something went wrong.
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 @@ | ||
| --mpath redhat/rhdocs/MAINTAINERS --no-git --no-git-fallback |
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,48 @@ | ||
| These files are deprecated and will be removed. The same files are available | ||
| under /sys/bus/typec (see Documentation/ABI/testing/sysfs-bus-typec). | ||
|
|
||
| What: /sys/class/typec/<port|partner|cable>/<dev>/svid | ||
| Date: April 2017 | ||
| Contact: Heikki Krogerus <heikki.krogerus@linux.intel.com> | ||
| Description: | ||
| The SVID (Standard or Vendor ID) assigned by USB-IF for this | ||
| alternate mode. | ||
|
|
||
| What: /sys/class/typec/<port|partner|cable>/<dev>/mode<index>/ | ||
| Date: April 2017 | ||
| Contact: Heikki Krogerus <heikki.krogerus@linux.intel.com> | ||
| Description: | ||
| Every supported mode will have its own directory. The name of | ||
| a mode will be "mode<index>" (for example mode1), where <index> | ||
| is the actual index to the mode VDO returned by Discover Modes | ||
| USB power delivery command. | ||
|
|
||
| What: /sys/class/typec/<port|partner|cable>/<dev>/mode<index>/description | ||
| Date: April 2017 | ||
| Contact: Heikki Krogerus <heikki.krogerus@linux.intel.com> | ||
| Description: | ||
| Shows description of the mode. The description is optional for | ||
| the drivers, just like with the Billboard Devices. | ||
|
|
||
| What: /sys/class/typec/<port|partner|cable>/<dev>/mode<index>/vdo | ||
| Date: April 2017 | ||
| Contact: Heikki Krogerus <heikki.krogerus@linux.intel.com> | ||
| Description: | ||
| Shows the VDO in hexadecimal returned by Discover Modes command | ||
| for this mode. | ||
|
|
||
| What: /sys/class/typec/<port|partner|cable>/<dev>/mode<index>/active | ||
| Date: April 2017 | ||
| Contact: Heikki Krogerus <heikki.krogerus@linux.intel.com> | ||
| Description: | ||
| Shows if the mode is active or not. The attribute can be used | ||
| for entering/exiting the mode with partners and cable plugs, and | ||
| with the port alternate modes it can be used for disabling | ||
| support for specific alternate modes. Entering/exiting modes is | ||
| supported as synchronous operation so write(2) to the attribute | ||
| does not return until the enter/exit mode operation has | ||
| finished. The attribute is notified when the mode is | ||
| entered/exited so poll(2) on the attribute wakes up. | ||
| Entering/exiting a mode will also generate uevent KOBJ_CHANGE. | ||
|
|
||
| Valid values: yes, no |
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 |
|---|---|---|
| @@ -0,0 +1,51 @@ | ||
| What: /sys/bus/typec/devices/.../active | ||
| Date: July 2018 | ||
| Contact: Heikki Krogerus <heikki.krogerus@linux.intel.com> | ||
| Description: | ||
| Shows if the mode is active or not. The attribute can be used | ||
| for entering/exiting the mode. Entering/exiting modes is | ||
| supported as synchronous operation so write(2) to the attribute | ||
| does not return until the enter/exit mode operation has | ||
| finished. The attribute is notified when the mode is | ||
| entered/exited so poll(2) on the attribute wakes up. | ||
| Entering/exiting a mode will also generate uevent KOBJ_CHANGE. | ||
|
|
||
| Valid values are boolean. | ||
|
|
||
| What: /sys/bus/typec/devices/.../description | ||
| Date: July 2018 | ||
| Contact: Heikki Krogerus <heikki.krogerus@linux.intel.com> | ||
| Description: | ||
| Shows description of the mode. The description is optional for | ||
| the drivers, just like with the Billboard Devices. | ||
|
|
||
| What: /sys/bus/typec/devices/.../mode | ||
| Date: July 2018 | ||
| Contact: Heikki Krogerus <heikki.krogerus@linux.intel.com> | ||
| Description: | ||
| The index number of the mode returned by Discover Modes USB | ||
| Power Delivery command. Depending on the alternate mode, the | ||
| mode index may be significant. | ||
|
|
||
| With some alternate modes (SVIDs), the mode index is assigned | ||
| for specific functionality in the specification for that | ||
| alternate mode. | ||
|
|
||
| With other alternate modes, the mode index values are not | ||
| assigned, and can not be therefore used for identification. When | ||
| the mode index is not assigned, identifying the alternate mode | ||
| must be done with either mode VDO or the description. | ||
|
|
||
| What: /sys/bus/typec/devices/.../svid | ||
| Date: July 2018 | ||
| Contact: Heikki Krogerus <heikki.krogerus@linux.intel.com> | ||
| Description: | ||
| The Standard or Vendor ID (SVID) assigned by USB-IF for this | ||
| alternate mode. | ||
|
|
||
| What: /sys/bus/typec/devices/.../vdo | ||
| Date: July 2018 | ||
| Contact: Heikki Krogerus <heikki.krogerus@linux.intel.com> | ||
| Description: | ||
| Shows the VDO in hexadecimal returned by Discover Modes command | ||
| for this mode. |
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,82 @@ | ||
| What: /sys/class/leds/<led>/pattern | ||
| Date: September 2018 | ||
| KernelVersion: 4.20 | ||
| Description: | ||
| Specify a software pattern for the LED, that supports altering | ||
| the brightness for the specified duration with one software | ||
| timer. It can do gradual dimming and step change of brightness. | ||
|
|
||
| The pattern is given by a series of tuples, of brightness and | ||
| duration (ms). The LED is expected to traverse the series and | ||
| each brightness value for the specified duration. Duration of | ||
| 0 means brightness should immediately change to new value, and | ||
| writing malformed pattern deactivates any active one. | ||
|
|
||
| 1. For gradual dimming, the dimming interval now is set as 50 | ||
| milliseconds. So the tuple with duration less than dimming | ||
| interval (50ms) is treated as a step change of brightness, | ||
| i.e. the subsequent brightness will be applied without adding | ||
| intervening dimming intervals. | ||
|
|
||
| The gradual dimming format of the software pattern values should be: | ||
| "brightness_1 duration_1 brightness_2 duration_2 brightness_3 | ||
| duration_3 ...". For example: | ||
|
|
||
| echo 0 1000 255 2000 > pattern | ||
|
|
||
| It will make the LED go gradually from zero-intensity to max (255) | ||
| intensity in 1000 milliseconds, then back to zero intensity in 2000 | ||
| milliseconds: | ||
|
|
||
| LED brightness | ||
| ^ | ||
| 255-| / \ / \ / | ||
| | / \ / \ / | ||
| | / \ / \ / | ||
| | / \ / \ / | ||
| 0-| / \/ \/ | ||
| +---0----1----2----3----4----5----6------------> time (s) | ||
|
|
||
| 2. To make the LED go instantly from one brigntess value to another, | ||
| we should use use zero-time lengths (the brightness must be same as | ||
| the previous tuple's). So the format should be: | ||
| "brightness_1 duration_1 brightness_1 0 brightness_2 duration_2 | ||
| brightness_2 0 ...". For example: | ||
|
|
||
| echo 0 1000 0 0 255 2000 255 0 > pattern | ||
|
|
||
| It will make the LED stay off for one second, then stay at max brightness | ||
| for two seconds: | ||
|
|
||
| LED brightness | ||
| ^ | ||
| 255-| +---------+ +---------+ | ||
| | | | | | | ||
| | | | | | | ||
| | | | | | | ||
| 0-| -----+ +----+ +---- | ||
| +---0----1----2----3----4----5----6------------> time (s) | ||
|
|
||
| What: /sys/class/leds/<led>/hw_pattern | ||
| Date: September 2018 | ||
| KernelVersion: 4.20 | ||
| Description: | ||
| Specify a hardware pattern for the LED, for LED hardware that | ||
| supports autonomously controlling brightness over time, according | ||
| to some preprogrammed hardware patterns. It deactivates any active | ||
| software pattern. | ||
|
|
||
| Since different LED hardware can have different semantics of | ||
| hardware patterns, each driver is expected to provide its own | ||
| description for the hardware patterns in their ABI documentation | ||
| file. | ||
|
|
||
| What: /sys/class/leds/<led>/repeat | ||
| Date: September 2018 | ||
| KernelVersion: 4.20 | ||
| Description: | ||
| Specify a pattern repeat number. -1 means repeat indefinitely, | ||
| other negative numbers and number 0 are invalid. | ||
|
|
||
| This file will always return the originally written repeat | ||
| number. |
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 |
|---|---|---|
| @@ -0,0 +1,49 @@ | ||
| What: /sys/bus/typec/devices/.../displayport/configuration | ||
| Date: July 2018 | ||
| Contact: Heikki Krogerus <heikki.krogerus@linux.intel.com> | ||
| Description: | ||
| Shows the current DisplayPort configuration for the connector. | ||
| Valid values are USB, source and sink. Source means DisplayPort | ||
| source, and sink means DisplayPort sink. | ||
|
|
||
| All supported configurations are listed as space separated list | ||
| with the active one wrapped in square brackets. | ||
|
|
||
| Source example: | ||
|
|
||
| USB [source] sink | ||
|
|
||
| The configuration can be changed by writing to the file | ||
|
|
||
| Note. USB configuration does not equal to Exit Mode. It is | ||
| separate configuration defined in VESA DisplayPort Alt Mode on | ||
| USB Type-C Standard. Functionally it equals to the situation | ||
| where the mode has been exited (to exit the mode, see | ||
| Documentation/ABI/testing/sysfs-bus-typec, and use file | ||
| /sys/bus/typec/devices/.../active). | ||
|
|
||
| What: /sys/bus/typec/devices/.../displayport/pin_assignment | ||
| Date: July 2018 | ||
| Contact: Heikki Krogerus <heikki.krogerus@linux.intel.com> | ||
| Description: | ||
| VESA DisplayPort Alt Mode on USB Type-C Standard defines six | ||
| different pin assignments for USB Type-C connector that are | ||
| labeled A, B, C, D, E, and F. The supported pin assignments are | ||
| listed as space separated list with the active one wrapped in | ||
| square brackets. | ||
|
|
||
| Example: | ||
|
|
||
| C [D] | ||
|
|
||
| Pin assignment can be changed by writing to the file. It is | ||
| possible to set pin assignment before configuration has been | ||
| set, but the assignment will not be active before the | ||
| connector is actually configured. | ||
|
|
||
| Note. As of VESA DisplayPort Alt Mode on USB Type-C Standard | ||
| version 1.0b, pin assignments A, B, and F are deprecated. Only | ||
| pin assignment D can now carry simultaneously one channel of | ||
| USB SuperSpeed protocol. From user perspective pin assignments C | ||
| and E are equal, where all channels on the connector are used | ||
| for carrying DisplayPort protocol (allowing higher resolutions). |
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.