Tomas Winkler | 602214d | 2014-06-23 15:10:36 +0300 | [diff] [blame] | 1 | What: /sys/class/mei/ |
| 2 | Date: May 2014 |
| 3 | KernelVersion: 3.17 |
| 4 | Contact: Tomas Winkler <tomas.winkler@intel.com> |
| 5 | Description: |
| 6 | The mei/ class sub-directory belongs to mei device class |
| 7 | |
| 8 | |
| 9 | What: /sys/class/mei/meiN/ |
| 10 | Date: May 2014 |
| 11 | KernelVersion: 3.17 |
| 12 | Contact: Tomas Winkler <tomas.winkler@intel.com> |
| 13 | Description: |
| 14 | The /sys/class/mei/meiN directory is created for |
| 15 | each probed mei device |
| 16 | |
Tomas Winkler | 7e4a90c | 2014-12-19 00:44:59 +0200 | [diff] [blame] | 17 | What: /sys/class/mei/meiN/fw_status |
| 18 | Date: Nov 2014 |
| 19 | KernelVersion: 3.19 |
| 20 | Contact: Tomas Winkler <tomas.winkler@intel.com> |
| 21 | Description: Display fw status registers content |
| 22 | |
| 23 | The ME FW writes its status information into fw status |
| 24 | registers for BIOS and OS to monitor fw health. |
| 25 | |
| 26 | The register contains running state, power management |
| 27 | state, error codes, and others. The way the registers |
| 28 | are decoded depends on PCH or SoC generation. |
| 29 | Also number of registers varies between 1 and 6 |
| 30 | depending on generation. |
| 31 | |
Alexander Usyskin | 88d1bec | 2016-10-30 01:42:18 +0200 | [diff] [blame] | 32 | What: /sys/class/mei/meiN/hbm_ver |
| 33 | Date: Aug 2016 |
| 34 | KernelVersion: 4.9 |
| 35 | Contact: Tomas Winkler <tomas.winkler@intel.com> |
| 36 | Description: Display the negotiated HBM protocol version. |
| 37 | |
| 38 | The HBM protocol version negotiated |
| 39 | between the driver and the device. |
| 40 | |
| 41 | What: /sys/class/mei/meiN/hbm_ver_drv |
| 42 | Date: Aug 2016 |
| 43 | KernelVersion: 4.9 |
| 44 | Contact: Tomas Winkler <tomas.winkler@intel.com> |
| 45 | Description: Display the driver HBM protocol version. |
| 46 | |
| 47 | The HBM protocol version supported by the driver. |
Alexander Usyskin | af336ca | 2018-02-25 20:07:05 +0200 | [diff] [blame] | 48 | |
| 49 | What: /sys/class/mei/meiN/tx_queue_limit |
| 50 | Date: Jan 2018 |
| 51 | KernelVersion: 4.16 |
| 52 | Contact: Tomas Winkler <tomas.winkler@intel.com> |
| 53 | Description: Configure tx queue limit |
| 54 | |
| 55 | Set maximal number of pending writes |
| 56 | per opened session. |
Alexander Usyskin | 3cfaeb3 | 2018-06-25 00:11:41 +0300 | [diff] [blame] | 57 | |
| 58 | What: /sys/class/mei/meiN/fw_ver |
| 59 | Date: May 2018 |
| 60 | KernelVersion: 4.18 |
| 61 | Contact: Tomas Winkler <tomas.winkler@intel.com> |
| 62 | Description: Display the ME firmware version. |
| 63 | |
| 64 | The version of the platform ME firmware is in format: |
| 65 | <platform>:<major>.<minor>.<milestone>.<build_no>. |
| 66 | There can be up to three such blocks for different |
| 67 | FW components. |
Alexander Usyskin | 43b8a7e | 2019-04-22 09:51:07 +0300 | [diff] [blame] | 68 | |
| 69 | What: /sys/class/mei/meiN/dev_state |
| 70 | Date: Mar 2019 |
| 71 | KernelVersion: 5.1 |
| 72 | Contact: Tomas Winkler <tomas.winkler@intel.com> |
| 73 | Description: Display the ME device state. |
| 74 | |
| 75 | The device state can have following values: |
| 76 | INITIALIZING |
| 77 | INIT_CLIENTS |
| 78 | ENABLED |
| 79 | RESETTING |
| 80 | DISABLED |
| 81 | POWER_DOWN |
| 82 | POWER_UP |
Alexander Usyskin | 52f6efd | 2019-11-07 12:44:45 +0200 | [diff] [blame] | 83 | |
| 84 | What: /sys/class/mei/meiN/trc |
| 85 | Date: Nov 2019 |
| 86 | KernelVersion: 5.5 |
| 87 | Contact: Tomas Winkler <tomas.winkler@intel.com> |
| 88 | Description: Display trc status register content |
| 89 | |
| 90 | The ME FW writes Glitch Detection HW (TRC) |
| 91 | status information into trc status register |
| 92 | for BIOS and OS to monitor fw health. |
Alexander Usyskin | 2f79d3d | 2020-07-28 22:22:42 +0300 | [diff] [blame] | 93 | |
| 94 | What: /sys/class/mei/meiN/kind |
| 95 | Date: Jul 2020 |
| 96 | KernelVersion: 5.8 |
| 97 | Contact: Tomas Winkler <tomas.winkler@intel.com> |
| 98 | Description: Display kind of the device |
| 99 | |
| 100 | Generic devices are marked as "mei" |
| 101 | while special purpose have their own |
| 102 | names. |
| 103 | Available options: |
| 104 | - mei: generic mei device. |
| 105 | - itouch: itouch (ipts) mei device. |