On Sat, Dec 24, 2016 at 09:54:57AM +0800, Allen Liu wrote: > Add ADC driver for the ADC controller found on HiSilicon BVT SOCs, like Hi3516CV300, etc. > The ADC controller is primarily in charge of detecting voltage. > > Reviewed-by: Jiancheng Xue <xuejiancheng@xxxxxxxxxxxxx> > Signed-off-by: Allen Liu <liurenzhong@xxxxxxxxxxxxx> > --- > .../devicetree/bindings/iio/adc/hibvt-lsadc.txt | 26 ++ > drivers/iio/adc/Kconfig | 10 + > drivers/iio/adc/Makefile | 1 + > drivers/iio/adc/hibvt_lsadc.c | 344 +++++++++++++++++++++ > 4 files changed, 381 insertions(+) > create mode 100644 Documentation/devicetree/bindings/iio/adc/hibvt-lsadc.txt > create mode 100644 drivers/iio/adc/hibvt_lsadc.c > > diff --git a/Documentation/devicetree/bindings/iio/adc/hibvt-lsadc.txt b/Documentation/devicetree/bindings/iio/adc/hibvt-lsadc.txt > new file mode 100644 > index 0000000..63de46e > --- /dev/null > +++ b/Documentation/devicetree/bindings/iio/adc/hibvt-lsadc.txt > @@ -0,0 +1,26 @@ > +Hisilicon BVT Low Speed (LS) A/D Converter bindings > + > +Required properties: > +- compatible: should be "hisilicon,<name>-lsadc" > + - "hisilicon,hibvt-lsadc": for hi3516cv300 Use the SoC name in the compatible string. > + > +- reg: physical base address of the controller and length of memory mapped > + region. > +- interrupts: The interrupt number to the cpu. The interrupt specifier format > + depends on the interrupt controller. > +- #io-channel-cells: Should be 1, see ../iio-bindings.txt > + > +Optional properties: > +- resets: Must contain an entry for each entry in reset-names if need support > + this option. See ../reset/reset.txt for details. > +- reset-names: Must include the name "saradc-apb". > + > +Example: > + lsadc: hibvt-lsadc@120e0000 { Just "adc@..." > + compatible = "hisilicon,hibvt-lsadc"; > + reg = <0x120e0000 0x1000>; > + interrupts = <19>; > + resets = <&crg 0x7c 3>; > + reset-names = "lsadc-crg"; > + status = "disabled"; > + }; -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html