forked from torvalds/linux
-
Notifications
You must be signed in to change notification settings - Fork 131
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 #970 from plbossart/merge/broonie-next-20190521
Merge/broonie next 20190521
- Loading branch information
Showing
11,729 changed files
with
542,474 additions
and
361,109 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 |
|---|---|---|
| @@ -1 +1,2 @@ | ||
| Christoph Hellwig <[email protected]> | ||
| Marc Gonzalez <[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
2 changes: 2 additions & 0 deletions
2
...on/ABI/testing/sysfs-class-net-batman-adv → ...n/ABI/obsolete/sysfs-class-net-batman-adv
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
2 changes: 2 additions & 0 deletions
2
...entation/ABI/testing/sysfs-class-net-mesh → ...ntation/ABI/obsolete/sysfs-class-net-mesh
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
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 |
|---|---|---|
|
|
@@ -81,7 +81,9 @@ What: /sys/bus/vmbus/devices/<UUID>/channels/<N>/latency | |
| Date: September. 2017 | ||
| KernelVersion: 4.14 | ||
| Contact: Stephen Hemminger <[email protected]> | ||
| Description: Channel signaling latency | ||
| Description: Channel signaling latency. This file is available only for | ||
| performance critical channels (storage, network, etc.) that use | ||
| the monitor page mechanism. | ||
| Users: Debugging tools | ||
|
|
||
| What: /sys/bus/vmbus/devices/<UUID>/channels/<N>/out_mask | ||
|
|
@@ -95,7 +97,9 @@ What: /sys/bus/vmbus/devices/<UUID>/channels/<N>/pending | |
| Date: September. 2017 | ||
| KernelVersion: 4.14 | ||
| Contact: Stephen Hemminger <[email protected]> | ||
| Description: Channel interrupt pending state | ||
| Description: Channel interrupt pending state. This file is available only for | ||
| performance critical channels (storage, network, etc.) that use | ||
| the monitor page mechanism. | ||
| Users: Debugging tools | ||
|
|
||
| What: /sys/bus/vmbus/devices/<UUID>/channels/<N>/read_avail | ||
|
|
@@ -137,7 +141,9 @@ What: /sys/bus/vmbus/devices/<UUID>/channels/<N>/monitor_id | |
| Date: January. 2018 | ||
| KernelVersion: 4.16 | ||
| Contact: Stephen Hemminger <[email protected]> | ||
| Description: Monitor bit associated with channel | ||
| Description: Monitor bit associated with channel. This file is available only | ||
| for performance critical channels (storage, network, etc.) that | ||
| use the monitor page mechanism. | ||
| Users: Debugging tools and userspace drivers | ||
|
|
||
| What: /sys/bus/vmbus/devices/<UUID>/channels/<N>/ring | ||
|
|
||
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 |
|---|---|---|
|
|
@@ -90,4 +90,89 @@ Date: December 2009 | |
| Contact: Lee Schermerhorn <[email protected]> | ||
| Description: | ||
| The node's huge page size control/query attributes. | ||
| See Documentation/admin-guide/mm/hugetlbpage.rst | ||
| See Documentation/admin-guide/mm/hugetlbpage.rst | ||
|
|
||
| What: /sys/devices/system/node/nodeX/accessY/ | ||
| Date: December 2018 | ||
| Contact: Keith Busch <[email protected]> | ||
| Description: | ||
| The node's relationship to other nodes for access class "Y". | ||
|
|
||
| What: /sys/devices/system/node/nodeX/accessY/initiators/ | ||
| Date: December 2018 | ||
| Contact: Keith Busch <[email protected]> | ||
| Description: | ||
| The directory containing symlinks to memory initiator | ||
| nodes that have class "Y" access to this target node's | ||
| memory. CPUs and other memory initiators in nodes not in | ||
| the list accessing this node's memory may have different | ||
| performance. | ||
|
|
||
| What: /sys/devices/system/node/nodeX/accessY/targets/ | ||
| Date: December 2018 | ||
| Contact: Keith Busch <[email protected]> | ||
| Description: | ||
| The directory containing symlinks to memory targets that | ||
| this initiator node has class "Y" access. | ||
|
|
||
| What: /sys/devices/system/node/nodeX/accessY/initiators/read_bandwidth | ||
| Date: December 2018 | ||
| Contact: Keith Busch <[email protected]> | ||
| Description: | ||
| This node's read bandwidth in MB/s when accessed from | ||
| nodes found in this access class's linked initiators. | ||
|
|
||
| What: /sys/devices/system/node/nodeX/accessY/initiators/read_latency | ||
| Date: December 2018 | ||
| Contact: Keith Busch <[email protected]> | ||
| Description: | ||
| This node's read latency in nanoseconds when accessed | ||
| from nodes found in this access class's linked initiators. | ||
|
|
||
| What: /sys/devices/system/node/nodeX/accessY/initiators/write_bandwidth | ||
| Date: December 2018 | ||
| Contact: Keith Busch <[email protected]> | ||
| Description: | ||
| This node's write bandwidth in MB/s when accessed from | ||
| found in this access class's linked initiators. | ||
|
|
||
| What: /sys/devices/system/node/nodeX/accessY/initiators/write_latency | ||
| Date: December 2018 | ||
| Contact: Keith Busch <[email protected]> | ||
| Description: | ||
| This node's write latency in nanoseconds when access | ||
| from nodes found in this class's linked initiators. | ||
|
|
||
| What: /sys/devices/system/node/nodeX/memory_side_cache/indexY/ | ||
| Date: December 2018 | ||
| Contact: Keith Busch <[email protected]> | ||
| Description: | ||
| The directory containing attributes for the memory-side cache | ||
| level 'Y'. | ||
|
|
||
| What: /sys/devices/system/node/nodeX/memory_side_cache/indexY/indexing | ||
| Date: December 2018 | ||
| Contact: Keith Busch <[email protected]> | ||
| Description: | ||
| The caches associativity indexing: 0 for direct mapped, | ||
| non-zero if indexed. | ||
|
|
||
| What: /sys/devices/system/node/nodeX/memory_side_cache/indexY/line_size | ||
| Date: December 2018 | ||
| Contact: Keith Busch <[email protected]> | ||
| Description: | ||
| The number of bytes accessed from the next cache level on a | ||
| cache miss. | ||
|
|
||
| What: /sys/devices/system/node/nodeX/memory_side_cache/indexY/size | ||
| Date: December 2018 | ||
| Contact: Keith Busch <[email protected]> | ||
| Description: | ||
| The size of this memory side cache in bytes. | ||
|
|
||
| What: /sys/devices/system/node/nodeX/memory_side_cache/indexY/write_policy | ||
| Date: December 2018 | ||
| Contact: Keith Busch <[email protected]> | ||
| Description: | ||
| The cache write policy: 0 for write-back, 1 for write-through, | ||
| other or unknown. | ||
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 |
|---|---|---|
| @@ -1,23 +1,46 @@ | ||
| What: /sys/kernel/debug/wilco_ec/h1_gpio | ||
| Date: April 2019 | ||
| KernelVersion: 5.2 | ||
| Description: | ||
| As part of Chrome OS's FAFT (Fully Automated Firmware Testing) | ||
| tests, we need to ensure that the H1 chip is properly setting | ||
| some GPIO lines. The h1_gpio attribute exposes the state | ||
| of the lines: | ||
| - ENTRY_TO_FACT_MODE in BIT(0) | ||
| - SPI_CHROME_SEL in BIT(1) | ||
|
|
||
| Output will formatted with "0x%02x\n". | ||
|
|
||
| What: /sys/kernel/debug/wilco_ec/raw | ||
| Date: January 2019 | ||
| KernelVersion: 5.1 | ||
| Description: | ||
| Write and read raw mailbox commands to the EC. | ||
|
|
||
| For writing: | ||
| Bytes 0-1 indicate the message type: | ||
| 00 F0 = Execute Legacy Command | ||
| 00 F2 = Read/Write NVRAM Property | ||
| Byte 2 provides the command code | ||
| Bytes 3+ consist of the data passed in the request | ||
| You can write a hexadecimal sentence to raw, and that series of | ||
| bytes will be sent to the EC. Then, you can read the bytes of | ||
| response by reading from raw. | ||
|
|
||
| At least three bytes are required, for the msg type and command, | ||
| with additional bytes optional for additional data. | ||
| For writing, bytes 0-1 indicate the message type, one of enum | ||
| wilco_ec_msg_type. Byte 2+ consist of the data passed in the | ||
| request, starting at MBOX[0] | ||
|
|
||
| At least three bytes are required for writing, two for the type | ||
| and at least a single byte of data. Only the first | ||
| EC_MAILBOX_DATA_SIZE bytes of MBOX will be used. | ||
|
|
||
| Example: | ||
| // Request EC info type 3 (EC firmware build date) | ||
| $ echo 00 f0 38 00 03 00 > raw | ||
| // Corresponds with sending type 0x00f0 with | ||
| // MBOX = [38, 00, 03, 00] | ||
| $ echo 00 f0 38 00 03 00 > /sys/kernel/debug/wilco_ec/raw | ||
| // View the result. The decoded ASCII result "12/21/18" is | ||
| // included after the raw hex. | ||
| $ cat raw | ||
| 00 31 32 2f 32 31 2f 31 38 00 38 00 01 00 2f 00 .12/21/18.8... | ||
| // Corresponds with MBOX = [00, 00, 31, 32, 2f, 32, 31, 38, ...] | ||
| $ cat /sys/kernel/debug/wilco_ec/raw | ||
| 00 00 31 32 2f 32 31 2f 31 38 00 38 00 01 00 2f 00 ..12/21/18.8... | ||
|
|
||
| Note that the first 32 bytes of the received MBOX[] will be | ||
| printed, even if some of the data is junk. It is up to you to | ||
| know how many of the first bytes of data are the actual | ||
| response. |
Oops, something went wrong.