diff for duplicates of <20181028120758.376da9aa@archlinux> diff --git a/a/1.txt b/N1/1.txt index 6898170..376566c 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -3,18 +3,15 @@ Rob Herring <robh@kernel.org> wrote: > On Thu, Oct 18, 2018 at 12:12:36PM +0300, Stefan Popa wrote: > > Document support for AD7606 Analog to Digital Converter. -> >=20 +> > > > Signed-off-by: Stefan Popa <stefan.popa@analog.com> > > --- -> > .../devicetree/bindings/iio/adc/adi,ad7606.txt | 51 ++++++++++++++= -++++++++ +> > .../devicetree/bindings/iio/adc/adi,ad7606.txt | 51 ++++++++++++++++++++++ > > MAINTAINERS | 1 + > > 2 files changed, 52 insertions(+) -> > create mode 100644 Documentation/devicetree/bindings/iio/adc/adi,ad760= -6.txt -> >=20 -> > diff --git a/Documentation/devicetree/bindings/iio/adc/adi,ad7606.txt b= -/Documentation/devicetree/bindings/iio/adc/adi,ad7606.txt +> > create mode 100644 Documentation/devicetree/bindings/iio/adc/adi,ad7606.txt +> > +> > diff --git a/Documentation/devicetree/bindings/iio/adc/adi,ad7606.txt b/Documentation/devicetree/bindings/iio/adc/adi,ad7606.txt > > new file mode 100644 > > index 0000000..dede581 > > --- /dev/null @@ -24,111 +21,95 @@ Rob Herring <robh@kernel.org> wrote: > > + > > +Required properties for the AD7606: > > + -> > + - compatible: Must be one of "adi,ad7605-4", "adi,ad7606-8", "adi,ad7= -606-6" or -> > + "adi,ad7606-4". =20 ->=20 +> > + - compatible: Must be one of "adi,ad7605-4", "adi,ad7606-8", "adi,ad7606-6" or +> > + "adi,ad7606-4". +> > Format as one per line please. ->=20 +> > > + - reg: SPI chip select number for the device > > + - spi-max-frequency: Max SPI frequency to use > > + see: Documentation/devicetree/bindings/spi/spi-bus.txt > > + - spi-cpha: See Documentation/devicetree/bindings/spi/spi-bus.txt > > + - avcc-supply: phandle to the Avcc power supply > > + - interrupts: IRQ line for the ADC -> > + see: Documentation/devicetree/bindings/interrupt-controller/interrup= -ts.txt -> > + - conversion-start-gpio: must be the device tree identifier of the CO= -NVST pin. +> > + see: Documentation/devicetree/bindings/interrupt-controller/interrupts.txt +> > + - conversion-start-gpio: must be the device tree identifier of the CONVST pin. > > + This logic input is used to initiate conversions on -> > + the analog input channels. =20 ->=20 +> > + the analog input channels. +> > Doesn't IIO have trigger GPIOs? Wrong way around. Those are for when you want to use a GPIO to tell the OS -to grab data now. This one is a 'capture now' pin used to cause the hardwa= -re -to start capturing. We might be able to do something a little generic arou= -nd +to grab data now. This one is a 'capture now' pin used to cause the hardware +to start capturing. We might be able to do something a little generic around this type, but I don't think we would gain much doing it. -The more interesting point is that the real reason devices have these is ei= -ther: +The more interesting point is that the real reason devices have these is either: 1) To capture synchronized data cross a bank of ADCs 2) To capture data under control of device not visible to the OS (some sort of external controller). Neither of these cases is terribly well handled at the moment. However, no -one has yet really expressed a desire to do so, hence maybe it's not actual= -ly +one has yet really expressed a desire to do so, hence maybe it's not actually done... The first option would need a 'hardware' trigger path which isn't something -we really do as yet in general. We have individual drivers doing it but no= -rmally -only when it's routing a pulse signal to cause the hardware to fill a fifo = -and +we really do as yet in general. We have individual drivers doing it but normally +only when it's routing a pulse signal to cause the hardware to fill a fifo and the OS only gets involved occasionally. -Ah well, if anyone cares we'll figure out how to do it ;)=20 +Ah well, if anyone cares we'll figure out how to do it ;) ->=20 +> > > + > > +Optional properties: > > + -> > + - reset-gpio: must be the device tree identifier of the RESET pin. If= - specified, -> > + it will be asserted during driver probe. =20 ->=20 +> > + - reset-gpio: must be the device tree identifier of the RESET pin. If specified, +> > + it will be asserted during driver probe. +> > -gpios is the preferred form: reset-gpios ->=20 +> > And state the active state ->=20 -> > + - first-data-gpio: must be the device tree identifier of the FRSTDATA= - pin. +> +> > + - first-data-gpio: must be the device tree identifier of the FRSTDATA pin. > > + The FRSTDATA output indicates when the first channel, V1, is > > + being read back on either the parallel, byte or serial interface. -> > +- standby-gpio: must be the device tree identifier of the STBY pin. Th= -is pin is used +> > +- standby-gpio: must be the device tree identifier of the STBY pin. This pin is used > > + to place the AD7606 into one of two power-down modes, Standby mode or > > + Shutdown mode. -> > +- range-gpio: must be the device tree identifier of the RANGE pin. The= - polarity on -> > + this pin determines the input range of the analog input channel= -s. If -> > + this pin is tied to a logic high, the analog input range is =C2= -=B110V for -> > + allchannels. If this pin is tied to a logic low, the analog inp= -ut range =20 ->=20 +> > +- range-gpio: must be the device tree identifier of the RANGE pin. The polarity on +> > + this pin determines the input range of the analog input channels. If +> > + this pin is tied to a logic high, the analog input range is ±10V for +> > + allchannels. If this pin is tied to a logic low, the analog input range +> > s/allchannels/all channels/ ->=20 -> > + is =C2=B15V for all channels. =20 ->=20 -> conversion-start-gpio, first-data-gpio, and range-gpio should all have=20 +> +> > + is ±5V for all channels. +> +> conversion-start-gpio, first-data-gpio, and range-gpio should all have > vendor prefix (in addition to -gpios). Gah, I should have spotted all of that. Thanks Rob! Jonathan ->=20 +> > > + > > +Example: > > + > > + adc@0 { -> > + compatible =3D "adi,ad7606-8"; -> > + reg =3D <0>; -> > + spi-max-frequency =3D <1000000>; +> > + compatible = "adi,ad7606-8"; +> > + reg = <0>; +> > + spi-max-frequency = <1000000>; > > + spi-cpol; > > + -> > + avcc-supply =3D <&adc_vref>; +> > + avcc-supply = <&adc_vref>; > > + -> > + interrupts =3D <25 IRQ_TYPE_EDGE_FALLING>; -> > + interrupt-parent =3D <&gpio>; +> > + interrupts = <25 IRQ_TYPE_EDGE_FALLING>; +> > + interrupt-parent = <&gpio>; > > + -> > + conversion-start-gpio =3D <&gpio 17 0>; -> > + reset-gpio =3D <&gpio 27 0>; -> > + first-data-gpio =3D <&gpio 22 0>; -> > + standby-gpio =3D <&gpio 24 0>; +> > + conversion-start-gpio = <&gpio 17 0>; +> > + reset-gpio = <&gpio 27 0>; +> > + first-data-gpio = <&gpio 22 0>; +> > + standby-gpio = <&gpio 24 0>; > > + }; > > diff --git a/MAINTAINERS b/MAINTAINERS > > index 843545d..6d63db4 100644 @@ -139,9 +120,9 @@ Jonathan > > S: Supported > > F: drivers/iio/adc/ad7606.c > > +F: Documentation/devicetree/bindings/iio/adc/ad7606.txt -> > =20 +> > > > ANALOG DEVICES INC AD9389B DRIVER > > M: Hans Verkuil <hans.verkuil@cisco.com> -> > --=20 +> > -- > > 2.7.4 -> > =20 +> > diff --git a/a/content_digest b/N1/content_digest index df42241..9dc8c4b 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -21,18 +21,15 @@ "\n" "> On Thu, Oct 18, 2018 at 12:12:36PM +0300, Stefan Popa wrote:\n" "> > Document support for AD7606 Analog to Digital Converter.\n" - "> >=20\n" + "> > \n" "> > Signed-off-by: Stefan Popa <stefan.popa@analog.com>\n" "> > ---\n" - "> > .../devicetree/bindings/iio/adc/adi,ad7606.txt | 51 ++++++++++++++=\n" - "++++++++\n" + "> > .../devicetree/bindings/iio/adc/adi,ad7606.txt | 51 ++++++++++++++++++++++\n" "> > MAINTAINERS | 1 +\n" "> > 2 files changed, 52 insertions(+)\n" - "> > create mode 100644 Documentation/devicetree/bindings/iio/adc/adi,ad760=\n" - "6.txt\n" - "> >=20\n" - "> > diff --git a/Documentation/devicetree/bindings/iio/adc/adi,ad7606.txt b=\n" - "/Documentation/devicetree/bindings/iio/adc/adi,ad7606.txt\n" + "> > create mode 100644 Documentation/devicetree/bindings/iio/adc/adi,ad7606.txt\n" + "> > \n" + "> > diff --git a/Documentation/devicetree/bindings/iio/adc/adi,ad7606.txt b/Documentation/devicetree/bindings/iio/adc/adi,ad7606.txt\n" "> > new file mode 100644\n" "> > index 0000000..dede581\n" "> > --- /dev/null\n" @@ -42,111 +39,95 @@ "> > +\n" "> > +Required properties for the AD7606:\n" "> > +\n" - "> > + - compatible: Must be one of \"adi,ad7605-4\", \"adi,ad7606-8\", \"adi,ad7=\n" - "606-6\" or\n" - "> > + \t \"adi,ad7606-4\". =20\n" - ">=20\n" + "> > + - compatible: Must be one of \"adi,ad7605-4\", \"adi,ad7606-8\", \"adi,ad7606-6\" or\n" + "> > + \t \"adi,ad7606-4\". \n" + "> \n" "> Format as one per line please.\n" - ">=20\n" + "> \n" "> > + - reg: SPI chip select number for the device\n" "> > + - spi-max-frequency: Max SPI frequency to use\n" "> > + \tsee: Documentation/devicetree/bindings/spi/spi-bus.txt\n" "> > + - spi-cpha: See Documentation/devicetree/bindings/spi/spi-bus.txt\n" "> > + - avcc-supply: phandle to the Avcc power supply\n" "> > + - interrupts: IRQ line for the ADC\n" - "> > + \tsee: Documentation/devicetree/bindings/interrupt-controller/interrup=\n" - "ts.txt\n" - "> > + - conversion-start-gpio: must be the device tree identifier of the CO=\n" - "NVST pin.\n" + "> > + \tsee: Documentation/devicetree/bindings/interrupt-controller/interrupts.txt\n" + "> > + - conversion-start-gpio: must be the device tree identifier of the CONVST pin.\n" "> > +\t\t\t This logic input is used to initiate conversions on\n" - "> > +\t\t\t the analog input channels. =20\n" - ">=20\n" + "> > +\t\t\t the analog input channels. \n" + "> \n" "> Doesn't IIO have trigger GPIOs?\n" "\n" "Wrong way around. Those are for when you want to use a GPIO to tell the OS\n" - "to grab data now. This one is a 'capture now' pin used to cause the hardwa=\n" - "re\n" - "to start capturing. We might be able to do something a little generic arou=\n" - "nd\n" + "to grab data now. This one is a 'capture now' pin used to cause the hardware\n" + "to start capturing. We might be able to do something a little generic around\n" "this type, but I don't think we would gain much doing it.\n" "\n" - "The more interesting point is that the real reason devices have these is ei=\n" - "ther:\n" + "The more interesting point is that the real reason devices have these is either:\n" "1) To capture synchronized data cross a bank of ADCs\n" "2) To capture data under control of device not visible to the OS (some sort\n" "of external controller).\n" "\n" "Neither of these cases is terribly well handled at the moment. However, no\n" - "one has yet really expressed a desire to do so, hence maybe it's not actual=\n" - "ly\n" + "one has yet really expressed a desire to do so, hence maybe it's not actually\n" "done...\n" "\n" "The first option would need a 'hardware' trigger path which isn't something\n" - "we really do as yet in general. We have individual drivers doing it but no=\n" - "rmally\n" - "only when it's routing a pulse signal to cause the hardware to fill a fifo =\n" - "and\n" + "we really do as yet in general. We have individual drivers doing it but normally\n" + "only when it's routing a pulse signal to cause the hardware to fill a fifo and\n" "the OS only gets involved occasionally.\n" "\n" - "Ah well, if anyone cares we'll figure out how to do it ;)=20\n" + "Ah well, if anyone cares we'll figure out how to do it ;) \n" "\n" - ">=20\n" + "> \n" "> > +\n" "> > +Optional properties:\n" "> > +\n" - "> > + - reset-gpio: must be the device tree identifier of the RESET pin. If=\n" - " specified,\n" - "> > + \t it will be asserted during driver probe. =20\n" - ">=20\n" + "> > + - reset-gpio: must be the device tree identifier of the RESET pin. If specified,\n" + "> > + \t it will be asserted during driver probe. \n" + "> \n" "> -gpios is the preferred form: reset-gpios\n" - ">=20\n" + "> \n" "> And state the active state\n" - ">=20\n" - "> > + - first-data-gpio: must be the device tree identifier of the FRSTDATA=\n" - " pin.\n" + "> \n" + "> > + - first-data-gpio: must be the device tree identifier of the FRSTDATA pin.\n" "> > + \t\t The FRSTDATA output indicates when the first channel, V1, is\n" "> > +\t\t being read back on either the parallel, byte or serial interface.\n" - "> > +- standby-gpio: must be the device tree identifier of the STBY pin. Th=\n" - "is pin is used\n" + "> > +- standby-gpio: must be the device tree identifier of the STBY pin. This pin is used\n" "> > +\t\tto place the AD7606 into one of two power-down modes, Standby mode or\n" "> > +\t\tShutdown mode.\n" - "> > +- range-gpio: must be the device tree identifier of the RANGE pin. The=\n" - " polarity on\n" - "> > +\t this pin determines the input range of the analog input channel=\n" - "s. If\n" - "> > +\t this pin is tied to a logic high, the analog input range is =C2=\n" - "=B110V for\n" - "> > +\t allchannels. If this pin is tied to a logic low, the analog inp=\n" - "ut range =20\n" - ">=20\n" + "> > +- range-gpio: must be the device tree identifier of the RANGE pin. The polarity on\n" + "> > +\t this pin determines the input range of the analog input channels. If\n" + "> > +\t this pin is tied to a logic high, the analog input range is \302\26110V for\n" + "> > +\t allchannels. If this pin is tied to a logic low, the analog input range \n" + "> \n" "> s/allchannels/all channels/\n" - ">=20\n" - "> > +\t is =C2=B15V for all channels. =20\n" - ">=20\n" - "> conversion-start-gpio, first-data-gpio, and range-gpio should all have=20\n" + "> \n" + "> > +\t is \302\2615V for all channels. \n" + "> \n" + "> conversion-start-gpio, first-data-gpio, and range-gpio should all have \n" "> vendor prefix (in addition to -gpios).\n" "Gah, I should have spotted all of that. Thanks Rob!\n" "\n" "Jonathan\n" - ">=20\n" + "> \n" "> > +\n" "> > +Example:\n" "> > +\n" "> > +\tadc@0 {\n" - "> > +\t\tcompatible =3D \"adi,ad7606-8\";\n" - "> > +\t\treg =3D <0>;\n" - "> > +\t\tspi-max-frequency =3D <1000000>;\n" + "> > +\t\tcompatible = \"adi,ad7606-8\";\n" + "> > +\t\treg = <0>;\n" + "> > +\t\tspi-max-frequency = <1000000>;\n" "> > +\t\tspi-cpol;\n" "> > +\n" - "> > +\t\tavcc-supply =3D <&adc_vref>;\n" + "> > +\t\tavcc-supply = <&adc_vref>;\n" "> > +\n" - "> > +\t\tinterrupts =3D <25 IRQ_TYPE_EDGE_FALLING>;\n" - "> > +\t\tinterrupt-parent =3D <&gpio>;\n" + "> > +\t\tinterrupts = <25 IRQ_TYPE_EDGE_FALLING>;\n" + "> > +\t\tinterrupt-parent = <&gpio>;\n" "> > +\n" - "> > +\t\tconversion-start-gpio =3D <&gpio 17 0>;\n" - "> > +\t\treset-gpio =3D <&gpio 27 0>;\n" - "> > +\t\tfirst-data-gpio =3D <&gpio 22 0>;\n" - "> > +\t\tstandby-gpio =3D <&gpio 24 0>;\n" + "> > +\t\tconversion-start-gpio = <&gpio 17 0>;\n" + "> > +\t\treset-gpio = <&gpio 27 0>;\n" + "> > +\t\tfirst-data-gpio = <&gpio 22 0>;\n" + "> > +\t\tstandby-gpio = <&gpio 24 0>;\n" "> > +\t};\n" "> > diff --git a/MAINTAINERS b/MAINTAINERS\n" "> > index 843545d..6d63db4 100644\n" @@ -157,11 +138,11 @@ "> > S:\tSupported\n" "> > F:\tdrivers/iio/adc/ad7606.c\n" "> > +F:\tDocumentation/devicetree/bindings/iio/adc/ad7606.txt\n" - "> > =20\n" + "> > \n" "> > ANALOG DEVICES INC AD9389B DRIVER\n" "> > M:\tHans Verkuil <hans.verkuil@cisco.com>\n" - "> > --=20\n" + "> > -- \n" "> > 2.7.4\n" - > > =20 + > > -54289d3fa09a3e4e5712cfe54acf5db749fb8d00528686d27422c39e86515a4d +f0c0de374f821554acd04dbadae8155fde181365ca5f54154a6418e38937f42d
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.