public inbox for linux-iio@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Murphy <dmurphy@ti.com>
To: Jonathan Cameron <jic23@kernel.org>, <linux-iio@vger.kernel.org>
Subject: Re: [PATCH 2/3] iio: bindings: Add TI afe4403 heart monitor documentation
Date: Mon, 27 Apr 2015 09:49:28 -0500	[thread overview]
Message-ID: <553E4C78.8000100@ti.com> (raw)
In-Reply-To: <553D20CA.7090107@kernel.org>

Jpnathan

On 04/26/2015 12:30 PM, Jonathan Cameron wrote:
> On 22/04/15 17:32, Dan Murphy wrote:
>> Add the TI afe4403 heart monitor device tree
>> binding documentation.  heart_monitors directory
>> created under iio.
>>
>> Signed-off-by: Dan Murphy <dmurphy@ti.com>
>> ---
>>  .../bindings/iio/heart_monitor/ti_afe4403.txt      | 26 ++++++++++++++++++++++
>>  1 file changed, 26 insertions(+)
>>  create mode 100644 Documentation/devicetree/bindings/iio/heart_monitor/ti_afe4403.txt
>>
>> diff --git a/Documentation/devicetree/bindings/iio/heart_monitor/ti_afe4403.txt b/Documentation/devicetree/bindings/iio/heart_monitor/ti_afe4403.txt
>> new file mode 100644
>> index 0000000..b196b17
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/iio/heart_monitor/ti_afe4403.txt
>> @@ -0,0 +1,26 @@
>> +* Texas Instruments - AFE4403 Heart rate and Pulse Oximeter
>> +
>> +The device consists of a low-noise receiver channel
>> +with an integrated analog-to-digital converter (ADC),
>> +an LED transmit section, and diagnostics for sensor and LED fault detection.
>> +
>> +Required properties:
>> +  - compatible: Must contain "ti,afe4403".
>> +  - ste-gpio: GPIO for the spi control line
> This gpio needs more info here.  From description it sounds like a chip select
> and those obviously don't need to be specified at driver level.

It is a chip select line.  There was an issue with this from the device side.
I will need to dig this up again and remember why I did this.

Maybe I can remove it.

Dan


>> +  - data-ready-gpio: GPIO interrupt when the afe4403 has data
>> +  - led-supply: Chip supply to the device
>> +
>> +Optional properties:
>> +  - reset-gpio: GPIO used to reset the device via HW
>> +
>> +Example:
>> +
>> +&heart_rate {
>> +	compatible = "ti,afe4403";
>> +	ste-gpio = <&gpio1 29 GPIO_ACTIVE_HIGH>;
>> +	data-ready-gpio = <&gpio1 28 GPIO_ACTIVE_HIGH>;
>> +	led-supply = <&vbat>;
>> +};
>> +
>> +Technical Datasheet:
>> +http://www.ti.com/product/AFE4403/datasheet
>>


-- 
------------------
Dan Murphy


  reply	other threads:[~2015-04-27 14:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-22 16:32 Adding Heart Monitors to IIO take 2 Dan Murphy
2015-04-22 16:32 ` [PATCH 1/3] iio: heart_monitors: Add support for heart rate monitors Dan Murphy
2015-04-26 17:29   ` Jonathan Cameron
2015-04-27 14:35     ` Dan Murphy
2015-04-22 16:32 ` [PATCH 2/3] iio: bindings: Add TI afe4403 heart monitor documentation Dan Murphy
2015-04-26 17:30   ` Jonathan Cameron
2015-04-27 14:49     ` Dan Murphy [this message]
2015-04-22 16:32 ` [PATCH 3/3] iio: heart_monitor: Add TI afe4403 heart monitor Dan Murphy
2015-04-26 18:38   ` Jonathan Cameron
2015-04-29 12:27     ` Dan Murphy
2015-05-07 22:51       ` Jonathan Cameron
2015-05-08 19:56         ` Dan Murphy
2015-04-29 13:52     ` Dan Murphy
2015-05-07 22:52       ` Jonathan Cameron

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=553E4C78.8000100@ti.com \
    --to=dmurphy@ti.com \
    --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