Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Hongyang Zhao" <hongyang.zhao@thundersoft.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH 1/2] ASoC: dt-bindings: es8316: Add regulator supplies
Date: Thu, 23 Jul 2026 08:40:42 +0000	[thread overview]
Message-ID: <20260723084042.899991F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260723-es8316-regulator-next-20260722-v1-1-721f757879a0@thundersoft.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Variant-specific supply properties are defined globally, improperly allowing them for other incompatible hardware variants covered by the same binding.
--

--- Patch [1]: [PATCH 1/2] ASoC: dt-bindings: es8316: Add regulator supplies ---
commit d435f3d7346be3dbbefc6d1734447b71df8be5a3
Author: Hongyang Zhao <hongyang.zhao@thundersoft.com>

ASoC: dt-bindings: es8316: Add regulator supplies

The ES8316 has separate AVDD, CPVDD, DVDD and PVDD supply inputs
for its analog, charge pump, digital core and digital I/O domains.
Describe all four inputs so boards can model the codec power topology.

> diff --git a/Documentation/devicetree/bindings/sound/everest,es8316.yaml b/Documentation/devicetree/bindings/sound/everest,es8316.yaml
> index fe5d938ca3102..f45f59b7b0709 100644
> --- a/Documentation/devicetree/bindings/sound/everest,es8316.yaml
> +++ b/Documentation/devicetree/bindings/sound/everest,es8316.yaml
> @@ -49,6 +49,18 @@ properties:
>      items:
>        - const: mclk
>  
> +  avdd-supply:
> +    description: Regulator providing the analog supply, from 2.0 V to 3.6 V
> +
> +  cpvdd-supply:
> +    description: Regulator providing the charge pump supply, from 1.6 V to 2.0 V

[Severity: Low]
Does defining this property globally inadvertently allow it for other
incompatible hardware variants covered by the same binding?

Since cpvdd-supply is defined at the global properties level, the schema
evaluates it as a valid optional property for all compatibles listed in the
file. This means if hardware variants like everest,es8311 and everest,es8323
lack a charge pump, the schema would silently accept cpvdd-supply in their
device tree nodes instead of properly rejecting it.

Should variant-specific supplies be guarded by an if:properties:compatible
conditional block to restrict them only to the hardware that actually supports
them?

[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260723-es8316-regulator-next-20260722-v1-0-721f757879a0@thundersoft.com?part=1

  reply	other threads:[~2026-07-23  8:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-23  7:54 [PATCH 0/2] ASoC: es8316: Add regulator support Hongyang Zhao
2026-07-23  7:54 ` [PATCH 1/2] ASoC: dt-bindings: es8316: Add regulator supplies Hongyang Zhao
2026-07-23  8:40   ` sashiko-bot [this message]
2026-07-24  9:53   ` Krzysztof Kozlowski
2026-07-30  2:26     ` Hongyang Zhao
2026-07-23  7:54 ` [PATCH 2/2] ASoC: codecs: es8316: Add regulator support Hongyang Zhao
2026-07-23  8:51   ` 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=20260723084042.899991F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=hongyang.zhao@thundersoft.com \
    --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