From: Tomas Winkler <tomas.winkler@intel.com>
To: gregkh@linuxfoundation.org
Cc: arnd@arndb.de, linux-kernel@vger.kernel.org,
Tomas Winkler <tomas.winkler@intel.com>
Subject: [char-misc-next 1/3 V2] mei: add ABI documentation for fw_status exported through sysfs
Date: Thu, 27 Nov 2014 14:07:27 +0200 [thread overview]
Message-ID: <1417090049-23219-1-git-send-email-tomas.winkler@intel.com> (raw)
Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
---
V2: rephrase the description
Documentation/ABI/testing/sysfs-class-mei | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff --git a/Documentation/ABI/testing/sysfs-class-mei b/Documentation/ABI/testing/sysfs-class-mei
index 0ec8b8178c41..4eb1379b976c 100644
--- a/Documentation/ABI/testing/sysfs-class-mei
+++ b/Documentation/ABI/testing/sysfs-class-mei
@@ -14,3 +14,18 @@ Description:
The /sys/class/mei/meiN directory is created for
each probed mei device
+What: /sys/class/mei/meiN/fw_status
+Date: Nov 2014
+KernelVersion: 3.19
+Contact: Tomas Winkler <tomas.winkler@intel.com>
+Description: Display fw status registers content
+
+ The ME FW writes its status information into fw status
+ registers for BIOS and OS to monitor fw health.
+
+ The register contains running state, power management
+ state, error codes, and others. The way the registers
+ are decoded depends on PCH or SoC generation.
+ Also number of registers varies between 1 and 6
+ depending on generation.
+
--
1.9.3
next reply other threads:[~2014-11-27 12:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 12:07 Tomas Winkler [this message]
2014-11-27 12:07 ` [char-misc-next 2/3 V2] mei: bus: use ssize_t as the return type for send and receive Tomas Winkler
2014-11-27 12:07 ` [char-misc-next 3/3 V2] mei: add reference counting for me clients Tomas Winkler
2015-01-09 22:51 ` Greg KH
2015-01-10 22:01 ` Winkler, Tomas
2014-12-18 9:37 ` [char-misc-next 1/3 V2] mei: add ABI documentation for fw_status exported through sysfs Winkler, Tomas
2014-12-18 22:15 ` gregkh
2014-12-18 22:46 ` Winkler, Tomas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1417090049-23219-1-git-send-email-tomas.winkler@intel.com \
--to=tomas.winkler@intel.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox