kpriv/linux-hardened
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Staging: iio: Fix typos in documentation

Browse source 
Spell-check wouln't catch these :)

Signed-off-by: Amit Kucheria <amit.kucheria@verdurent.com>
Acked-by: Jonathan Cameron <jic23@cam.ac.uk>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
This commit is contained in:
Amit Kucheria 2009-11-09 15:10:15 +02:00 committed by Greg Kroah-Hartman
parent 727acb4fb2
commit 51bf00aef0
2 changed files with 7 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
drivers/staging/iio/Documentation/device.txt
View file

@ -10,7 +10,7 @@ First allocate one using:
struct iio_dev *indio_dev = iio_allocate_device();
The fill in the following.
Then fill in the following:
indio_dev->dev.parent
the struct device associated with the underlying hardware.
@ -45,5 +45,5 @@ allocated prior to registering the device with the iio-core, but must
be registered afterwards (otherwise the whole parentage of devices
gets confused)
On remove iio_device_unregister(indio_dev) will remove the device from
On remove, iio_device_unregister(indio_dev) will remove the device from
the core, and iio_free_device will clean up.

9
drivers/staging/iio/Documentation/overview.txt
View file

@ -24,11 +24,12 @@ hwmon with simple polled access to device channels via sysfs.
* Event chrdevs. These are similar to input in that they provide a
route to user space for hardware triggered events. Such events include
threshold detectors, free-fall detectors and more complex action
detection. They events themselves are currently very simple with
detection. The events themselves are currently very simple with
merely an event code and a timestamp. Any data associated with the
event must be accessed via polling. Note a given device may have one
or more event channel. These events are turned on or off (if possible)
via sysfs interfaces.
event must be accessed via polling.
Note: A given device may have one or more event channel. These events are
turned on or off (if possible) via sysfs interfaces.
* Hardware ring buffer support. Some recent sensors have included
fifo / ring buffers on the sensor chip. These greatly reduce the load