All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gabriel Krisman Bertazi <krisman@collabora.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Shreeya Patel <shreeya.patel@collabora.com>,
	lars@metafoo.de, robh+dt@kernel.org, Zhigang.Shi@liteon.com,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, kernel@collabora.com,
	alvaro.soliverez@collabora.com
Subject: Re: [PATCH 2/3] dt-bindings: Document ltrf216a light sensor bindings
Date: Sun, 27 Mar 2022 22:49:20 -0400	[thread overview]
Message-ID: <87czi6ssen.fsf@collabora.com> (raw)
In-Reply-To: <20220327145511.2d36dd10@jic23-huawei> (Jonathan Cameron's message of "Sun, 27 Mar 2022 14:55:11 +0100")

Jonathan Cameron <jic23@kernel.org> writes:

> On Fri, 25 Mar 2022 16:00:13 +0530
> Shreeya Patel <shreeya.patel@collabora.com> wrote:
>
>> Add devicetree bindings for ltrf216a ambient light sensor
>> 
>> Signed-off-by: Shreeya Patel <shreeya.patel@collabora.com>
> Hi Shreeya,
>
> As we are making this Zhigang Shi's problem to maintain, I'm 
> looking for an ack.  Bit mean otherwise :)

Alternatively, Shreeya could take over the maintainership of this
schema, since she wrote it. :)

>
> Except for the deprecated part this could just have gone in
> trivial-bindings.yaml.
>
> I guess you don't need it for your existing board, but best
> practice would probably include ensuring whatever supplies
> the device needs are here so that platforms that don't enable
> them by default can turn them on.
>
> Also, there is an interrupt according to the datasheet linked
> from patch 3 and that should definitely be in the binding
> even if the driver isn't using it.
>
> Jonathan
>
>
>> ---
>>  .../bindings/iio/light/liteon,ltrf216a.yaml   | 42 +++++++++++++++++++
>>  1 file changed, 42 insertions(+)
>>  create mode 100644 Documentation/devicetree/bindings/iio/light/liteon,ltrf216a.yaml
>> 
>> diff --git a/Documentation/devicetree/bindings/iio/light/liteon,ltrf216a.yaml b/Documentation/devicetree/bindings/iio/light/liteon,ltrf216a.yaml
>> new file mode 100644
>> index 000000000000..275d86a0353a
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/iio/light/liteon,ltrf216a.yaml
>> @@ -0,0 +1,42 @@
>> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/iio/light/liteon,ltrf216a.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: LTRF216A Ambient Light Sensor
>> +
>> +maintainers:
>> +  - Zhigang Shi <Zhigang.Shi@liteon.com>
>> +
>> +description: |
>> +  Ambient sensing with an i2c interface.
>> +
>> +properties:
>> +  compatible:
>> +    enum:
>> +      - liteon,ltrf216a
>> +      - ltr,ltrf216a
>> +
>> +  reg:
>> +    maxItems: 1
>> +
>> +required:
>> +  - compatible
>> +  - reg
>> +
>> +additionalProperties: false
>> +
>> +examples:
>> +  - |
>> +    i2c {
>> +
>> +        #address-cells = <1>;
>> +        #size-cells = <0>;
>> +
>> +        light-sensor@53 {
>> +                compatible = "ltr,ltrf216a";
>> +                reg = <0x53>;
>> +        };
>> +    };
>> +...
>

-- 
Gabriel Krisman Bertazi

  reply	other threads:[~2022-03-28  2:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-25 10:30 [PATCH 0/3] Add LTRF216A Driver Shreeya Patel
2022-03-25 10:30 ` [PATCH 1/3] dt-bindings: vendor-prefixes: Add 'ltr' as deprecated vendor prefix Shreeya Patel
2022-03-25 12:21   ` Krzysztof Kozlowski
2022-03-25 10:30 ` [PATCH 2/3] dt-bindings: Document ltrf216a light sensor bindings Shreeya Patel
2022-03-25 12:23   ` Krzysztof Kozlowski
2022-03-27 13:55   ` Jonathan Cameron
2022-03-28  2:49     ` Gabriel Krisman Bertazi [this message]
2022-03-25 10:30 ` [PATCH 3/3] iio: light: Add support for ltrf216a sensor Shreeya Patel
2022-03-25 12:25   ` Krzysztof Kozlowski
2022-03-27 14:30   ` Jonathan Cameron
2022-03-29 20:03     ` Shreeya Patel
2022-04-02 16:49       ` Jonathan Cameron
2022-04-11 17:06     ` Shreeya Patel
2022-04-12 14:06       ` Gabriel Krisman Bertazi
2022-04-12 14:53         ` Jonathan Cameron
2022-03-28  3:59   ` Gabriel Krisman Bertazi

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=87czi6ssen.fsf@collabora.com \
    --to=krisman@collabora.com \
    --cc=Zhigang.Shi@liteon.com \
    --cc=alvaro.soliverez@collabora.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jic23@kernel.org \
    --cc=kernel@collabora.com \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=shreeya.patel@collabora.com \
    /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.