From: Jonathan Cameron <jic23@kernel.org>
To: "Jose A. Perez de Azpillaga" <azpijr@gmail.com>
Cc: linux-iio@vger.kernel.org,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
devicetree@vger.kernel.org
Subject: Re: [RFC PATCH v2 1/2] dt-bindings: iio: light: add Broadcom APDS9999
Date: Sat, 16 May 2026 15:47:50 +0100 [thread overview]
Message-ID: <20260516154750.176a89b0@jic23-huawei> (raw)
In-Reply-To: <438370a42f57250cbead53ac73834fbf9ccb9269.1778659152.git.azpijr@gmail.com>
On Wed, 13 May 2026 10:10:03 +0200
"Jose A. Perez de Azpillaga" <azpijr@gmail.com> wrote:
> Add Device Tree binding for the Broadcom APDS9999 ambient light
> and proximity sensor.
>
> The APDS9999 features individual R, G, B, and IR channels with
> a green channel that uses optical coating to approximate the
> human eye spectral response for ALS/lux measurements. Proximity
> and RGB functionality are not yet implemented in the driver.
State in this description a little bit of why you didn't merge it
with similar bindings.
Trivial stuff inline.
>
> Signed-off-by: Jose A. Perez de Azpillaga <azpijr@gmail.com>
> ---
> .../bindings/iio/light/brcm,apds9999.yaml | 53 +++++++++++++++++++
> MAINTAINERS | 6 +++
> 2 files changed, 59 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/iio/light/brcm,apds9999.yaml
>
> diff --git a/Documentation/devicetree/bindings/iio/light/brcm,apds9999.yaml b/Documentation/devicetree/bindings/iio/light/brcm,apds9999.yaml
> new file mode 100644
> index 000000000000..759fe0151549
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/light/brcm,apds9999.yaml
> @@ -0,0 +1,53 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/iio/light/brcm,apds9999.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +title: Broadcom APDS-9999 Digital Proximity and RGB Sensor
> +
> +maintainers:
> + - Jose A. Perez de Azpillaga <azpijr@gmail.com>
> +
> +description: |
> + Broadcom APDS-9999 is a digital proximity and RGB sensor with
> + ambient light sensing (ALS) capability. The device uses individual
> + R, G, B, and IR channels plus a VCSEL for proximity detection.
What's a VCSEL? Spell it out.
Otherwise
> +
> + Datasheet: https://docs.broadcom.com/docs/APDS-9999-DS
> +
> +properties:
> + compatible:
> + enum:
> + - brcm,apds9999
> +
> + reg:
> + maxItems: 1
> +
> + vdd-supply: true
> +
> + vled-supply:
> + description: VCSEL power supply
> +
> + interrupts:
> + maxItems: 1
> +
> +additionalProperties: false
> +
> +required:
> + - compatible
> + - reg
> + - vdd-supply
> +
> +examples:
> + - |
> + i2c {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + light-sensor@52 {
> + compatible = "brcm,apds9999";
> + reg = <0x52>;
> + vdd-supply = <&vdd_reg>;
> + vled-supply = <&vled_reg>;
> + };
> + };
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 1aa9c989973f..64c8cf2601e8 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -4302,6 +4302,12 @@ S: Maintained
> F: Documentation/devicetree/bindings/iio/light/avago,apds9300.yaml
> F: drivers/iio/light/apds9306.c
>
> +BROADCOM APDS9999 AMBIENT LIGHT SENSOR DRIVER
> +M: Jose A. Perez de Azpillaga <azpijr@gmail.com>
> +L: linux-iio@vger.kernel.org
> +S: Maintained
> +F: Documentation/devicetree/bindings/iio/light/brcm,apds9999.yaml
Sashiko pointed out this should be in alphabetical order.
Bit annoying in this particular case but we'll just find someone
else moves it if we don't do it from the start.
> +
> AVIA HX711 ANALOG DIGITAL CONVERTER IIO DRIVER
> M: Andreas Klinger <ak@it-klinger.de>
> L: linux-iio@vger.kernel.org
>
>
>
prev parent reply other threads:[~2026-05-16 14:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1778659152.git.azpijr@gmail.com>
2026-05-13 8:10 ` [RFC PATCH v2 1/2] dt-bindings: iio: light: add Broadcom APDS9999 Jose A. Perez de Azpillaga
2026-05-14 2:49 ` sashiko-bot
2026-05-16 14:47 ` Jonathan Cameron [this message]
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=20260516154750.176a89b0@jic23-huawei \
--to=jic23@kernel.org \
--cc=azpijr@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=linux-iio@vger.kernel.org \
--cc=nuno.sa@analog.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox