From dde38d00390b6ad01e065686c1a3b69e0885ee71 Mon Sep 17 00:00:00 2001 From: Amit Kucheria Date: Mon, 9 Nov 2009 15:10:15 +0200 Subject: [PATCH] --- yaml --- r: 175230 b: refs/heads/master c: 51bf00aef02d410bf74afb31ec2d5dbcedb1a52f h: refs/heads/master v: v3 --- [refs] | 2 +- trunk/drivers/staging/iio/Documentation/device.txt | 4 ++-- trunk/drivers/staging/iio/Documentation/overview.txt | 9 +++++---- 3 files changed, 8 insertions(+), 7 deletions(-) diff --git a/[refs] b/[refs] index 26643f9ab86f..ea965ec0685d 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: 727acb4fb2143ac7228b9a49f9e2f73f71e748d9 +refs/heads/master: 51bf00aef02d410bf74afb31ec2d5dbcedb1a52f diff --git a/trunk/drivers/staging/iio/Documentation/device.txt b/trunk/drivers/staging/iio/Documentation/device.txt index 6916cd333350..69d9570f29fc 100644 --- a/trunk/drivers/staging/iio/Documentation/device.txt +++ b/trunk/drivers/staging/iio/Documentation/device.txt @@ -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. diff --git a/trunk/drivers/staging/iio/Documentation/overview.txt b/trunk/drivers/staging/iio/Documentation/overview.txt index 64584ad40241..e39dfc1705aa 100644 --- a/trunk/drivers/staging/iio/Documentation/overview.txt +++ b/trunk/drivers/staging/iio/Documentation/overview.txt @@ -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