devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Lechner <dlechner@baylibre.com>
To: Mariel Tinaco <Mariel.Tinaco@analog.com>
Cc: linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	 linux-kernel@vger.kernel.org,
	Jonathan Cameron <jic23@kernel.org>,
	 Lars-Peter Clausen <lars@metafoo.de>,
	Rob Herring <robh@kernel.org>,
	 Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	 Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>,
	 Michael Hennerich <Michael.Hennerich@analog.com>,
	Marcelo Schmitt <marcelo.schmitt1@gmail.com>,
	 Dimitri Fedrau <dima.fedrau@gmail.com>,
	Guenter Roeck <linux@roeck-us.net>
Subject: Re: [PATCH 0/2] add AD8460 DAC driver
Date: Fri, 10 May 2024 12:30:46 -0500	[thread overview]
Message-ID: <CAMknhBHd2XCJH4rgYDq=vbCL5E_tM3FxFPWbNy9PvxLCJL4tcA@mail.gmail.com> (raw)
In-Reply-To: <20240510064053.278257-1-Mariel.Tinaco@analog.com>

On Fri, May 10, 2024 at 1:42 AM Mariel Tinaco <Mariel.Tinaco@analog.com> wrote:
>
> The AD8460 is a 14-bit, high power +-40V 1A, high-speed DAC,
> with dual digital input modes, programmable supply current and
> fault monitoring and protection settings for output current,
> output voltage and junction temperature.
>
> The fault monitoring and shutdown protection features were
> supported in the earlier versions of the IIO driver but was
> scrapped due to uncertainties if the functionalities belong to
> the IIO driver. However, it would be best to implement it for
> the device's quality of life. I'd like to know if it's better
> suited as a stand-alone HWMON driver.
>
> The following are the configurable and readable parameters
> through SPI that could be implemented on the HWMON driver:
>   * An enable bit to arm/protect the device on overcurrent,
> overvoltage or overtemperature events. The device is shut down
> upon detection.
>   * A configurable range/threshold for voltage, current and
> temperature that raises alarm when exceeded while the device is
> armed.
>   * Flags that can be polled to raise alarm upon detection of
> overcurrent, overvoltage or overtemperature events, and apply
> additional protective measures.
>   * Programmable quiescent current (optional)
>   * Thermal monitoring is done by measuring voltage on TMP pin
> (unlikely to be included)
>

Adding myself to the cc: here since I'm interested to see what
Jonathan (or anyone else) has to say about the fault monitoring.

  parent reply	other threads:[~2024-05-10 17:30 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-10  6:40 [PATCH 0/2] add AD8460 DAC driver Mariel Tinaco
2024-05-10  6:40 ` [PATCH 1/2] dt-bindings: iio: dac: add docs for ad8460 Mariel Tinaco
2024-05-10  7:21   ` Rob Herring (Arm)
2024-05-10 17:28   ` David Lechner
2024-05-11 16:25     ` Jonathan Cameron
2024-05-11 18:47       ` David Lechner
2024-05-21  7:07         ` Nuno Sá
2024-06-24  4:20       ` Tinaco, Mariel
2024-05-10  6:40 ` [PATCH 2/2] iio: dac: support the ad8460 Waveform DAC Mariel Tinaco
2024-05-10 17:30   ` David Lechner
2024-05-11 16:44   ` Jonathan Cameron
2024-06-24  4:19     ` Tinaco, Mariel
2024-06-28 18:45       ` Jonathan Cameron
2024-07-08  5:17         ` Tinaco, Mariel
2024-07-08 16:05           ` Jonathan Cameron
2024-07-11  9:20             ` Nuno Sá
2024-07-11 21:31               ` David Lechner
2024-07-12  6:57                 ` Nuno Sá
2024-07-13  9:57                   ` Jonathan Cameron
2024-07-14  6:17                     ` Nuno Sá
2024-06-24  4:56     ` Tinaco, Mariel
2024-06-28 18:51       ` Jonathan Cameron
2024-07-07 23:32         ` Tinaco, Mariel
2024-07-07 23:37           ` Tinaco, Mariel
2024-05-10 17:30 ` David Lechner [this message]
2024-05-11 16:21   ` [PATCH 0/2] add AD8460 DAC driver Jonathan Cameron
2024-06-24  4:38     ` Tinaco, Mariel
2024-06-28 18:39       ` Jonathan Cameron
2024-07-07 23:29         ` Tinaco, Mariel

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='CAMknhBHd2XCJH4rgYDq=vbCL5E_tM3FxFPWbNy9PvxLCJL4tcA@mail.gmail.com' \
    --to=dlechner@baylibre.com \
    --cc=Mariel.Tinaco@analog.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dima.fedrau@gmail.com \
    --cc=jic23@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=lars@metafoo.de \
    --cc=lgirdwood@gmail.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=marcelo.schmitt1@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;
as well as URLs for NNTP newsgroup(s).