From: Jonathan Cameron <jic23@kernel.org>
To: Conor Dooley <conor@kernel.org>
Cc: "Kim Seer Paller" <kimseer.paller@analog.com>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Philipp Zabel" <p.zabel@pengutronix.de>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux@analog.com, devicetree@vger.kernel.org
Subject: Re: [PATCH v4 2/4] dt-bindings: iio: dac: add adi,ad5710r.yaml
Date: Tue, 1 Sep 2026 04:14:08 +0100 [thread overview]
Message-ID: <20260901041408.06d3f7ac@jic23-huawei> (raw)
In-Reply-To: <20260831-singer-reimburse-defba31848bc@spud>
Hi Conor,
> > + adi,range-double:
> > + description:
> > + Configure the output range for all channels. If the property is present,
> > + the output will range from 0V to 2 x Vref. If the property is not present,
> > + the output will range from 0V to Vref.
>
> What was the rationale provided for this not being a userspace control?
>
Jumping in as I happen to read this...
For DACs we often do it in kernel as potentially there is a circuit dependent aspect.
In extreme case leading to the bad kind of smoke. Normally it is covered by an
output-range pair, but can't do that here as it is relative to vref (which
we have no way of knowing in the binding).
For input devices it is always a userspace thing to control.
> > + type: boolean
next prev parent reply other threads:[~2026-09-01 3:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-29 5:59 [PATCH v4 0/4] Add support for AD5710R/AD5711R DAC Kim Seer Paller
2026-08-29 5:59 ` [PATCH v4 1/4] iio: ABI: Add DAC current powerdown attributes and 15kohm_to_gnd mode Kim Seer Paller
2026-08-29 5:59 ` [PATCH v4 2/4] dt-bindings: iio: dac: add adi,ad5710r.yaml Kim Seer Paller
2026-08-31 17:04 ` Conor Dooley
2026-09-01 3:14 ` Jonathan Cameron [this message]
2026-09-01 17:45 ` Conor Dooley
2026-08-29 5:59 ` [PATCH v4 3/4] iio: dac: ad3530r: parameterize DAC resolution Kim Seer Paller
2026-08-29 5:59 ` [PATCH v4 4/4] iio: dac: ad3530r: add support for AD5710R/AD5711R Kim Seer Paller
2026-08-29 17:36 ` Jonathan Cameron
2026-08-31 7:39 ` Andy Shevchenko
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=20260901041408.06d3f7ac@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=kimseer.paller@analog.com \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@analog.com \
--cc=nuno.sa@analog.com \
--cc=p.zabel@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