On Fri, 20 Sep 2024 17:33:24 +0000 Guillaume Stols <gstols@xxxxxxxxxxxx> wrote: > The Analog Devices Inc. AD7606 (and similar chips) are complex ADCs that > will benefit from a detailed driver documentation. > > This documents the current features supported by the driver. > > Signed-off-by: Guillaume Stols <gstols@xxxxxxxxxxxx> > --- > Documentation/iio/ad7606.rst | 143 +++++++++++++++++++++++++++++++++++++++++++ > 1 file changed, 143 insertions(+) > > diff --git a/Documentation/iio/ad7606.rst b/Documentation/iio/ad7606.rst > new file mode 100644 > index 000000000000..270a49aae685 > --- /dev/null > +++ b/Documentation/iio/ad7606.rst > @@ -0,0 +1,143 @@ > +.. SPDX-License-Identifier: GPL-2.0-only > + > +============= > +AD7606 driver > +============= > + > +ADC driver for Analog Devices Inc. AD7606 and similar devices. The module name > +is ``ad7606``. > + > +Supported devices > +================= > + > +The following chips are supported by this driver: > + > +* `AD7605 <https://www.analog.com/en/products/ad7605.html>`_ > +* `AD7606 <https://www.analog.com/en/products/ad7606.html>`_ > +* `AD7606B <https://www.analog.com/en/products/ad7606b.html>`_ > +* `AD7616 <https://www.analog.com/en/products/ad7616.html>`_ > + > +Supported features > +================== > + > +SPI wiring modes > +---------------- > + > +ad7606x ADCs can output data on several SDO lines (1/2/4/8). The driver > +currently supports only 1 SDO line. > + > +Parallel wiring mode > +-------------------- > + > +AD7606x ADC have also a parallel interface, with 16 lines (that can be reduced If intent here is AD7606 and AD7606B only as covered by that wildcard, then I'd just state them both explicitly. If the others are intended that wildcard is wrong. If it's all of them, just say These ADCs > +to 8 in byte mode). The parallel interface is selected by declaring the device > +as platform in the device tree (with no io-backends node defined, see below). > + > +IIO-backend mode > +---------------- > + > +This mode allows to reach the best sample rates, but it requires an external > +hardware (eg HDL or APU) to handle the low level communication. > +The backend mode is enabled when through the definition of the "io-backends" > +property in the device tree. > + > +The reference configuration for the current implementation of IIO-backend mode > +is the HDL reference provided by ADI: > +https://wiki.analog.com/resources/eval/user-guides/ad7606x-fmc/hdl > + > +This implementation embeds an IIO-backend compatible IP (adi-axi-adc) and a PWM > +connected to the conversion trigger pin. > + > ++---+ +---------------------------- > +| | +-------+ |AD76xx > +| A | controls | | | > +| D |-------------->| PWM |-------------->| cnvst > +| 7 | | | | > +| 6 | +-------+ | > +| 0 | controls +-----------+-----------+ | > +| 6 |---------->| | |<--| frstdata > +| | | Backend | Backend |<--| busy > +| D | | Driver | | | > +| R | | | |-->| clk > +| I | requests |+---------+| DMA | | > +| V |----------->| Buffer ||<---- |<=>| DATA > +| E | |+---------+| | | > +| R | +-----------+-----------+ | > +| |-------------------------------------->| reset/configuration gpios > ++---+ +----------------------------- > + I think we should introduce an annual award for best kernel ASCII art. This one is nice. > +IIO backend buffer > +------------------ > + > +When IIO backend is used, the trigger is not needed, and the sample rate is > +considered as stable, hence there is no timestamp channel. That's a dodge I think. There is no timestamp because we have no way to insert one into the DMA buffer! I'd drop the hence "stable. There is no timestamp channel." > The communication is > +delegated to an external logic, called a backend, and the backend's driver > +handles the buffer. When this mode is enabled, the driver cannot control the > +conversion pin, because the busy pin is bound to the backend. > + Nice docs in general. Jonathan
