From: Matt Ranostay <matt@ranostay.consulting>
To: jic23@kernel.org
Cc: linux-iio@vger.kernel.org, Matt Ranostay <matt@ranostay.consulting>
Subject: [PATCH 0/2] iio: health: add MAX30102 oximeter driver support
Date: Thu, 19 Jan 2017 21:40:58 -0800 [thread overview]
Message-ID: <20170120054100.902-1-matt@ranostay.consulting> (raw)
Add support for the MAX30102 oximeter unit. This driver is heavily based on
the previous MAX30100 driver but has much more functionality that prevents a
common core which includes but not limited to:
* sample averaging
* bigger FIFO
* much different register mapping
* more fine tuned LED current settings
Important Note: ADC data from both IR + RED has been confirmed to be valid but
hasn't been plotted on a graph yet.
Matt Ranostay (2):
devicetree: add documentation for MAX30102
iio: health: add MAX30102 oximeter driver support
.../devicetree/bindings/iio/health/max30102.txt | 30 ++
drivers/iio/health/Kconfig | 13 +
drivers/iio/health/Makefile | 1 +
drivers/iio/health/max30102.c | 478 +++++++++++++++++++++
4 files changed, 522 insertions(+)
create mode 100644 Documentation/devicetree/bindings/iio/health/max30102.txt
create mode 100644 drivers/iio/health/max30102.c
--
2.10.2
next reply other threads:[~2017-01-20 5:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 5:40 Matt Ranostay [this message]
2017-01-20 5:40 ` [PATCH 1/2] devicetree: add documentation for MAX30102 oximeter Matt Ranostay
2017-01-22 12:22 ` Jonathan Cameron
2017-01-24 22:16 ` Matt Ranostay
2017-01-28 11:42 ` Jonathan Cameron
2017-01-20 5:41 ` [PATCH 2/2] iio: health: add MAX30102 oximeter driver support Matt Ranostay
2017-01-22 9:00 ` Peter Meerwald-Stadler
2017-01-22 12:21 ` Jonathan Cameron
2017-01-22 21:30 ` Matt Ranostay
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=20170120054100.902-1-matt@ranostay.consulting \
--to=matt@ranostay.consulting \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
/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).