From: Jonathan Cameron <jic23@kernel.org>
To: Matt Ranostay <matt.ranostay@konsulko.com>
Cc: Matt Ranostay <matt@ranostay.consulting>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] devicetree: add documentation for MAX30102 oximeter
Date: Sat, 28 Jan 2017 11:42:18 +0000 [thread overview]
Message-ID: <3ed1a40d-20ae-575d-788c-0665c99de3de@kernel.org> (raw)
In-Reply-To: <CAJCx=gni77DOZQM3Ynmnd_TDgyQ3z5CGMgmQNomowj7k+_SCMA@mail.gmail.com>
On 24/01/17 22:16, Matt Ranostay wrote:
> On Sun, Jan 22, 2017 at 4:22 AM, Jonathan Cameron <jic23@kernel.org> wrote:
>> On 20/01/17 05:40, Matt Ranostay wrote:
>>> Cc: devicetree@vger.kernel.org
>>> Signed-off-by: Matt Ranostay <matt@ranostay.consulting>
>>> ---
>>> .../devicetree/bindings/iio/health/max30102.txt | 30 ++++++++++++++++++++++
>>> 1 file changed, 30 insertions(+)
>>> create mode 100644 Documentation/devicetree/bindings/iio/health/max30102.txt
>>>
>>> diff --git a/Documentation/devicetree/bindings/iio/health/max30102.txt b/Documentation/devicetree/bindings/iio/health/max30102.txt
>>> new file mode 100644
>>> index 000000000000..c93d1bb25597
>>> --- /dev/null
>>> +++ b/Documentation/devicetree/bindings/iio/health/max30102.txt
>>> @@ -0,0 +1,30 @@
>>> +Maxim MAX30102 heart rate and pulse oximeter sensor
>>> +
>>> +* https://datasheets.maximintegrated.com/en/ds/MAX30102.pdf
>>> +
>>> +Required properties:
>>> + - compatible: must be "maxim,max30102"
>>> + - reg: the I2C address of the sensor
>>> + - interrupt-parent: should be the phandle for the interrupt controller
>>> + - interrupts: the sole interrupt generated by the device
>>> +
>>> + Refer to interrupt-controller/interrupts.txt for generic
>>> + interrupt client node bindings.
>>> +
>>> +Optional properties:
>>> + - maxim,red-led-current-microamp: configuration for RED LED current
>>> + - maxim,ir-led-current-microamp: configuration for IR LED current
>>> +
>>> + Note that each step is approximately 200 microamps, ranging from 0 uA to
>>> + 50800 uA.
>> Are these due to the hardware present, or are we looking at something that should
>> be controllable from userspace?
>
> Generally you'd set this value based on the hardware application it is
> being used for.. namely if you had a plastic case or wristband that is
> affecting the signal..
Fair enough.
>
>>> +
>>> +Example:
>>> +
>>> +max30100@57 {
>>> + compatible = "maxim,max30102";
>>> + reg = <57>;
>>> + maxim,red-led-current-microamp = <7000>;
>>> + maxim,ir-led-current-microamp = <7000>;
>>> + interrupt-parent = <&gpio1>;
>>> + interrupts = <16 2>;
>>> +};
>>>
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-01-28 11:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 5:40 [PATCH 0/2] iio: health: add MAX30102 oximeter driver support Matt Ranostay
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 [this message]
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=3ed1a40d-20ae-575d-788c-0665c99de3de@kernel.org \
--to=jic23@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=matt.ranostay@konsulko.com \
--cc=matt@ranostay.consulting \
/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).