All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jose A. Perez de Azpillaga" <azpijr@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: linux-iio@vger.kernel.org,
	"David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <nuno.sa@analog.com>
Subject: Re: [RFC 1/4] dt-bindings: iio: light: add DT binding for Broadcom APDS9999
Date: Mon, 11 May 2026 17:28:19 +0200	[thread overview]
Message-ID: <agHzqPiGttkJtTMz@gmail.com> (raw)
In-Reply-To: <20260511132635.7f0855c4@jic23-huawei>

On Mon, May 11, 2026 at 01:26:35PM +0100, Jonathan Cameron wrote:
> On Mon, 11 May 2026 12:14:44 +0200
> "Jose A. Perez de Azpillaga" <azpijr@gmail.com> wrote:
>
> Title doesn't need to mention binding twice.

I will fix it in v2.

> dt-bindings: iio: light: add Broadcomm ADPS9999
>
> > Add Device Tree binding documentation for the Broadcom APDS9999
> > ambient light sensor.
> >
> > Proximity and RGB features are not yet implemented in the driver
> > and therefore not included in this binding.
> >
> > Signed-off-by: Jose A. Perez de Azpillaga <azpijr@gmail.com>
>
> Can you combine this with the existing avago,apds9300.yaml binding?
> Other than the missing interrupt in this file they look identical.
>
> Note that a separate driver doesn't necessarily need a separate binding
> doc.  May not be worth doing given the extra supply this part takes
> (which you are currently missing by the look of it)

the VCSEL supply and required vdd-supply make a combined binding messy
with conditional schemas. keeping it separate.

...

> Power supply should be required

noted for v2.

> Also you need to fully describe the part where possible. Here there
> is an interrupt and a vcsel-supply by the look of it.

okay, I'll address everything said in v2.

--
jose a. p-a

  reply	other threads:[~2026-05-11 15:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-11 10:14 [RFC 0/4] iio: light: add driver for Broadcom APDS9999 Jose A. Perez de Azpillaga
2026-05-11 10:14 ` [RFC 1/4] dt-bindings: iio: light: add DT binding " Jose A. Perez de Azpillaga
2026-05-11 12:26   ` Jonathan Cameron
2026-05-11 15:28     ` Jose A. Perez de Azpillaga [this message]
2026-05-11 10:14 ` [RFC 2/4] iio: light: add support for APDS9999 sensor Jose A. Perez de Azpillaga
2026-05-11 13:06   ` Jonathan Cameron
2026-05-11 16:14     ` Jose A. Perez de Azpillaga
2026-05-11 10:14 ` [RFC 3/4] iio: light: add build support for APDS9999 Jose A. Perez de Azpillaga
2026-05-11 12:28   ` Jonathan Cameron
2026-05-11 15:30     ` Jose A. Perez de Azpillaga
2026-05-11 10:14 ` [RFC 4/4] MAINTAINERS: add myself as APDS9999 maintainer Jose A. Perez de Azpillaga
2026-05-11 12:29   ` Jonathan Cameron
2026-05-11 15:33     ` Jose A. Perez de Azpillaga
2026-05-11 12:21 ` [RFC 0/4] iio: light: add driver for Broadcom APDS9999 Jonathan Cameron
2026-05-11 15:19   ` Jose A. Perez de Azpillaga
2026-05-11 15:53     ` Jonathan Cameron
2026-05-11 16:19       ` Jose A. Perez de Azpillaga

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=agHzqPiGttkJtTMz@gmail.com \
    --to=azpijr@gmail.com \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --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 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.