Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Karl Asseily" <karl@asseily.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v3 2/4] ASoC: dt-bindings: add ESS Technology ES9039Q2M
Date: Fri, 18 Sep 2026 03:20:47 +0000	[thread overview]
Message-ID: <20260918032047.F217F1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260918031326.68542-3-karl@asseily.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] dt-bindings: esstech,es9039q2m: missing power supply properties
--

commit 319b6af08837af1db6a259282cc4b550059341ed
Author: Karl Asseily <karl@asseily.com>

ASoC: dt-bindings: add ESS Technology ES9039Q2M

Add a binding for the ES9039Q2M, a 32-bit two-channel audio DAC with an
asynchronous sample rate converter.

> diff --git a/Documentation/devicetree/bindings/sound/esstech,es9039q2m.yaml b/Documentation/devicetree/bindings/sound/esstech,es9039q2m.yaml
> new file mode 100644
> index 0000000000000..c1d03d3a85527
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/sound/esstech,es9039q2m.yaml
[ ... ]
> +properties:
> +  compatible:
> +    const: esstech,es9039q2m
> +
> +  reg:
> +    description:
> +      I2C address, selected by the ADDR0 and ADDR1 pins - 0x48, 0x49, 0x4a or
> +      0x4b for GND/GND, GND/AVDD, AVDD/GND and AVDD/AVDD respectively.

[Severity: Medium]
Should there be a property for the AVDD power supply in this binding?

The description explicitly mentions the AVDD pin, confirming the hardware
utilizes power supplies that are not modeled as properties in the schema.
Without them, device trees cannot properly model the analogue and digital power
supplies of the hardware.

If the supplies are dynamically managed, the lack of properties prevents
describing this topology, potentially leaving the device unpowered on systems
where the bootloader does not leave them enabled. Adding them as required
properties later would break backward compatibility with device trees written
against this initial schema.

> +    enum: [ 0x48, 0x49, 0x4a, 0x4b ]
> +
> +  clocks:
> +    maxItems: 1

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260918031326.68542-1-karl@asseily.com?part=2

  reply	other threads:[~2026-09-18  3:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-18  3:13 [PATCH v3 0/4] ASoC: add ESS Technology ES9039Q2M codec driver Karl Asseily
2026-09-18  3:13 ` [PATCH v3 1/4] dt-bindings: vendor-prefixes: add ESS Technology Karl Asseily
2026-09-18 17:27   ` Rob Herring
2026-09-18  3:13 ` [PATCH v3 2/4] ASoC: dt-bindings: add ESS Technology ES9039Q2M Karl Asseily
2026-09-18  3:20   ` sashiko-bot [this message]
2026-09-18 17:29   ` Rob Herring
2026-09-18  3:13 ` [PATCH v3 3/4] ASoC: es9039q2m: add ESS Technology ES9039Q2M codec driver Karl Asseily
2026-09-18  3:24   ` sashiko-bot
2026-09-18 18:27     ` Karl Asseily
2026-09-18 10:46   ` Mark Brown
2026-09-18 10:59     ` Karl Asseily
2026-09-18 11:23       ` Mark Brown
2026-09-18  3:13 ` [PATCH v3 4/4] MAINTAINERS: add entry for the " Karl Asseily

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=20260918032047.F217F1F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=karl@asseily.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