diff options
| author | Rasmus Villemoes <linux@rasmusvillemoes.dk> | 2022-11-15 10:55:17 +0100 |
|---|---|---|
| committer | Jonathan Cameron <Jonathan.Cameron@huawei.com> | 2022-11-23 20:54:37 +0000 |
| commit | f237cf1914e24ebba88670ecc36e8209c888c9a2 (patch) | |
| tree | 0110cb81d0e16f9d45ff3279e8206140ff99f1d2 /drivers/iio/test | |
| parent | 6aaf7045697aa93589bea1b33e751814b0776991 (diff) | |
| download | linux-stable-f237cf1914e24ebba88670ecc36e8209c888c9a2.tar.gz linux-stable-f237cf1914e24ebba88670ecc36e8209c888c9a2.tar.bz2 linux-stable-f237cf1914e24ebba88670ecc36e8209c888c9a2.zip | |
iio: addac: ad74413r: add support for reset-gpio
We have a board where the reset pin of the ad74412 is connected to a
gpio, but also pulled low (i.e., asserted) by default. Hence to get
the chip out of reset, the driver needs to know about that gpio and
deassert the reset signal before attempting to communicate with the
chip.
When a reset-gpio is given in device tree, use that instead of the
software reset. According to the data sheet, the two methods are
functionally equivalent.
Signed-off-by: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Link: https://lore.kernel.org/r/20221115095517.1008632-4-linux@rasmusvillemoes.dk
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Diffstat (limited to 'drivers/iio/test')
0 files changed, 0 insertions, 0 deletions