From: Stephen Warren <swarren@wwwdotorg.org>
To: Jacek Anaszewski <j.anaszewski@samsung.com>
Cc: linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
jic23@kernel.org, kyungmin.park@samsung.com,
s.nawrocki@samsung.com, rob.herring@calxeda.com,
pawel.moll@arm.com, mark.rutland@arm.com,
ian.campbell@citrix.com
Subject: Re: [PATCH/RFC v4 3/3] DT: Add documentation for gp2ap020a00f sensor
Date: Mon, 19 Aug 2013 15:29:05 -0600 [thread overview]
Message-ID: <52128E21.6020303@wwwdotorg.org> (raw)
In-Reply-To: <1376658760-3459-1-git-send-email-j.anaszewski@samsung.com>
On 08/16/2013 07:12 AM, Jacek Anaszewski wrote:
> This patch adds device tree binding documentation
> for the gp2ap020a00f proximity/als sensor.
> diff --git a/Documentation/devicetree/bindings/iio/light/gp2ap020a00f.txt b/Documentation/devicetree/bindings/iio/light/gp2ap020a00f.txt
> new file mode 100644
> index 0000000..e4f377d
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/light/gp2ap020a00f.txt
> @@ -0,0 +1,20 @@
> +* Sharp GP2AP020A00F I2C Proximity/ALS sensor
> +
> +Required properties:
> +
> + - compatible : should be "sharp,gp2ap020a00f"
> + - reg : the I2C address of the light sensor
> + - interrupt-parent : phandle to the parent interrupt controller
> + - interrupts : should be INT interrupt pin
> + - vled-supply : VLED power supply, as covered
> + in Documentation/devicetree/bindings/regulator/regulator.txt
If this is a sensor for proximity and light, why does it need a
regulator for an LED?
next prev parent reply other threads:[~2013-08-19 21:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-16 13:12 [PATCH/RFC v4 3/3] DT: Add documentation for gp2ap020a00f sensor Jacek Anaszewski
2013-08-16 13:28 ` Pawel Moll
2013-08-19 10:55 ` Sylwester Nawrocki
2013-08-19 12:13 ` Pawel Moll
2013-08-19 21:29 ` Stephen Warren [this message]
2013-08-20 5:54 ` Jonathan Cameron
2013-08-20 16:20 ` Stephen Warren
2013-08-21 8:29 ` Jacek Anaszewski
2013-08-21 17:12 ` Stephen Warren
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=52128E21.6020303@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=devicetree@vger.kernel.org \
--cc=ian.campbell@citrix.com \
--cc=j.anaszewski@samsung.com \
--cc=jic23@kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-iio@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=s.nawrocki@samsung.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.