linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Murphy <dmurphy@ti.com>
To: Jonathan Cameron <jic23@kernel.org>, <linux-iio@vger.kernel.org>
Cc: <pmeerw@pmeerw.net>, <daniel.baluta@intel.com>,
	<k.wrona@samsung.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Rob Herring <robh+dt@kernel.org>, Pawel Moll <Pawel.Moll@arm.com>,
	Mark Rutland <Mark.Rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>
Subject: Re: [RFC v2 2/3] iio: bindings: Add TI afe4403 heart monitor documentation
Date: Thu, 13 Nov 2014 06:40:59 -0600	[thread overview]
Message-ID: <5464A6DB.3060203@ti.com> (raw)
In-Reply-To: <545E031A.7050302@kernel.org>

Jonathan

On 11/08/2014 05:48 AM, Jonathan Cameron wrote:
> On 06/11/14 15:18, 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>
> As a device tree binding this MUST go to the device tree list
> and maintainers.  Cc'd.

Yeah forgot to add the list

>
> I suspect from my review of the driver that there will be a
> whole load more stuff to go in here...
>
>> ---
>>
>> v2 - Updated per v1 comments - http://marc.info/?l=linux-iio&m=141331404132215&w=2
>>
>>  .../bindings/iio/heart_monitor/ti_afe4403.txt      | 23 ++++++++++++++++++++++
>>  1 file changed, 23 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..cf75b5a
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/iio/heart_monitor/ti_afe4403.txt
>> @@ -0,0 +1,23 @@
>> +* 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
>> +  - data-ready-gpio: GPIO interrupt when the afe4403 has data
> Does this actually need to be a gpio?  Doesn't look like it from the driver.
> As such should be handled as a generic interrupt both here and in the driver.

Well in my setup I connected the data-ready output of the device to a GPIO
and I need to tell the driver which GPIO to use.

Not sure how else to route the signal from the device to a SoC.

>
>> +  - 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>;
>> +};
>>


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


  reply	other threads:[~2014-11-13 12:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-06 15:18 [RFC v2 1/3] iio: heart_monitors: Add support for heart rate monitors Dan Murphy
2014-11-06 15:18 ` [RFC v2 2/3] iio: bindings: Add TI afe4403 heart monitor documentation Dan Murphy
2014-11-08 11:48   ` Jonathan Cameron
2014-11-13 12:40     ` Dan Murphy [this message]
2014-11-19 22:02   ` Hartmut Knaack
2014-11-06 15:18 ` [RFC v2 3/3] iio: heart_monitor: Add TI afe4403 heart monitor Dan Murphy
2014-11-08 11:47   ` Jonathan Cameron
2014-11-06 16:04 ` [RFC v2 1/3] iio: heart_monitors: Add support for heart rate monitors Daniel Baluta
2014-11-13 12:43   ` Dan Murphy

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=5464A6DB.3060203@ti.com \
    --to=dmurphy@ti.com \
    --cc=Mark.Rutland@arm.com \
    --cc=Pawel.Moll@arm.com \
    --cc=daniel.baluta@intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=jic23@kernel.org \
    --cc=k.wrona@samsung.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=pmeerw@pmeerw.net \
    --cc=robh+dt@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).