From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from saturn.retrosnub.co.uk ([178.18.118.26]:39974 "EHLO saturn.retrosnub.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751311AbdAVM3U (ORCPT ); Sun, 22 Jan 2017 07:29:20 -0500 Subject: Re: [PATCH 1/2] devicetree: add documentation for MAX30102 oximeter To: Matt Ranostay References: <20170120054100.902-1-matt@ranostay.consulting> <20170120054100.902-2-matt@ranostay.consulting> Cc: linux-iio@vger.kernel.org, devicetree@vger.kernel.org From: Jonathan Cameron Message-ID: Date: Sun, 22 Jan 2017 12:22:57 +0000 MIME-Version: 1.0 In-Reply-To: <20170120054100.902-2-matt@ranostay.consulting> Content-Type: text/plain; charset=windows-1252 Sender: linux-iio-owner@vger.kernel.org List-Id: linux-iio@vger.kernel.org On 20/01/17 05:40, Matt Ranostay wrote: > Cc: devicetree@vger.kernel.org > Signed-off-by: Matt Ranostay > --- > .../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? > + > +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>; > +}; >