All of lore.kernel.org
 help / color / mirror / Atom feed
From: Parthiban Nallathambi <pn@denx.de>
To: jic23@kernel.org, knaack.h@gmx.de, lars@metafoo.de,
	pmeerw@pmeerw.net, robh+dt@kernel.org
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 v3 2/2] iio: light: Add device tree binding for vishay vcnl4035
Date: Thu,  2 Aug 2018 11:52:30 +0200	[thread overview]
Message-ID: <20180802095230.2049554-2-pn@denx.de> (raw)
In-Reply-To: <20180802095230.2049554-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
---
 .../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..871f995f7b35
--- /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


  reply	other threads:[~2018-08-02  9:52 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-28 12:30 [PATCH 1/2] iio: light: Add support for vishay vcnl4035 Parthiban Nallathambi
2018-06-28 12:30 ` [PATCH 2/2] iio: light: Add device tree binding " Parthiban Nallathambi
2018-06-28 15:35 ` [PATCH 1/2] iio: light: Add support " kbuild test robot
2018-06-28 15:35   ` kbuild test robot
2018-06-29 15:38 ` [PATCH v2 " Parthiban Nallathambi
2018-06-29 15:38   ` [PATCH v2 2/2] iio: light: Add device tree binding " Parthiban Nallathambi
2018-07-06 20:34     ` Rob Herring
2018-07-07 17:06       ` Parthiban Nallathambi
2018-06-29 23:46   ` [PATCH v2 1/2] iio: light: Add support " kbuild test robot
2018-06-29 23:46     ` kbuild test robot
2018-06-30  9:51   ` Peter Meerwald-Stadler
2018-07-03 12:58     ` Parthiban Nallathambi
2018-08-02  9:52   ` [PATCH v3 " Parthiban Nallathambi
2018-08-02  9:52     ` Parthiban Nallathambi [this message]
2018-08-02 12:51       ` [PATCH v3 2/2] iio: light: Add device tree binding " Jonathan Cameron
2018-08-02 12:51         ` Jonathan Cameron
2018-08-02 12:49     ` [PATCH v3 1/2] iio: light: Add support " Jonathan Cameron
2018-08-02 12:49       ` Jonathan Cameron
2018-08-02 14:01       ` Parthiban Nallathambi
2018-08-03 22:16         ` Jonathan Cameron
2018-06-29 17:59 ` [PATCH " Jonathan Cameron
2018-06-29 17:59   ` Jonathan Cameron
2018-07-03 13:35   ` Parthiban Nallathambi
2018-07-07 16:23     ` 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=20180802095230.2049554-2-pn@denx.de \
    --to=pn@denx.de \
    --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 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.