From: Parthiban Nallathambi <pn@denx.de>
To: jic23@kernel.org, knaack.h@gmx.de, lars@metafoo.de,
pmeerw@pmeerw.net, robh+dt@kernel.org, andy.shevchenko@gmail.com
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
mark.rutland@arm.com, devicetree@vger.kernel.org,
matthias.bgg@gmail.com, wd@denx.de, sbabic@denx.de, hs@denx.de,
Parthiban Nallathambi <pn@denx.de>
Subject: [PATCH v6 2/2] iio: light: Add device tree binding for vishay vcnl4035
Date: Tue, 7 Aug 2018 12:27:04 +0200 [thread overview]
Message-ID: <20180807102704.1652656-2-pn@denx.de> (raw)
In-Reply-To: <20180807102704.1652656-1-pn@denx.de>
Adding device tree binding for vcnl4035 and vendor
prefix for Vishay Intertechnology
Signed-off-by: Parthiban Nallathambi <pn@denx.de>
Changelog in v3:
- removed interrupt-parent property reference in documentation
- renamed vcnl4035 to light-sensor
Changelog in v4:
- commit message fix
- same indexing/space in binding
---
.../devicetree/bindings/iio/light/vcnl4035.txt | 18 ++++++++++++++++++
Documentation/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 7cad066191ee..3cc46d5735a9 100644
--- a/Documentation/devicetree/bindings/vendor-prefixes.txt
+++ b/Documentation/devicetree/bindings/vendor-prefixes.txt
@@ -395,6 +395,7 @@ v3 V3 Semiconductor
variscite Variscite Ltd.
via VIA Technologies, Inc.
virtio Virtual I/O Device Specification, developed by the OASIS consortium
+vishay Vishay Intertechnology, Inc
vivante Vivante Corporation
vocore VoCore Studio
voipac Voipac Technologies s.r.o.
--
2.14.4
next prev parent reply other threads:[~2018-08-07 10:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-07 10:27 [PATCH v6 1/2] iio: light: Add support for vishay vcnl4035 Parthiban Nallathambi
2018-08-07 10:27 ` Parthiban Nallathambi [this message]
2018-08-07 14:54 ` [PATCH v6 2/2] iio: light: Add device tree binding " Rob Herring
2018-08-11 15:25 ` [PATCH v6 1/2] iio: light: Add support " kbuild test robot
2018-08-19 17:35 ` Jonathan Cameron
2018-08-19 18:51 ` Jonathan Cameron
2018-08-19 21:50 ` Marcus Folkesson
2018-08-20 8:27 ` Parthiban Nallathambi
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=20180807102704.1652656-2-pn@denx.de \
--to=pn@denx.de \
--cc=andy.shevchenko@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=hs@denx.de \
--cc=jic23@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=robh+dt@kernel.org \
--cc=sbabic@denx.de \
--cc=wd@denx.de \
/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).