From: Jonathan Cameron <jic23@kernel.org>
To: Parthiban Nallathambi <pn@denx.de>
Cc: knaack.h@gmx.de, lars@metafoo.de, pmeerw@pmeerw.net,
robh+dt@kernel.org, andy.shevchenko@gmail.com,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
mark.rutland@arm.com, devicetree@vger.kernel.org,
matthias.bgg@gmail.com
Subject: Re: [PATCH v7 2/2] iio: light: Add device tree binding for vishay vcnl4035
Date: Sun, 11 Nov 2018 13:29:28 +0000 [thread overview]
Message-ID: <20181111132928.218d0811@archlinux> (raw)
In-Reply-To: <20181107170821.1171886-2-pn@denx.de>
On Wed, 7 Nov 2018 18:08:21 +0100
Parthiban Nallathambi <pn@denx.de> wrote:
> Adding device tree binding for vcnl4035 and vendor
> prefix for Vishay Intertechnology
>
> Signed-off-by: Parthiban Nallathambi <pn@denx.de>
> Reviewed-by: Rob Herring <robh@kernel.org>
Applied. Thanks,
Jonathan
> ---
>
> Notes:
> Changelog in v4:
> - commit message fix
> - same indexing/space in binding
>
> Changelog in v3:
> - removed interrupt-parent property reference in documentation
> - renamed vcnl4035 to light-sensor
>
> .../devicetree/bindings/iio/light/vcnl4035.txt | 18 ++++++++++++++++++
> .../devicetree/bindings/vendor-prefixes.txt | 1 +
> 2 files changed, 19 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/iio/light/vcnl4035.txt
>
> diff --git a/Documentation/devicetree/bindings/iio/light/vcnl4035.txt b/Documentation/devicetree/bindings/iio/light/vcnl4035.txt
> new file mode 100644
> index 000000000000..c07c7f052556
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/light/vcnl4035.txt
> @@ -0,0 +1,18 @@
> +VISHAY VCNL4035 - Ambient Light and proximity sensor
> +
> +Link to datasheet: https://www.vishay.com/docs/84251/vcnl4035x01.pdf
> +
> +Required properties:
> +
> + -compatible: should be "vishay,vcnl4035"
> + -reg: I2C address of the sensor, should be 0x60
> + -interrupts: interrupt mapping for GPIO IRQ (level active low)
> +
> +Example:
> +
> +light-sensor@60 {
> + compatible = "vishay,vcnl4035";
> + reg = <0x60>;
> + interrupt-parent = <&gpio4>;
> + interrupts = <11 IRQ_TYPE_LEVEL_LOW>;
> +};
> diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt b/Documentation/devicetree/bindings/vendor-prefixes.txt
> index 4b1a2a8fcc16..3c5e0c6f6cee 100644
> --- a/Documentation/devicetree/bindings/vendor-prefixes.txt
> +++ b/Documentation/devicetree/bindings/vendor-prefixes.txt
> @@ -415,6 +415,7 @@ vamrs Vamrs Ltd.
> variscite Variscite Ltd.
> via VIA Technologies, Inc.
> virtio Virtual I/O Device Specification, developed by the OASIS consortium
> +vishay Vishay Intertechnology, Inc
> vitesse Vitesse Semiconductor Corporation
> vivante Vivante Corporation
> vocore VoCore Studio
next prev parent reply other threads:[~2018-11-11 13:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 17:08 [PATCH v7 1/2] iio: light: Add support for vishay vcnl4035 Parthiban Nallathambi
2018-11-07 17:08 ` [PATCH v7 2/2] iio: light: Add device tree binding " Parthiban Nallathambi
2018-11-11 13:29 ` Jonathan Cameron [this message]
2018-11-07 20:24 ` [PATCH v7 1/2] iio: light: Add support " Andy Shevchenko
2018-11-11 13:27 ` 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=20181111132928.218d0811@archlinux \
--to=jic23@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=devicetree@vger.kernel.org \
--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=matthias.bgg@gmail.com \
--cc=pmeerw@pmeerw.net \
--cc=pn@denx.de \
--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).