From: Laxman Dewangan <ldewangan@nvidia.com>
To: jic23@cam.ac.uk, gregkh@linuxfoundation.org,
grant.likely@secretlab.ca, rob.herring@calxeda.com,
jbrenner@taosinc.com, rklein@nvidia.com, max@stro.at
Cc: linux-iio@vger.kernel.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org,
Laxman Dewangan <ldewangan@nvidia.com>
Subject: [PATCH V1 2/2] staging: Documentation: add proximity_sampling_period as sysfs details
Date: Wed, 11 Apr 2012 22:58:04 +0530 [thread overview]
Message-ID: <1334165284-11326-3-git-send-email-ldewangan@nvidia.com> (raw)
In-Reply-To: <1334165284-11326-1-git-send-email-ldewangan@nvidia.com>
Add the sysfs proximity_sampling_period for sampling period of
proximity sensing.
Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
---
.../staging/iio/Documentation/sysfs-bus-iio-light | 7 +++++++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/drivers/staging/iio/Documentation/sysfs-bus-iio-light b/drivers/staging/iio/Documentation/sysfs-bus-iio-light
index edbf470..9d6108b 100644
--- a/drivers/staging/iio/Documentation/sysfs-bus-iio-light
+++ b/drivers/staging/iio/Documentation/sysfs-bus-iio-light
@@ -83,3 +83,10 @@ Description:
Hardware or software applied calibration scale factor assumed
to account for attenuation due to industrial design (glass
filters or aperture holes).
+
+What: /sys/bus/iio/devices/device[n]/proximity_sampling_period
+KernelVersion: 3.5
+Contact: linux-iio@vger.kernel.org
+Description:
+ Hardware dependent mode for proximity sensor device to set/get
+ the sampling rate of proximity sensing and conversion.
--
1.7.1.1
prev parent reply other threads:[~2012-04-11 17:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 17:28 [PATCH V1 0/2] staging: iio: add isl29028 driver Laxman Dewangan
2012-04-11 17:28 ` [PATCH V1 1/2] staging: iio: add driver for isl29028 Laxman Dewangan
2012-04-11 19:55 ` Dan Carpenter
2012-04-11 17:28 ` Laxman Dewangan [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1334165284-11326-3-git-send-email-ldewangan@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=devel@driverdev.osuosl.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=gregkh@linuxfoundation.org \
--cc=jbrenner@taosinc.com \
--cc=jic23@cam.ac.uk \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=max@stro.at \
--cc=rklein@nvidia.com \
--cc=rob.herring@calxeda.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).