aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/misc-devices/mei/mei-client-bus.txt
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/misc-devices/mei/mei-client-bus.txt')
-rw-r--r--Documentation/misc-devices/mei/mei-client-bus.txt7
1 files changed, 5 insertions, 2 deletions
diff --git a/Documentation/misc-devices/mei/mei-client-bus.txt b/Documentation/misc-devices/mei/mei-client-bus.txt
index f83910a8ce76..6ca486bd0d14 100644
--- a/Documentation/misc-devices/mei/mei-client-bus.txt
+++ b/Documentation/misc-devices/mei/mei-client-bus.txt
@@ -1,9 +1,10 @@
1Intel(R) Management Engine (ME) Client bus API 1Intel(R) Management Engine (ME) Client bus API
2=============================================== 2==============================================
3 3
4 4
5Rationale 5Rationale
6========= 6=========
7
7MEI misc character device is useful for dedicated applications to send and receive 8MEI misc character device is useful for dedicated applications to send and receive
8data to the many FW appliance found in Intel's ME from the user space. 9data to the many FW appliance found in Intel's ME from the user space.
9However for some of the ME functionalities it make sense to leverage existing software 10However for some of the ME functionalities it make sense to leverage existing software
@@ -17,7 +18,8 @@ the existing code.
17 18
18 19
19MEI CL bus API 20MEI CL bus API
20=========== 21==============
22
21A driver implementation for an MEI Client is very similar to existing bus 23A driver implementation for an MEI Client is very similar to existing bus
22based device drivers. The driver registers itself as an MEI CL bus driver through 24based device drivers. The driver registers itself as an MEI CL bus driver through
23the mei_cl_driver structure: 25the mei_cl_driver structure:
@@ -55,6 +57,7 @@ received buffers.
55 57
56Example 58Example
57======= 59=======
60
58As a theoretical example let's pretend the ME comes with a "contact" NFC IP. 61As a theoretical example let's pretend the ME comes with a "contact" NFC IP.
59The driver init and exit routines for this device would look like: 62The driver init and exit routines for this device would look like:
60 63