public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: "Conor Dooley" <conor@kernel.org>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	kernel@pengutronix.de, linux-kernel@vger.kernel.org,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	"Andy Shevchenko" <andy@kernel.org>,
	"David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"David Jander" <david@protonic.nl>
Subject: Re: [PATCH v1 2/8] dt-bindings: iio: dac: maxim,ds4424: add maxim,rfs-ohms property
Date: Sun, 25 Jan 2026 10:22:07 +0000	[thread overview]
Message-ID: <20260125102207.37ce3501@jic23-huawei> (raw)
In-Reply-To: <aXNHeq9Fi1Ldf-oE@pengutronix.de>

On Fri, 23 Jan 2026 11:03:38 +0100
Oleksij Rempel <o.rempel@pengutronix.de> wrote:

> On Fri, Jan 23, 2026 at 09:28:19AM +0000, Jonathan Cameron wrote:
> > On Mon, 19 Jan 2026 18:27:52 +0000
> > Conor Dooley <conor@kernel.org> wrote:
> >   
> > > On Mon, Jan 19, 2026 at 07:24:18PM +0100, Oleksij Rempel wrote:  
> > > > Introduce the 'maxim,rfs-ohms' property. The full-scale output current
> > > > of these DACs is determined by external resistors (Rfs) connected to
> > > > the FS pins. The driver requires the physical resistance values to
> > > > calculate the correct current scale (Amps per step) for the IIO
> > > > subsystem.
> > > > 
> > > > Keep it optional to avoid forcing updates of existing DTs; without it
> > > > the driver cannot derive a correct IIO scale.    
> > > 
> > > I don't really follow the logic here, if the driver doesn't work
> > > properly without it, shouldn't it be a required property even if that
> > > means existing devicetrees get new warnings? Warnings are preferable to
> > > the drivers malfunctioning on those devices, after all!  
> > 
> > Agreed. The driver can paper over holes or I guess we could provide a default
> > if the datasheet has some reference value or similar?    
> 
> No, this DAC controls the current. The current range is application specific and
> defined by the load resistors. Is it better to not provide scale if this
> information not available, guessing it will make things worse and
> potentially damage some HW.
> 
Then does this need to be a fix on the driver side?
Or are you just suggesting not proving the scale if we don't have enough info?
That's fine if so.

> > DT binding should require it.  
> 
> ACK


  reply	other threads:[~2026-01-25 10:22 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-19 18:24 [PATCH v1 0/8] iio: dac: ds4424: add DS4402/DS4404 support and scale Oleksij Rempel
2026-01-19 18:24 ` [PATCH v1 1/8] dt-bindings: iio: dac: maxim,ds4424: add ds4402/ds4404 Oleksij Rempel
2026-01-19 18:28   ` Conor Dooley
2026-01-19 18:24 ` [PATCH v1 2/8] dt-bindings: iio: dac: maxim,ds4424: add maxim,rfs-ohms property Oleksij Rempel
2026-01-19 18:27   ` Conor Dooley
2026-01-23  9:28     ` Jonathan Cameron
2026-01-23 10:03       ` Oleksij Rempel
2026-01-25 10:22         ` Jonathan Cameron [this message]
2026-01-26  9:54           ` Oleksij Rempel
2026-01-20 10:39   ` Krzysztof Kozlowski
2026-01-19 18:24 ` [PATCH v1 3/8] iio: dac: ds4424: add DS4402/DS4404 device IDs Oleksij Rempel
2026-01-19 18:24 ` [PATCH v1 4/8] iio: dac: ds4424: reject -128 RAW value Oleksij Rempel
2026-01-19 19:03   ` Andy Shevchenko
2026-01-23  9:33     ` Jonathan Cameron
2026-01-26  9:52       ` Oleksij Rempel
2026-01-19 18:24 ` [PATCH v1 5/8] iio: dac: ds4424: add Rfs-based scale and per-variant limits Oleksij Rempel
2026-01-19 19:11   ` Andy Shevchenko
2026-01-19 18:24 ` [PATCH v1 6/8] iio: dac: ds4424: clear outputs on probe Oleksij Rempel
2026-01-19 19:12   ` Andy Shevchenko
2026-01-23  9:38   ` Jonathan Cameron
2026-01-23  9:59     ` Oleksij Rempel
2026-01-19 18:24 ` [PATCH v1 7/8] iio: dac: ds4424: ratelimit read errors and use device context Oleksij Rempel
2026-01-19 19:14   ` Andy Shevchenko
2026-01-19 18:24 ` [PATCH v1 8/8] iio: dac: ds4424: document output sign and probe verification Oleksij Rempel

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=20260125102207.37ce3501@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=andy@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=conor@kernel.org \
    --cc=david@protonic.nl \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=o.rempel@pengutronix.de \
    --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