From: Rob Herring <robh@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
linux-iio@vger.kernel.org, "Hartmut Knaack" <knaack.h@gmx.de>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Peter Meerwald-Stadler" <pmeerw@pmeerw.net>,
linux-input@vger.kernel.org,
"Stephan Gerhold" <stephan@gerhold.net>,
"Donggeun Kim" <dg77.kim@samsung.com>,
"Minkyu Kang" <mk7.kang@samsung.com>,
"Paweł Chmiel" <pawel.mikolaj.chmiel@gmail.com>,
"Jonathan Bakker" <xc-racer2@live.ca>,
"Oskar Andero" <oskar.andero@gmail.com>,
"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2 v1] iio: light: Add DT bindings for GP2AP002
Date: Wed, 8 Jan 2020 10:46:23 -0600 [thread overview]
Message-ID: <20200108164623.GA18967@bogus> (raw)
In-Reply-To: <20191228201109.13635-1-linus.walleij@linaro.org>
On Sat, Dec 28, 2019 at 09:11:08PM +0100, Linus Walleij wrote:
> This adds device tree bindings for the GP2AP002 light
> and proximity sensor.
>
> As with other early proximity sensors (~2010) the light
> sensor and proximity sensors were combined into a single
> component.
>
> Cc: Stephan Gerhold <stephan@gerhold.net>
> Cc: Donggeun Kim <dg77.kim@samsung.com>
> Cc: Minkyu Kang <mk7.kang@samsung.com>
> Cc: Paweł Chmiel <pawel.mikolaj.chmiel@gmail.com>
> Cc: Jonathan Bakker <xc-racer2@live.ca>
> Cc: Oskar Andero <oskar.andero@gmail.com>
> Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> Cc: devicetree@vger.kernel.org
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> .../bindings/iio/light/sharp,gp2ap002.yaml | 87 +++++++++++++++++++
> 1 file changed, 87 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/iio/light/sharp,gp2ap002.yaml
>
> diff --git a/Documentation/devicetree/bindings/iio/light/sharp,gp2ap002.yaml b/Documentation/devicetree/bindings/iio/light/sharp,gp2ap002.yaml
> new file mode 100644
> index 000000000000..27d129e76a8b
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/light/sharp,gp2ap002.yaml
> @@ -0,0 +1,87 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/iio/light/sharp,gp2ap002.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Sharp GP2AP002A00F and GP2AP002S00F proximity and ambient light sensors
> +
> +maintainers:
> + - Linus Walleij <linus.walleij@linaro.org>
> +
> +description: |
> + Proximity and ambient light sensor with IR LED for the proximity
> + sensing and an analog output for light intensity. The ambient light
> + sensor output is not available on the GP2AP002S00F variant.
> +
> +properties:
> + compatible:
> + enum:
> + - sharp,gp2ap002a00f
> + - sharp,gp2ap002s00f
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + maxItems: 1
> + description: an interrupt for proximity, usually a GPIO line
> +
> + vdd-supply:
> + maxItems: 1
*-supply is always 1 item, so drop.
> + description: VDD power supply a phandle to a regulator
> +
> + vio-supply:
> + maxItems: 1
> + description: VIO power supply a phandle to a regulator
> +
> + io-channels:
> + maxItems: 1
> + description: ALSOUT ADC channel to read the ambient light
> +
> + io-channel-names:
> + const: "alsout"
Drop quotes
> +
> + sharp,proximity-far-hysteresis:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description: |
> + Hysteresis setting for "far" object detection, this setting is
> + device-unique and adjust the optical setting for proximity detection
> + of a "far away" object in front of the sensor.
0-2^32 is allowed?
default?
> +
> + sharp,proximity-close-hysteresis:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description: |
> + Hysteresis setting for "close" object detection, this setting is
> + device-unique and adjust the optical setting for proximity detection
> + of a "close" object in front of the sensor.
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> + - sharp,proximity-far-hysteresis
> + - sharp,proximity-close-hysteresis
> +
> +examples:
> + - |
> + #include <dt-bindings/interrupt-controller/irq.h>
> +
> + i2c {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + light-sensor@44 {
> + compatible = "sharp,gp2ap002a00f";
> + reg = <0x44>;
> + interrupts = <18 IRQ_TYPE_EDGE_FALLING>;
> + vdd-supply = <&vdd_regulator>;
> + vio-supply = <&vio_regulator>;
> + io-channels = <&adc_channel>;
> + io-channel-names = "alsout";
> + sharp,proximity-far-hysteresis = <0x2f>;
> + sharp,proximity-close-hysteresis = <0x0f>;
> + };
> + };
> +
> +...
> --
> 2.21.0
>
prev parent reply other threads:[~2020-01-08 16:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-28 20:11 [PATCH 1/2 v1] iio: light: Add DT bindings for GP2AP002 Linus Walleij
2019-12-28 20:11 ` [PATCH 2/2 v1] iio: light: Add a driver for Sharp GP2AP002x00F Linus Walleij
2019-12-30 17:39 ` Jonathan Cameron
2020-01-02 22:15 ` Dmitry Torokhov
2020-01-05 10:36 ` Jonathan Cameron
2020-01-06 9:08 ` Linus Walleij
2020-01-07 11:59 ` Jonathan Cameron
2020-01-08 16:46 ` Rob Herring [this message]
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=20200108164623.GA18967@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dg77.kim@samsung.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linus.walleij@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=mk7.kang@samsung.com \
--cc=oskar.andero@gmail.com \
--cc=pawel.mikolaj.chmiel@gmail.com \
--cc=pmeerw@pmeerw.net \
--cc=stephan@gerhold.net \
--cc=xc-racer2@live.ca \
/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).