From: Conor Dooley <conor@kernel.org>
To: sashiko@lists.linux.dev
Cc: Piyush Patle <piyushpatle228@gmail.com>,
krzk+dt@kernel.org, robh@kernel.org, devicetree@vger.kernel.org,
conor+dt@kernel.org
Subject: Re: [PATCH v7 04/11] dt-bindings: iio: adc: hx711: add HX710B support
Date: Tue, 12 May 2026 17:51:20 +0100 [thread overview]
Message-ID: <20260512-frantic-finch-2b268bed4e15@spud> (raw)
In-Reply-To: <20260511215430.4441FC2BCF5@smtp.kernel.org>
[-- Attachment #1: Type: text/plain, Size: 2565 bytes --]
On Mon, May 11, 2026 at 09:54:29PM +0000, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Medium] The `dvdd-supply` property is incorrectly permitted for the older HX711 variant, violating the intended hardware constraints and contradicting the commit message.
> --
>
> commit b2ce63274d21d343a80ad3dfc6983d09ccc4fbdc
> Author: Piyush Patle <piyushpatle228@gmail.com>
>
> dt-bindings: iio: adc: hx711: add HX710B support
>
> This adds the avia,hx710b compatible string and documents the hx710b-specific
> dvdd and vref supplies. It also adds constraints to forbid hx711-only
> properties on hx710b nodes and requires vref-supply for hx710b.
>
> > diff --git a/Documentation/devicetree/bindings/iio/adc/avia-hx711.yaml b/Documentation/devicetree/bindings/iio/adc/avia-hx711.yaml
> > index 9134bbe413796..b2b5c7bdf05e6 100644
> > --- a/Documentation/devicetree/bindings/iio/adc/avia-hx711.yaml
> > +++ b/Documentation/devicetree/bindings/iio/adc/avia-hx711.yaml
>
> [ ... ]
>
> > @@ -44,6 +49,17 @@ properties:
> > RATE pin state is determined by the board wiring.
> > maxItems: 1
> >
> > + dvdd-supply:
> > + description:
> > + Digital supply voltage (DVDD). For the HX710B, DVDD must be
> > + greater than or equal to AVDD. When DVDD is a battery rail and
> > + AVDD is a regulated supply, one channel monitors the DVDD-AVDD
> > + difference for battery level detection.
> > +
> > + vref-supply:
> > + description:
> > + Reference voltage input (VREF).
> > +
> > clock-frequency:
>
> [ ... ]
>
> > @@ -53,6 +69,21 @@ properties:
> > maximum: 2500000
> > default: 400000
> >
> > +allOf:
> > + - if:
> > + properties:
> > + compatible:
> > + const: avia,hx710b
> > + then:
> > + properties:
> > + vsup-supply: false
> > + rate-gpios: false
> > + required:
> > + - vref-supply
> > + else:
> > + properties:
> > + vref-supply: false
>
> The commit message states the intention to document the hx710b-specific dvdd
> and vref supplies.
>
> Since dvdd-supply is defined in the top-level properties block, does this
> else clause also need to forbid dvdd-supply for the older avia,hx711 variant?
>
> Currently, omitting dvdd-supply: false permits the property for the older
> hx711 variant. Should dvdd-supply: false be added here?
Seemingly no, hx711 schematic has a dvdd.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
parent reply other threads:[~2026-05-12 16:51 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20260511215430.4441FC2BCF5@smtp.kernel.org>]
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=20260512-frantic-finch-2b268bed4e15@spud \
--to=conor@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=piyushpatle228@gmail.com \
--cc=robh@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