Devicetree
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Piyush Patle <piyushpatle228@gmail.com>
Cc: ak@it-klinger.de, andriy.shevchenko@linux.intel.com,
	dlechner@baylibre.com, nuno.sa@analog.com, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 v8 02/11] dt-bindings: iio: adc: hx711: add VSUP supply property
Date: Wed, 20 May 2026 11:01:49 +0100	[thread overview]
Message-ID: <20260520110149.4086c934@jic23-huawei> (raw)
In-Reply-To: <CAMB+xkaOEVbc=nO0nSODJC6cmbGiXZ9C+WA8NEY8Lhj=3c89JQ@mail.gmail.com>

On Tue, 19 May 2026 02:47:44 +0530
Piyush Patle <piyushpatle228@gmail.com> wrote:

> On Tue, May 12, 2026 at 5:38 PM Jonathan Cameron <jic23@kernel.org> wrote:
> >
> > On Tue, 12 May 2026 13:06:22 +0100
> > Jonathan Cameron <jic23@kernel.org> wrote:
> >  
> > > On Mon, 11 May 2026 23:13:27 +0530
> > > Piyush Patle <piyushpatle228@gmail.com> wrote:
> > >  
> > > > Document the optional VSUP supply used by the HX711 on-chip regulator.
> > > >
> > > > Signed-off-by: Piyush Patle <piyushpatle228@gmail.com>
> > > > Reviewed-by: Andy Shevchenko <andriy.shevchenko@intel.com>
> > > > Acked-by: Conor Dooley <conor.dooley@microchip.com>
> > > > ---  
> > >
> > > I got curious given the driver doesn't yet turn this on and wanted
> > > to just sanity check it via a datasheet.
> > >
> > > Why are we including this one but not dvdd-supply?  The suggested
> > > wiring does connect them to the same supply but it's external to the
> > > chip so in theory they might not be.  Curiously dvdd supply is allowed
> > > to be 0.1 V lower than vsup-supply.  
> The HX711 does have a DVDD pin, but it is the output of the internal
> LDO and is normally just bypassed to ground. VSUP is the rail supplied by
> the board, so that was the one I documented here.

Not according to the diagram in figure 1 of
https://cdn.sparkfun.com/datasheets/Sensors/ForceFlex/hx711_english.pdf

That clearly shows DVDD connected to same input supply as VSUP.
There is a note in there to say that if the internal regulator is not
used VSUP should always be connected to the higher of DVDD and AVDD.


> That said, dvdd-supply is already allowed for HX711 nodes by patch 04,
> as only vref-supply is forbidden for HX711. So the binding does not block
> a board from describing DVDD if needed.

Agreed you add it later, but it should be in this patch that is adding missing
dt-bindings for the existing part.

> The driver does not use DVDD for HX711 today, but explicit support can be
> added later if there is a real user for it.

We should make dt-bindings complete.  That doesn't mean the driver has to
use them though!

Hence I'd like to see dvdd added in this patch rather than later with
a statement of why it is used for the hx711.  As far as I can tell it should
really be required and documented as a bug in the original binding.

Jonathan


> >
> > I should have said, given there is nothing wrong with what you have here
> > and the above is a possible additional change - applied to the testing
> > branch of iio.git.
> >
> > Thanks,
> >
> > Jonathan
> >  
> Thanks for applying patches 01-03.
> > >  
> > > >  Documentation/devicetree/bindings/iio/adc/avia-hx711.yaml | 4 ++++
> > > >  1 file changed, 4 insertions(+)
> > > >
> > > > diff --git a/Documentation/devicetree/bindings/iio/adc/avia-hx711.yaml b/Documentation/devicetree/bindings/iio/adc/avia-hx711.yaml
> > > > index 1ea60dff98d5..a8eaa1f18de5 100644
> > > > --- a/Documentation/devicetree/bindings/iio/adc/avia-hx711.yaml
> > > > +++ b/Documentation/devicetree/bindings/iio/adc/avia-hx711.yaml
> > > > @@ -33,6 +33,10 @@ properties:
> > > >      description:
> > > >        Analog supply voltage (AVDD).
> > > >
> > > > +  vsup-supply:
> > > > +    description:
> > > > +      Supply voltage for the on-chip regulator (VSUP).
> > > > +
> > > >    clock-frequency:
> > > >      description:
> > > >        Controls the SCK bit-bang timing. The value is used to derive the  
> > >  
> >  
> 


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

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-11 17:43 [PATCH v8 00/11] iio: adc: hx711: add HX710B support Piyush Patle
2026-05-11 17:43 ` [PATCH v8 v8 01/11] dt-bindings: iio: adc: hx711: clean up existing binding text Piyush Patle
2026-05-12 12:05   ` Jonathan Cameron
2026-05-11 17:43 ` [PATCH v8 v8 02/11] dt-bindings: iio: adc: hx711: add VSUP supply property Piyush Patle
2026-05-12 12:06   ` Jonathan Cameron
2026-05-12 12:08     ` Jonathan Cameron
2026-05-18 21:17       ` Piyush Patle
2026-05-20 10:01         ` Jonathan Cameron [this message]
2026-05-11 17:43 ` [PATCH v8 v8 03/11] dt-bindings: iio: adc: hx711: add RATE GPIO property Piyush Patle
2026-05-12 12:08   ` Jonathan Cameron
2026-05-11 17:43 ` [PATCH v8 v8 04/11] dt-bindings: iio: adc: hx711: add HX710B support Piyush Patle
2026-05-12 12:13   ` Jonathan Cameron
2026-05-12 22:34   ` sashiko-bot
2026-05-11 17:43 ` [PATCH v8 v8 05/11] iio: adc: hx711: move scale computation to per-device storage Piyush Patle
2026-05-12 12:14   ` Jonathan Cameron
2026-05-11 17:43 ` [PATCH v8 v8 06/11] iio: adc: hx711: introduce hx711_chip_info structure Piyush Patle
2026-05-12 12:19   ` Jonathan Cameron
2026-05-18 21:26     ` Piyush Patle
2026-05-12 23:30   ` sashiko-bot
2026-05-11 17:43 ` [PATCH v8 v8 07/11] iio: adc: hx711: pass trailing pulse count into hx711_read Piyush Patle
2026-05-11 17:43 ` [PATCH v8 v8 08/11] iio: adc: hx711: split variable assignments in hx711_read and hx711_reset Piyush Patle
2026-05-11 17:43 ` [PATCH v8 v8 09/11] iio: adc: hx711: localize loop iterators in hx711_read Piyush Patle
2026-05-11 17:43 ` [PATCH v8 v8 10/11] iio: adc: hx711: pass iio_chan_spec to hx711_reset_read Piyush Patle
2026-05-12 12:21   ` Jonathan Cameron
2026-05-11 17:43 ` [PATCH v8 v8 11/11] iio: adc: hx711: add support for HX710B Piyush Patle
2026-05-12 12:38   ` Jonathan Cameron
2026-05-18 21:30     ` Piyush Patle
2026-05-13  1:13   ` 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=20260520110149.4086c934@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=ak@it-klinger.de \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=piyushpatle228@gmail.com \
    --cc=robh@kernel.org \
    /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