diff options
| author | Lukas Wunner <lukas@wunner.de> | 2017-09-09 20:32:41 +0200 |
|---|---|---|
| committer | Jonathan Cameron <Jonathan.Cameron@huawei.com> | 2017-09-24 16:28:50 +0100 |
| commit | fd060b3cd585542b44335d9169c71ce40b6384ac (patch) | |
| tree | a85f70bf242e3723f3ea9b65a69ebd2c57362df1 /drivers/iio/trigger/stm32-timer-trigger.c | |
| parent | 5e3c3e3382e87a637c5c9229b4b539dfbf81c64b (diff) | |
| download | linux-fd060b3cd585542b44335d9169c71ce40b6384ac.tar.gz linux-fd060b3cd585542b44335d9169c71ce40b6384ac.tar.bz2 linux-fd060b3cd585542b44335d9169c71ce40b6384ac.zip | |
dt-bindings: iio: adc: mcp320x: Update for mcp3550/1/3
All chips supported by this driver clock data out on the falling edge
and latch data in on the rising edge, hence SPI mode (0,0) or (1,1)
must be used.
Furthermore, none of the chips has an internal reference voltage
regulator, so an external supply is always required and needs to be
specified in the device tree lest the IIO "scale" in sysfs cannot be
calculated.
Document these requirements in the device tree binding, add compatible
strings for the newly supported mcp3550/1/3 and explain that SPI mode
(0,0) should be preferred for these chips.
Cc: Mathias Duckeck <m.duckeck@kunbus.de>
Signed-off-by: Lukas Wunner <lukas@wunner.de>
Acked-by: Rob Herring <robh@kernel.org>
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Diffstat (limited to 'drivers/iio/trigger/stm32-timer-trigger.c')
0 files changed, 0 insertions, 0 deletions