From: Rob Herring <robh@kernel.org>
To: Mikael Gonella-Bolduc <mgonellabolduc@dimonoff.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
Mikael Gonella-Bolduc <m.gonella.bolduc@gmail.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
Hugo Villeneuve <hvilleneuve@dimonoff.com>,
Matti Vaittinen <mazziesaccount@gmail.com>
Subject: Re: [PATCH v4 1/2] dt-bindings: iio: light: Add APDS9160 binding
Date: Tue, 7 Jan 2025 17:29:19 -0600 [thread overview]
Message-ID: <20250107232919.GA2044181-robh@kernel.org> (raw)
In-Reply-To: <20250106-apds9160-driver-v4-1-f88d9fc45d84@dimonoff.com>
On Mon, Jan 06, 2025 at 05:23:01PM -0500, Mikael Gonella-Bolduc wrote:
> Add device tree bindings for APDS9160
> Note: Using alternate email for maintainer
>
> Signed-off-by: Mikael Gonella-Bolduc <mgonellabolduc@dimonoff.com>
> ---
> .../bindings/iio/light/brcm,apds9160.yaml | 86 ++++++++++++++++++++++
> 1 file changed, 86 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/iio/light/brcm,apds9160.yaml b/Documentation/devicetree/bindings/iio/light/brcm,apds9160.yaml
> new file mode 100644
> index 0000000000000000000000000000000000000000..756d46c2edb171da840ee49a7339cb781fe84ad2
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/light/brcm,apds9160.yaml
> @@ -0,0 +1,86 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/iio/light/brcm,apds9160.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Broadcom Combined Proximity & Ambient light sensor
> +
> +maintainers:
> + - Mikael Gonella-Bolduc <m.gonella.bolduc@gmail.com>
> +
> +description: |
> + Datasheet: https://docs.broadcom.com/docs/APDS-9160-003-DS
> +
> +properties:
> + compatible:
> + enum:
> + - brcm,apds9160
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + maxItems: 1
> +
> + vdd-supply: true
> +
> + ps-cancellation-duration:
These all need a vendor prefix.
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description: |
Don't need '|' if no formatting to preserve.
> + Proximity sensor cancellation pulse duration in half clock cycles.
> + This parameter determines a cancellation pulse duration.
But maybe this is a paragraph break. If so, blank line between
paragraphs. And '>' is more appropriate than '|' in that case.
> + The cancellation is applied in the integration phase to cancel out
> + unwanted reflected light from very near objects such as tempered glass
> + in front of the sensor.
> + minimum: 0
That's already the min being unsigned.
> + maximum: 63
> + default: 0
> +
> + ps-cancellation-current-coarse:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description: |
> + Proximity sensor crosstalk cancellation current coarse value.
> + This parameter adjust the current in steps of 60 nA up to 240 nA.
> + This parameter is used in conjunction with the cancellation duration.
> + minimum: 0
> + maximum: 4
> + default: 0
> +
> + ps-cancellation-current-fine:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description: |
> + Proximity sensor crosstalk cancellation current fine value.
> + This parameter adjust the current in steps of 2.4 nA up to 36 nA.
> + This parameter is used in conjunction with the cancellation duration.
> + minimum: 0
> + maximum: 15
> + default: 0
> +
> +required:
> + - compatible
> + - reg
> + - vdd-supply
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/interrupt-controller/irq.h>
> +
> + i2c {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + light-sensor@53 {
> + compatible = "brcm,apds9160";
> + reg = <0x53>;
> + vdd-supply = <&vdd_reg>;
> + interrupts = <29 IRQ_TYPE_EDGE_FALLING>;
> + interrupt-parent = <&pinctrl>;
> + ps-cancellation-duration = <10>;
> + ps-cancellation-current-coarse = <2>;
> + ps-cancellation-current-fine = <10>;
> + };
> + };
> +...
>
> --
> 2.34.1
>
next prev parent reply other threads:[~2025-01-07 23:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-06 22:23 [PATCH v4 0/2] Add support for Avago/Broadcom APDS9160 Mikael Gonella-Bolduc
2025-01-06 22:23 ` Mikael Gonella-Bolduc via B4 Relay
2025-01-06 22:23 ` [PATCH v4 1/2] dt-bindings: iio: light: Add APDS9160 binding Mikael Gonella-Bolduc
2025-01-06 22:23 ` Mikael Gonella-Bolduc via B4 Relay
2025-01-07 23:29 ` Rob Herring [this message]
2025-01-12 11:10 ` Jonathan Cameron
2025-01-13 14:07 ` Mikael Gonella-Bolduc
2025-01-18 11:48 ` Jonathan Cameron
2025-01-22 23:01 ` Mikael Gonella-Bolduc
2025-01-06 22:23 ` [PATCH v4 2/2] iio: light: Add APDS9160 ALS & Proximity sensor driver Mikael Gonella-Bolduc
2025-01-06 22:23 ` Mikael Gonella-Bolduc via B4 Relay
2025-01-12 11:28 ` 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=20250107232919.GA2044181-robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hvilleneuve@dimonoff.com \
--cc=jic23@kernel.org \
--cc=justinstitt@google.com \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=m.gonella.bolduc@gmail.com \
--cc=mazziesaccount@gmail.com \
--cc=mgonellabolduc@dimonoff.com \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.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.