From: Dharma Balasubiramani <dharma.b@microchip.com>
To: Mikael Gonella-Bolduc <m.gonella.bolduc@gmail.com>,
Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
<linux-iio@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Dharma Balasubiramani <dharma.b@microchip.com>
Subject: [PATCH] dt-bindings: iio: light: fix missing type definition
Date: Wed, 5 Feb 2025 09:48:45 +0530 [thread overview]
Message-ID: <20250205-brcm-binding-v1-1-a996a840d2d6@microchip.com> (raw)
Add the missing type definition for ps-cancellation-current-picoamp property.
Fixes: 47736b32d1b8 ("dt-bindings: iio: light: Add APDS9160 binding")
Signed-off-by: Dharma Balasubiramani <dharma.b@microchip.com>
---
Documentation/devicetree/bindings/iio/light/brcm,apds9160.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/iio/light/brcm,apds9160.yaml b/Documentation/devicetree/bindings/iio/light/brcm,apds9160.yaml
index bb1cc4404a55..f9c35c29fe04 100644
--- a/Documentation/devicetree/bindings/iio/light/brcm,apds9160.yaml
+++ b/Documentation/devicetree/bindings/iio/light/brcm,apds9160.yaml
@@ -37,6 +37,7 @@ properties:
maximum: 63
ps-cancellation-current-picoamp:
+ $ref: /schemas/types.yaml#/definitions/uint32
description:
Proximity sensor crosstalk cancellation current in picoampere.
This parameter adjusts the current in steps of 2400 pA up to 276000 pA.
---
base-commit: 40b8e93e17bff4a4e0cc129e04f9fdf5daa5397e
change-id: 20250205-brcm-binding-71b6d990d67e
Best regards,
--
Dharma Balasubiramani <dharma.b@microchip.com>
next reply other threads:[~2025-02-05 4:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 4:18 Dharma Balasubiramani [this message]
2025-02-05 11:37 ` [PATCH] dt-bindings: iio: light: fix missing type definition Krzysztof Kozlowski
2025-02-06 2:41 ` Dharma.B
2025-02-06 7:38 ` Krzysztof Kozlowski
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=20250205-brcm-binding-v1-1-a996a840d2d6@microchip.com \
--to=dharma.b@microchip.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.gonella.bolduc@gmail.com \
--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