summaryrefslogtreecommitdiffstats
path: root/kernel/Documentation/misc-devices
diff options
context:
space:
mode:
Diffstat (limited to 'kernel/Documentation/misc-devices')
-rw-r--r--kernel/Documentation/misc-devices/apds990x.txt2
-rw-r--r--kernel/Documentation/misc-devices/isl290032
-rw-r--r--kernel/Documentation/misc-devices/max68752
-rw-r--r--kernel/Documentation/misc-devices/mei/mei.txt45
-rw-r--r--kernel/Documentation/misc-devices/spear-pcie-gadget.txt2
5 files changed, 48 insertions, 5 deletions
diff --git a/kernel/Documentation/misc-devices/apds990x.txt b/kernel/Documentation/misc-devices/apds990x.txt
index d5408cade..454d95d62 100644
--- a/kernel/Documentation/misc-devices/apds990x.txt
+++ b/kernel/Documentation/misc-devices/apds990x.txt
@@ -30,7 +30,7 @@ lead to false interrupt, but that doesn't harm.
ALS contains 4 different gain steps. Driver automatically
selects suitable gain step. After each measurement, reliability of the results
-is estimated and new measurement is trigged if necessary.
+is estimated and new measurement is triggered if necessary.
Platform data can provide tuned values to the conversion formulas if
values are known. Otherwise plain sensor default values are used.
diff --git a/kernel/Documentation/misc-devices/isl29003 b/kernel/Documentation/misc-devices/isl29003
index c4ff5f38e..80b952fd3 100644
--- a/kernel/Documentation/misc-devices/isl29003
+++ b/kernel/Documentation/misc-devices/isl29003
@@ -29,7 +29,7 @@ Detection
The ISL29003 does not have an ID register which could be used to identify
it, so the detection routine will just try to read from the configured I2C
-addess and consider the device to be present as soon as it ACKs the
+address and consider the device to be present as soon as it ACKs the
transfer.
diff --git a/kernel/Documentation/misc-devices/max6875 b/kernel/Documentation/misc-devices/max6875
index 1e89ee3cc..2f2bd0b17 100644
--- a/kernel/Documentation/misc-devices/max6875
+++ b/kernel/Documentation/misc-devices/max6875
@@ -22,7 +22,7 @@ At reset, the MAX6875 reads the configuration EEPROM into its configuration
registers. The chip then begins to operate according to the values in the
registers.
-The Maxim MAX6874 is a similar, mostly compatible device, with more intputs
+The Maxim MAX6874 is a similar, mostly compatible device, with more inputs
and outputs:
vin gpi vout
MAX6874 6 4 8
diff --git a/kernel/Documentation/misc-devices/mei/mei.txt b/kernel/Documentation/misc-devices/mei/mei.txt
index 8d47501bb..91c1fa34f 100644
--- a/kernel/Documentation/misc-devices/mei/mei.txt
+++ b/kernel/Documentation/misc-devices/mei/mei.txt
@@ -96,7 +96,7 @@ A code snippet for an application communicating with Intel AMTHI client:
IOCTL
=====
-The Intel MEI Driver supports the following IOCTL command:
+The Intel MEI Driver supports the following IOCTL commands:
IOCTL_MEI_CONNECT_CLIENT Connect to firmware Feature (client).
usage:
@@ -125,6 +125,49 @@ The Intel MEI Driver supports the following IOCTL command:
data that can be sent or received. (e.g. if MTU=2K, can send
requests up to bytes 2k and received responses up to 2k bytes).
+ IOCTL_MEI_NOTIFY_SET: enable or disable event notifications
+
+ Usage:
+ uint32_t enable;
+ ioctl(fd, IOCTL_MEI_NOTIFY_SET, &enable);
+
+ Inputs:
+ uint32_t enable = 1;
+ or
+ uint32_t enable[disable] = 0;
+
+ Error returns:
+ EINVAL Wrong IOCTL Number
+ ENODEV Device is not initialized or the client not connected
+ ENOMEM Unable to allocate memory to client internal data.
+ EFAULT Fatal Error (e.g. Unable to access user input data)
+ EOPNOTSUPP if the device doesn't support the feature
+
+ Notes:
+ The client must be connected in order to enable notification events
+
+
+ IOCTL_MEI_NOTIFY_GET : retrieve event
+
+ Usage:
+ uint32_t event;
+ ioctl(fd, IOCTL_MEI_NOTIFY_GET, &event);
+
+ Outputs:
+ 1 - if an event is pending
+ 0 - if there is no even pending
+
+ Error returns:
+ EINVAL Wrong IOCTL Number
+ ENODEV Device is not initialized or the client not connected
+ ENOMEM Unable to allocate memory to client internal data.
+ EFAULT Fatal Error (e.g. Unable to access user input data)
+ EOPNOTSUPP if the device doesn't support the feature
+
+ Notes:
+ The client must be connected and event notification has to be enabled
+ in order to receive an event
+
Intel ME Applications
=====================
diff --git a/kernel/Documentation/misc-devices/spear-pcie-gadget.txt b/kernel/Documentation/misc-devices/spear-pcie-gadget.txt
index 02c13ef5e..89b88dee4 100644
--- a/kernel/Documentation/misc-devices/spear-pcie-gadget.txt
+++ b/kernel/Documentation/misc-devices/spear-pcie-gadget.txt
@@ -2,7 +2,7 @@ Spear PCIe Gadget Driver:
Author
=============
-Pratyush Anand (pratyush.anand@st.com)
+Pratyush Anand (pratyush.anand@gmail.com)
Location
============