From: Jonathan Cameron <jic23@kernel.org>
To: Rishi Gupta <gupt21@gmail.com>
Cc: knaack.h@gmx.de, lars@metafoo.de, pmeerw@pmeerw.net,
gregkh@linuxfoundation.org, tglx@linutronix.de,
allison@lohutok.net, alexios.zavras@intel.com, angus@akkea.ca,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
hslester96@gmail.com, wsa+renesas@sang-engineering.com,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org
Subject: Re: [RESEND PATCH v2 2/3] dt-bindings: iio: light: add veml6030 ALS bindings
Date: Sat, 5 Oct 2019 15:14:04 +0100 [thread overview]
Message-ID: <20191005151404.5fc7386f@archlinux> (raw)
In-Reply-To: <b9d5cb134c7c2c7351025a0b556148bca23f302f.1569321085.git.gupt21@gmail.com>
On Tue, 24 Sep 2019 16:21:57 +0530
Rishi Gupta <gupt21@gmail.com> wrote:
> This commit adds device tree bindings for veml6030 ambient
> light sensor.
>
> Signed-off-by: Rishi Gupta <gupt21@gmail.com>
looks fine to me, but...
DT bindings should always be sent to the DT-bindings maintainers and mailing list
for review.
+CC Rob, Mark and devicetree list.
Jonathan
> ---
> Changes in v2:
> * Corrected grammatical mistake from 'is' to 'are' in description of bindings
>
> .../devicetree/bindings/iio/light/veml6030.yaml | 62 ++++++++++++++++++++++
> 1 file changed, 62 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/iio/light/veml6030.yaml
>
> diff --git a/Documentation/devicetree/bindings/iio/light/veml6030.yaml b/Documentation/devicetree/bindings/iio/light/veml6030.yaml
> new file mode 100644
> index 0000000..969b314
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/light/veml6030.yaml
> @@ -0,0 +1,62 @@
> +# SPDX-License-Identifier: GPL-2.0+
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/iio/light/veml6030.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: VEML6030 Ambient Light Sensor (ALS)
> +
> +maintainers:
> + - Rishi Gupta <gupt21@gmail.com>
> +
> +description: |
> + Bindings for the ambient light sensor veml6030 from Vishay
> + Semiconductors over an i2c interface.
> +
> + Irrespective of whether interrupt is used or not, application
> + can get the ALS and White channel reading from IIO raw interface.
> +
> + If the interrupts are used, application will receive an IIO event
> + whenever configured threshold is crossed.
> +
> + Specifications about the sensor can be found at:
> + https://www.vishay.com/docs/84366/veml6030.pdf
> +
> +properties:
> + compatible:
> + enum:
> + - vishay,veml6030
> +
> + reg:
> + description:
> + I2C address of the device. If the ADDR pin on veml6030
> + is pulled up, this address is 0x48. If the ADDR pin is
> + pulled down, this address is 0x10.
> + maxItems: 1
> +
> + interrupts:
> + description:
> + interrupt mapping for IRQ. Configure with IRQ_TYPE_LEVEL_LOW.
> + Refer to interrupt-controller/interrupts.txt for generic
> + interrupt client node bindings.
> + maxItems: 1
> +
> +required:
> + - compatible
> + - reg
> +
> +examples:
> + - |
> + #include <dt-bindings/interrupt-controller/irq.h>
> +
> + i2c {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + light-sensor@10 {
> + compatible = "vishay,veml6030";
> + reg = <0x10>;
> + interrupts = <12 IRQ_TYPE_LEVEL_LOW>;
> + };
> + };
> +...
next parent reply other threads:[~2019-10-05 14:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1569321085.git.gupt21@gmail.com>
[not found] ` <b9d5cb134c7c2c7351025a0b556148bca23f302f.1569321085.git.gupt21@gmail.com>
2019-10-05 14:14 ` Jonathan Cameron [this message]
2019-10-21 13:31 ` [PATCH v3 2/3] dt-bindings: iio: light: add veml6030 ALS bindings Rishi Gupta
2019-10-21 17:28 ` Rob Herring
2019-10-22 3:57 ` [PATCH v4 " Rishi Gupta
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=20191005151404.5fc7386f@archlinux \
--to=jic23@kernel.org \
--cc=alexios.zavras@intel.com \
--cc=allison@lohutok.net \
--cc=angus@akkea.ca \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=gupt21@gmail.com \
--cc=hslester96@gmail.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pmeerw@pmeerw.net \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
--cc=wsa+renesas@sang-engineering.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 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).