linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Joachim Eastwood <manabian@gmail.com>
Cc: knaack.h@gmx.de, lars@metafoo.de, pmeerw@pmeerw.net,
	linux-iio@vger.kernel.org, robh+dt@kernel.org
Subject: Re: [PATCH 0/4] Support for analog peripherals on LPC18xx familiy
Date: Sat, 5 Mar 2016 18:24:09 +0000	[thread overview]
Message-ID: <56DB2449.8090300@kernel.org> (raw)
In-Reply-To: <1456772741-9402-1-git-send-email-manabian@gmail.com>

On 29/02/16 19:05, Joachim Eastwood wrote:
> This patch set adds support for the analog (ADC and DAC) peripherals
> found on NXP LPC18xx/43xx SoCs. The ADC is a SAR converter with 10-bit
> resolution and 8 muxed inputs. The DAC is a simple single channel 10-
> bit DAC.
> 
> Note that these drivers do not support all the features found on the
> peripherals. DMA and interrupts are not supported in either drivers.
> The ADC driver also lack 'burst-mode' and hardware triggers. So for
> now the ADC is limited to single shot samples.
> 
> Both drivers tested on Embedded Artists' LPC4357 Developer's Kit.
> 
> Based on iio/testing branch from 29.02.15.
Series looks pretty good.  Will do a review of V2 - right now I haven't
found anything to add to what Peter found.

Nice little ADC from a quick read of the data sheet.  Not too complex
but still well featured.
> 
> 
> Joachim Eastwood (4):
>   iio: adc: add NXP LPC18xx ADC driver
>   dt: document NXP LPC1850 ADC driver bindings
>   iio: dac: add NXP LPC18xx DAC driver
>   dt: document NXP LPC1850 DAC driver bindings
> 
>  .../devicetree/bindings/iio/adc/lpc1850-adc.txt    |  21 ++
>  .../devicetree/bindings/iio/dac/lpc1850-dac.txt    |  20 ++
>  drivers/iio/adc/Kconfig                            |  10 +
>  drivers/iio/adc/Makefile                           |   1 +
>  drivers/iio/adc/lpc18xx_adc.c                      | 226 +++++++++++++++++++++
>  drivers/iio/dac/Kconfig                            |  10 +
>  drivers/iio/dac/Makefile                           |   1 +
>  drivers/iio/dac/lpc18xx_dac.c                      | 204 +++++++++++++++++++
>  8 files changed, 493 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/iio/adc/lpc1850-adc.txt
>  create mode 100644 Documentation/devicetree/bindings/iio/dac/lpc1850-dac.txt
>  create mode 100644 drivers/iio/adc/lpc18xx_adc.c
>  create mode 100644 drivers/iio/dac/lpc18xx_dac.c
> 


      parent reply	other threads:[~2016-03-05 18:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-29 19:05 [PATCH 0/4] Support for analog peripherals on LPC18xx familiy Joachim Eastwood
2016-02-29 19:05 ` [PATCH 1/4] iio: adc: add NXP LPC18xx ADC driver Joachim Eastwood
2016-02-29 19:42   ` Peter Meerwald-Stadler
2016-02-29 20:45     ` Joachim Eastwood
2016-02-29 19:05 ` [PATCH 2/4] dt: document NXP LPC1850 ADC driver bindings Joachim Eastwood
2016-02-29 19:05 ` [PATCH 3/4] iio: dac: add NXP LPC18xx DAC driver Joachim Eastwood
2016-02-29 19:05 ` [PATCH 4/4] dt: document NXP LPC1850 DAC driver bindings Joachim Eastwood
2016-03-01 20:33 ` [PATCH 0/4] Support for analog peripherals on LPC18xx familiy Rob Herring
2016-03-01 20:43   ` Joachim Eastwood
2016-03-05 18:24 ` Jonathan Cameron [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56DB2449.8090300@kernel.org \
    --to=jic23@kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=manabian@gmail.com \
    --cc=pmeerw@pmeerw.net \
    --cc=robh+dt@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).