From: David Heidelberg <david@ixit.cz>
To: linux-iio@vger.kernel.org
Cc: "David Heidelberg" <david@ixit.cz>,
"Dmitry Osipenko" <digetx@gmail.com>,
"Michał Mirosław" <mirq-linux@rere.qmqm.pl>,
"Daniel Baluta" <daniel.baluta@nxp.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"Hartmut Knaack" <knaack.h@gmx.de>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Peter Meerwald-Stadler" <pmeerw@pmeerw.net>,
"Rob Herring" <robh+dt@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
devicetree@vger.kernel.org
Subject: [PATCH v2 2/7] dt-bindings: iio: light: add support for Dyna-Image AL3010
Date: Tue, 28 Jan 2020 14:30:47 +0100 [thread overview]
Message-ID: <20200128133052.201587-3-david@ixit.cz> (raw)
In-Reply-To: <20200128133052.201587-1-david@ixit.cz>
The Dyna-Image AL3010 is a 16-bit digital ambient light sensor which
provides a multiple gain function with linear response over a dynamic
range 1216/4863/19452/77806.
Signed-off-by: David Heidelberg <david@ixit.cz>
---
.../devicetree/bindings/iio/light/al3010.yaml | 40 +++++++++++++++++++
1 file changed, 40 insertions(+)
create mode 100644 Documentation/devicetree/bindings/iio/light/al3010.yaml
diff --git a/Documentation/devicetree/bindings/iio/light/al3010.yaml b/Documentation/devicetree/bindings/iio/light/al3010.yaml
new file mode 100644
index 000000000000..9cd1f34a6d63
--- /dev/null
+++ b/Documentation/devicetree/bindings/iio/light/al3010.yaml
@@ -0,0 +1,40 @@
+# SPDX-License-Identifier: (GPL-2.0-only)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/iio/light/al3010.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Dyna-Image AL3010 sensor
+
+maintainers:
+ - David Heidelberg <david@ixit.cz>
+
+properties:
+ compatible:
+ const: dynaimage,al3010
+
+ reg:
+ maxItems: 1
+
+ interrupts:
+ maxItems: 1
+
+ vdd-supply:
+ description: Regulator that provides power to the sensor
+
+required:
+ - compatible
+ - reg
+ - interrupt
+ - vdd-supply
+
+examples:
+ - |
+ i2c {
+ al3010@1c {
+ compatible = "dynaimage,al3010";
+ reg = <0x1c>;
+ vdd-supply = <&vdd_reg>;
+ interrupts = <0 99 4>;
+ };
+ };
--
2.25.0
next prev parent reply other threads:[~2020-01-28 13:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 13:30 [PATCH 0/7] iio: light: AL3010 introduction David Heidelberg
2020-01-28 13:30 ` [PATCH v2 1/7] dt-bindings: iio: light: add support for Dyna-Image AL3320A David Heidelberg
2020-01-31 14:23 ` Rob Herring
2020-01-28 13:30 ` David Heidelberg [this message]
2020-01-28 19:43 ` [PATCH v2 2/7] dt-bindings: iio: light: add support for Dyna-Image AL3010 Dmitry Osipenko
2020-01-31 14:24 ` Rob Herring
2020-01-31 14:28 ` Dmitry Osipenko
2020-01-28 13:30 ` [PATCH v2 3/7] iio: light: al3320a slightly improve code formatting David Heidelberg
2020-01-28 13:30 ` [PATCH v2 4/7] iio: light: add Dyna-Image AL3010 driver David Heidelberg
2020-01-28 13:30 ` [PATCH v2 5/7] iio: light: al3010 implement suspend support David Heidelberg
2020-01-28 19:46 ` Dmitry Osipenko
2020-01-28 13:30 ` [PATCH v2 6/7] iio: light: al3320a " David Heidelberg
2020-01-28 13:30 ` [PATCH v2 7/7] iio: light: al3320a allow module autoload and polish David Heidelberg
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=20200128133052.201587-3-david@ixit.cz \
--to=david@ixit.cz \
--cc=daniel.baluta@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=digetx@gmail.com \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mirq-linux@rere.qmqm.pl \
--cc=pmeerw@pmeerw.net \
--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).