Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Kaustabh Chakraborty" <kauschluss@disroot.org>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v3 1/3] dt-bindings: iio: proximity: add Sharp GP2AP070S proximity sensor
Date: Thu, 30 Jul 2026 20:12:41 +0000	[thread overview]
Message-ID: <20260730201242.0F13D1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260731-gp2ap070s-v3-1-d1f5cecf9fe7@disroot.org>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The `vled-supply` property is missing from the `required` list, despite the hardware requiring it for core functionality.
--

--- Patch [1]: [PATCH v3 1/3] dt-bindings: iio: proximity: add Sharp GP2AP070S proximity sensor ---
commit a5f76b868834c635a43cd3859fdfeb8667e96336
Author: Kaustabh Chakraborty <kauschluss@disroot.org>

dt-bindings: iio: proximity: add Sharp GP2AP070S proximity sensor

This commit introduces the device tree binding for the Sharp GP2AP070S
proximity sensor. The sensor expects two voltage supplies, one for the
core and one for the infrared LED.

> diff --git a/Documentation/devicetree/bindings/iio/proximity/sharp,gp2ap070s.yaml b/Documentation/devicetree/bindings/iio/proximity/sharp,gp2ap070s.yaml
> new file mode 100644
> index 0000000000000..73f0abc1f09cb
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/proximity/sharp,gp2ap070s.yaml

[ ... ]

> +  vdd-supply:
> +    description: Voltage supply for the internal circuitry
> +
> +  vled-supply:
> +    description: Voltage supply for the IR LED
> +
> +  proximity-near-level: true
> +
> +required:
> +  - compatible
> +  - reg
> +  - interrupts
> +  - vdd-supply

[Severity: Medium]
Since the commit message indicates the hardware expects two voltage supplies,
should vled-supply also be included in this required list?

Without it, device trees missing the vled-supply property will silently pass
schema validation, which could lead to incomplete configurations.

> +
> +additionalProperties: false

[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260731-gp2ap070s-v3-0-d1f5cecf9fe7@disroot.org?part=1

  reply	other threads:[~2026-07-30 20:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-30 20:06 [PATCH v3 0/3] Add Sharp GP2AP070S Proximity Driver and enable it in Galaxy J6 (j6lte) Kaustabh Chakraborty
2026-07-30 20:07 ` [PATCH v3 1/3] dt-bindings: iio: proximity: add Sharp GP2AP070S proximity sensor Kaustabh Chakraborty
2026-07-30 20:12   ` sashiko-bot [this message]
2026-07-30 20:07 ` [PATCH v3 2/3] iio: proximity: add driver for " Kaustabh Chakraborty
2026-07-30 20:18   ` sashiko-bot
2026-07-30 20:07 ` [PATCH v3 3/3] arm64: dts: exynos7870-j6lte: add " Kaustabh Chakraborty
2026-07-30 20:19   ` sashiko-bot

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=20260730201242.0F13D1F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kauschluss@disroot.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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