From: Jonathan Cameron <jic23@kernel.org>
To: Andrew Davis <afd@ti.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Nikita Travkin <nikita@trvn.ru>, <linux-iio@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: iio: light: ltr501: Add liteon,ltr303
Date: Sat, 7 Mar 2026 11:37:57 +0000 [thread overview]
Message-ID: <20260307113757.69abe0f1@jic23-huawei> (raw)
In-Reply-To: <20260305195917.831104-1-afd@ti.com>
On Thu, 5 Mar 2026 13:59:17 -0600
Andrew Davis <afd@ti.com> wrote:
> This device is already supported by the driver and this compatible
> string was added to the of_device_id list but was not documented
> here in the binding, fix this.
>
Needs a brief note on why it is different enough from all other supported
devices that we can't do a fallback compatible.
Seems it has a mix of scaling and channels that doesn't match any other device.
> Signed-off-by: Andrew Davis <afd@ti.com>
> ---
> Documentation/devicetree/bindings/iio/light/liteon,ltr501.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/iio/light/liteon,ltr501.yaml b/Documentation/devicetree/bindings/iio/light/liteon,ltr501.yaml
> index c8074f180a793..ab9bb68dd7363 100644
> --- a/Documentation/devicetree/bindings/iio/light/liteon,ltr501.yaml
> +++ b/Documentation/devicetree/bindings/iio/light/liteon,ltr501.yaml
> @@ -18,6 +18,7 @@ properties:
> - liteon,ltr501
> - liteon,ltr559
> - liteon,ltr301
> + - liteon,ltr303
>
> reg:
> maxItems: 1
prev parent reply other threads:[~2026-03-07 11:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 19:59 [PATCH] dt-bindings: iio: light: ltr501: Add liteon,ltr303 Andrew Davis
2026-03-07 11:37 ` 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=20260307113757.69abe0f1@jic23-huawei \
--to=jic23@kernel.org \
--cc=afd@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nikita@trvn.ru \
--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