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 V4 0/2] staging: iio: add isl29028 driver
Date: Thu, 12 Apr 2012 19:31:04 +0530 [thread overview]
Message-ID: <1334239266-29505-1-git-send-email-ldewangan@nvidia.com> (raw)
ISL29028 is concurrent Ambient light and proximity sensor
from intersil.
Adding driver for supporting this device.
Changes from V1:
- Taken care of cleanups comments.
Changes from V2:
- Implement the sampling frequency selection per channel wise.
- Remove documentation change as it is already there.
- Use the channel info for selecting proximity sampling rather than
exposing new sysfs from driver.
Changes from V3:
- change samp_freq to sampling_frequency
- Remove sysfs range and add scale through channel info.
Laxman Dewangan (2):
staging: iio: add channel info for sampling frequency
staging: iio: add driver for isl29028
drivers/staging/iio/iio.h | 5 +
drivers/staging/iio/industrialio-core.c | 1 +
drivers/staging/iio/light/Kconfig | 10 +
drivers/staging/iio/light/Makefile | 1 +
drivers/staging/iio/light/isl29028.c | 563 +++++++++++++++++++++++++++++++
5 files changed, 580 insertions(+), 0 deletions(-)
create mode 100644 drivers/staging/iio/light/isl29028.c
next reply other threads:[~2012-04-12 14:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 14:01 Laxman Dewangan [this message]
2012-04-12 14:01 ` [PATCH V4 1/2] staging: iio: add channel info for sampling frequency Laxman Dewangan
2012-04-12 14:27 ` Jonathan Cameron
2012-04-12 14:01 ` [PATCH V4 2/2] staging: iio: add driver for isl29028 Laxman Dewangan
2012-04-12 14:34 ` Jonathan Cameron
2012-04-13 9:48 ` Laxman Dewangan
2012-04-13 10:05 ` Jonathan Cameron
2012-04-13 9:49 ` Laxman Dewangan
2012-04-12 15:36 ` Stephen Warren
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=1334239266-29505-1-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
Powered by JetHome