diff options
author | Tomas Winkler <tomas.winkler@intel.com> | 2012-05-29 09:39:09 -0400 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2012-06-13 16:38:25 -0400 |
commit | f6a4e494e059b7f0e361dba28f0e2d13144da1d1 (patch) | |
tree | 447094b179469adb764f370dc81177bf19b2811f /Documentation/misc-devices | |
parent | cfaf025112d3856637ff34a767ef785ef5cf2ca9 (diff) |
mei: mei.txt: minor grammar fixes
Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'Documentation/misc-devices')
-rw-r--r-- | Documentation/misc-devices/mei/mei.txt | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/Documentation/misc-devices/mei/mei.txt b/Documentation/misc-devices/mei/mei.txt index 2785697da59d..6ec702950719 100644 --- a/Documentation/misc-devices/mei/mei.txt +++ b/Documentation/misc-devices/mei/mei.txt | |||
@@ -50,25 +50,25 @@ Intel MEI Driver | |||
50 | The driver exposes a misc device called /dev/mei. | 50 | The driver exposes a misc device called /dev/mei. |
51 | 51 | ||
52 | An application maintains communication with an Intel ME feature while | 52 | An application maintains communication with an Intel ME feature while |
53 | /dev/mei is open. The binding to a specific features is performed by calling | 53 | /dev/mei is open. The binding to a specific feature is performed by calling |
54 | MEI_CONNECT_CLIENT_IOCTL, which passes the desired UUID. | 54 | MEI_CONNECT_CLIENT_IOCTL, which passes the desired UUID. |
55 | The number of instances of an Intel ME feature that can be opened | 55 | The number of instances of an Intel ME feature that can be opened |
56 | at the same time depends on the Intel ME feature, but most of the | 56 | at the same time depends on the Intel ME feature, but most of the |
57 | features allow only a single instance. | 57 | features allow only a single instance. |
58 | 58 | ||
59 | The Intel AMT Host Interface (Intel AMTHI) feature supports multiple | 59 | The Intel AMT Host Interface (Intel AMTHI) feature supports multiple |
60 | simultaneous user applications. Therefore, the Intel MEI driver handles | 60 | simultaneous user connected applications. The Intel MEI driver |
61 | this internally by maintaining request queues for the applications. | 61 | handles this internally by maintaining request queues for the applications. |
62 | 62 | ||
63 | The driver is oblivious to data that is passed between firmware feature | 63 | The driver is transparent to data that are passed between firmware feature |
64 | and host application. | 64 | and host application. |
65 | 65 | ||
66 | Because some of the Intel ME features can change the system | 66 | Because some of the Intel ME features can change the system |
67 | configuration, the driver by default allows only a privileged | 67 | configuration, the driver by default allows only a privileged |
68 | user to access it. | 68 | user to access it. |
69 | 69 | ||
70 | A code snippet for an application communicating with | 70 | A code snippet for an application communicating with Intel AMTHI client: |
71 | Intel AMTHI client: | 71 | |
72 | struct mei_connect_client_data data; | 72 | struct mei_connect_client_data data; |
73 | fd = open(MEI_DEVICE); | 73 | fd = open(MEI_DEVICE); |
74 | 74 | ||
@@ -185,7 +185,7 @@ The Intel AMT Watchdog is composed of two parts: | |||
185 | 2) Intel MEI driver - connects to the watchdog feature, configures the | 185 | 2) Intel MEI driver - connects to the watchdog feature, configures the |
186 | watchdog and sends the heartbeats. | 186 | watchdog and sends the heartbeats. |
187 | 187 | ||
188 | The Intel MEI driver uses the kernel watchdog to configure the Intel AMT | 188 | The Intel MEI driver uses the kernel watchdog API to configure the Intel AMT |
189 | Watchdog and to send heartbeats to it. The default timeout of the | 189 | Watchdog and to send heartbeats to it. The default timeout of the |
190 | watchdog is 120 seconds. | 190 | watchdog is 120 seconds. |
191 | 191 | ||