From: Daniel Baluta <daniel.baluta@intel.com>
To: sathyanarayanan.kuppuswamy@linux.intel.com, jic23@kernel.org
Cc: pmeerw@pmeerw.net, linux-iio@vger.kernel.org,
srinivas.pandruvada@linux.intel.com, daniel.baluta@intel.com
Subject: [PATCH v8 0/2] Add support for LTR-301 and LTR-559 sensors
Date: Tue, 21 Apr 2015 19:10:58 +0300 [thread overview]
Message-ID: <1429632660-8716-1-git-send-email-daniel.baluta@intel.com> (raw)
This patchset adds support for LiteOn LTR301 ambient light sensor
and LTR559 ambient light and proximity sensor.
I will just leave this here if Sathya needs to push support for LTR-301.
Minimal tested. I will be back in few days with more testing.
v8:
1. Rebased on the latest linux-iio testing branch.
v7:
1. Rebase LTR-301 on top of LTR-559 and merged the patches into a single patchset
2. Moved ltr501_chip_info_tbl below ltr501_info in patch 1 in order
to make patch 2 changes look natural. :)
3. Moved "else" branch of id check from patch 2 to patch 1. Now it is no
longer possible to have a NULL name after this check. If id is not NULL
than id->name is one of ltr501_id already defined strings.
v6:
1. Changed the title in commit log
v5:
1. Rebased this patch on top of Daniel's LTR559 patchset
(http://marc.info/?l=linux-kernel&m=142779827617036&w=2)
2. Added info and channel members to chip_info struture.
v4:
1. Addressed minor comments from Peter Meerwald
2. Changed invalid chip id errno from ENOSYS to ENODEV
3. Fixed channel id index number
4. Removed unused variable.
v3:
1. Sent v2 before by mistake. So sending the final version of v2 as v3.
v2:
1. Handled device id NULL case in probe
2. Changed pr_warn to dev_warn
v1:
Extended LTR501 driver to support both LTR301 and LTR501 device.
Daniel Baluta (2):
iio: ltr501: Add support for ltr559 chip
iio: ltr501: Add support for ltr301 chip
drivers/iio/light/Kconfig | 3 +-
drivers/iio/light/ltr501.c | 290 +++++++++++++++++++++++++++++++++++++++------
2 files changed, 256 insertions(+), 37 deletions(-)
--
1.9.1
next reply other threads:[~2015-04-21 16:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 16:10 Daniel Baluta [this message]
2015-04-21 16:10 ` [PATCH v8 1/2] iio: ltr501: Add support for ltr559 chip Daniel Baluta
2015-04-26 15:55 ` Jonathan Cameron
2015-04-21 16:11 ` [PATCH v8 2/2] iio: ltr501: Add support for ltr301 chip Daniel Baluta
2015-04-21 16:23 ` Kuppuswamy Sathyanarayanan
2015-04-21 16:27 ` Daniel Baluta
2015-04-21 17:26 ` Kuppuswamy Sathyanarayanan
2015-04-21 17:55 ` Jonathan Cameron
2015-04-26 7:18 ` Sathyanarayanan Kuppuswamy
2015-04-26 15:56 ` Jonathan Cameron
2015-04-21 16:24 ` [PATCH v8 0/2] Add support for LTR-301 and LTR-559 sensors Kuppuswamy Sathyanarayanan
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=1429632660-8716-1-git-send-email-daniel.baluta@intel.com \
--to=daniel.baluta@intel.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=srinivas.pandruvada@linux.intel.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