From: David Heidelberg <david@ixit.cz>
To: Rob Herring <robh@kernel.org>
Cc: "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>,
"Mark Rutland" <mark.rutland@arm.com>,
devicetree@vger.kernel.org, linux-iio@vger.kernel.org
Subject: Re: [PATCH v4 1/7] dt-bindings: iio: light: add support for Dyna-Image AL3320A
Date: Thu, 06 Feb 2020 22:16:39 +0100 [thread overview]
Message-ID: <1581023799.790008.0@ixit.cz> (raw)
In-Reply-To: <20200206190758.GA11064@bogus>
Rob Herring <robh@kernel.org> napsal Čt, 6. úno 2020 v 19∶07:
> On Tue, Feb 04, 2020 at 10:30:27AM +0100, David Heidelberg wrote:
>> This commit add dt-bindings support to al3320a driver and
>> vendor-prefix
>> dynaimage.
>>
>>
>> Signed-off-by: David Heidelberg <david@ixit.cz>
>> ---
>> .../bindings/iio/light/al3320a.yaml | 45
>> +++++++++++++++++++
>> .../devicetree/bindings/vendor-prefixes.yaml | 2 +
>> 2 files changed, 47 insertions(+)
>> create mode 100644
>> Documentation/devicetree/bindings/iio/light/al3320a.yaml
>>
>> diff --git
>> a/Documentation/devicetree/bindings/iio/light/al3320a.yaml
>> b/Documentation/devicetree/bindings/iio/light/al3320a.yaml
>> new file mode 100644
>> index 000000000000..08e7ee4bdf55
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/iio/light/al3320a.yaml
>> @@ -0,0 +1,45 @@
>> +# SPDX-License-Identifier: (GPL-2.0-only)
>
> Dual license new bindings:
>
> (GPL-2.0-only OR BSD-2-Clause)
It BSD usage in Linux kernel enforced for bindings?
I'd like to publish my code only under GPL if possible.
>
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/iio/light/al3320a.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: Dyna-Image AL3320A sensor
>> +
>> +maintainers:
>> + - David Heidelberg <david@ixit.cz>
>> +
>> +properties:
>> + compatible:
>> + const: dynaimage,al3320a
>> +
>> + reg:
>> + maxItems: 1
>> +
>> + interrupts:
>> + maxItems: 1
>> +
>> + vdd-supply:
>> + description: Regulator that provides power to the sensor
>> +
>> +required:
>> + - compatible
>> + - reg
>> + - interrupts
>> + - vdd-supply
>> +
>> +examples:
>> + - |
>> + #include <dt-bindings/interrupt-controller/irq.h>
>> +
>> + i2c {
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> +
>> + al3320a@1c {
>
> light-sensor@1c
Fixed for next revision, thanks.
>
>> + compatible = "dynaimage,al3320a";
>> + reg = <0x1c>;
>> + vdd-supply = <&vdd_reg>;
>> + interrupts = <0 99 4>;
>> + };
>> + };
>> diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml
>> b/Documentation/devicetree/bindings/vendor-prefixes.yaml
>> index 9cd52d9e1f7f..8d2ebf3d0aa1 100644
>> --- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
>> +++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
>> @@ -267,6 +267,8 @@ patternProperties:
>> description: Dragino Technology Co., Limited
>> "^dserve,.*":
>> description: dServe Technology B.V.
>> + "^dynaimage,.*":
>> + description: Dyna-Image
>> "^ea,.*":
>> description: Embedded Artists AB
>> "^ebs-systart,.*":
>> --
>> 2.25.0
>>
next prev parent reply other threads:[~2020-02-06 21:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200204093031.616409-1-david@ixit.cz>
2020-02-04 9:30 ` [PATCH v4 1/7] dt-bindings: iio: light: add support for Dyna-Image AL3320A David Heidelberg
2020-02-06 19:07 ` Rob Herring
2020-02-06 21:16 ` David Heidelberg [this message]
2020-02-06 21:27 ` Rob Herring
2020-02-06 21:44 ` David Heidelberg
2020-02-04 9:30 ` [PATCH v4 2/7] dt-bindings: iio: light: add support for Dyna-Image AL3010 David Heidelberg
2020-02-04 9:52 ` Michał Mirosław
2020-02-04 15:10 ` Dmitry Osipenko
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=1581023799.790008.0@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@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).