Linux Hardware Monitor development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Nuno Sá via B4 Relay" <devnull+nuno.sa.analog.com@kernel.org>
Cc: linux-hwmon@vger.kernel.org
Subject: Re: [PATCH v13 1/3] dt-bindings: hwmon: Document the LTC4283 Swap Controller
Date: Sat, 02 May 2026 10:05:35 +0000	[thread overview]
Message-ID: <20260502100535.DD16FC19425@smtp.kernel.org> (raw)
In-Reply-To: <20260502-ltc4283-support-v13-1-1c206542e652@analog.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The `dependencies` block forces `adi,pgio4-func` to be explicitly defined when external fault properties are used, breaking its default value semantics.
--

commit 95d75c53b856792667507b1a119fd7e090fe8173
Author: Nuno Sá <nuno.sa@analog.com>

dt-bindings: hwmon: Document the LTC4283 Swap Controller

This commit introduces device tree binding documentation for the LTC4283
negative voltage hot swap controller. It also updates the MAINTAINERS file
with the new binding document.

> diff --git a/Documentation/devicetree/bindings/hwmon/adi,ltc4283.yaml b/Documentation/devicetree/bindings/hwmon/adi,ltc4283.yaml
> new file mode 100644
> index 000000000000..05e2132ad4d8
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/hwmon/adi,ltc4283.yaml
> @@ -0,0 +1,272 @@

[ ... ]

> +  adi,pgio4-func:
> +    description: Configures the function of the PGIO4 pin.
> +    $ref: /schemas/types.yaml#/definitions/string
> +    enum: [inverted_external_fault, external_fault, gpio]
> +    default: inverted_external_fault

[ ... ]

> +dependencies:

[ ... ]

> +  adi,external-fault-retry-enable:
> +    - adi,pgio4-func
> +  adi,external-fault-fet-off-enable:
> +    - adi,pgio4-func

Does this dependencies block cause a regression for device trees that rely on
the default value of adi,pgio4-func?

Because adi,pgio4-func defines a default value of "inverted_external_fault"
above, omitting it from a node is perfectly valid. However, standard JSON
schema dependencies check for the literal presence of the key in the instance.

If a device tree defines adi,external-fault-retry-enable but omits
adi,pgio4-func to rely on the default value, schema validation will fail.

Since the allOf block already rejects conflicting configurations (such as when
adi,pgio4-func is set to "gpio"), could these dependency requirements be
removed to allow device trees to safely use the default value?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260502-ltc4283-support-v13-0-1c206542e652@analog.com?part=1

  reply	other threads:[~2026-05-02 10:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-02  9:56 [PATCH v13 0/3] hwmon: Add support for the LTC4283 Hot Swap Controller Nuno Sá via B4 Relay
2026-05-02  9:56 ` [PATCH v13 1/3] dt-bindings: hwmon: Document the LTC4283 " Nuno Sá via B4 Relay
2026-05-02 10:05   ` sashiko-bot [this message]
2026-05-02  9:56 ` [PATCH v13 2/3] hwmon: ltc4283: Add support for " Nuno Sá via B4 Relay
2026-05-02 10:43   ` sashiko-bot
2026-05-02 16:21     ` Guenter Roeck
2026-05-04  9:51       ` Nuno Sá
2026-05-02  9:56 ` [PATCH v13 3/3] gpio: gpio-ltc4283: " Nuno Sá via B4 Relay
2026-05-02 11:02   ` 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=20260502100535.DD16FC19425@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=devnull+nuno.sa.analog.com@kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=sashiko@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