Linux Hardware Monitor development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: florin.leotescu@oss.nxp.com
Cc: linux-hwmon@vger.kernel.org
Subject: Re: [PATCH v7 2/3] dt-bindings: hwmon: emc2305: Add fan-shutdown-percent property
Date: Wed, 29 Apr 2026 08:09:38 +0000	[thread overview]
Message-ID: <20260429080939.C291BC19425@smtp.kernel.org> (raw)
In-Reply-To: <20260429065955.2113012-3-florin.leotescu@oss.nxp.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The `fan-shutdown-percent` property is redefined locally in the emc2305 binding instead of being moved to the common fan schema.
--

commit 0de7c28110f8526177da5d5c1903c8b485eec6ec
Author: Florin Leotescu <florin.leotescu@nxp.com>

dt-bindings: hwmon: emc2305: Add fan-shutdown-percent property

The EMC2305 fan controller supports multiple independent PWM fan
outputs. Some systems require fans to enter a defined safe state
during system shutdown or reboot handoff.

> diff --git a/Documentation/devicetree/bindings/hwmon/microchip,emc2305.yaml b/Documentation/devicetree/bindings/hwmon/microchip,emc2305.yaml
> index d3f06ebc19fa..8c2548539d7f 100644
> --- a/Documentation/devicetree/bindings/hwmon/microchip,emc2305.yaml
> +++ b/Documentation/devicetree/bindings/hwmon/microchip,emc2305.yaml
> @@ -54,6 +54,12 @@ patternProperties:
>            The fan number used to determine the associated PWM channel.
>          maxItems: 1
>  
> +      fan-shutdown-percent:

This isn't a bug, but should this property be moved to the common fan
schema instead of being defined locally here?

The fan-shutdown-percent property already exists in
Documentation/devicetree/bindings/hwmon/pwm-fan.yaml to represent the same
hardware behavior. Unifying this property in fan-common.yaml would prevent
schema fragmentation and serve as a single source of truth, especially since
microchip,emc2305.yaml already references fan-common.yaml# for its child
nodes.

> +        description:
> +          PWM duty cycle in percent applied to the fan during shutdown.
> +        minimum: 0
> +        maximum: 100
> +

[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260429065955.2113012-1-florin.leotescu@oss.nxp.com?part=2

  reply	other threads:[~2026-04-29  8:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-29  6:59 [PATCH v7 0/3] Support configurable fan PWM at shutdown florin.leotescu
2026-04-29  6:59 ` [PATCH v7 1/3] hwmon: emc2305: Fix fan channel index handling florin.leotescu
2026-04-29  7:48   ` sashiko-bot
2026-04-30 23:13   ` Guenter Roeck
2026-04-29  6:59 ` [PATCH v7 2/3] dt-bindings: hwmon: emc2305: Add fan-shutdown-percent property florin.leotescu
2026-04-29  8:09   ` sashiko-bot [this message]
2026-04-29 18:18   ` Conor Dooley
2026-04-30 12:02     ` Florin Leotescu
2026-04-30 18:53       ` Conor Dooley
2026-04-30 23:14   ` Guenter Roeck
2026-04-29  6:59 ` [PATCH v7 3/3] hwmon: emc2305: Support configurable fan PWM at shutdown florin.leotescu
2026-04-29  8:48   ` sashiko-bot
2026-04-30 23:17   ` Guenter Roeck

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=20260429080939.C291BC19425@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=florin.leotescu@oss.nxp.com \
    --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