From: Stefan Roese <sr@denx.de>
To: Jonathan Cameron <jic23@cam.ac.uk>
Cc: linux-iio@vger.kernel.org, devicetree-discuss@ozlabs.org,
spear-devel@list.st.com, Viresh Kumar <viresh.kumar@st.com>
Subject: Re: [PATCH] staging:iio:adc: Add SPEAr ADC driver
Date: Thu, 12 Apr 2012 08:01:04 +0200 [thread overview]
Message-ID: <201204120801.05269.sr@denx.de> (raw)
In-Reply-To: <4F8589E4.7020809@cam.ac.uk>
On Wednesday 11 April 2012 15:40:52 Jonathan Cameron wrote:
> On 4/11/2012 2:19 PM, Stefan Roese wrote:
> > This patch implements the basic single data conversion support for
> > the SPEAr600 SoC ADC. The register layout of SPEAr600 differs a bit
> > from other SPEAr SoC variants (e.g. SPEAr3xx). These differences are
> > handled via DT compatible testing. Resuling in a multi-arch binary.
>
> Resulting
>
> > This driver is currently tested only on SPEAr600. Futur patches may add
> > support for other SoC variants (SPEAr3xx) and features like software
> > buffer or DMA.
>
> Future
>
> Ironically that's about it wrt to comments. Couple of totally trivial
> bits inline.
> Basically I'm happy, so if/when someone acks the device tree side of
> things, please
> clean up the trivial bits and send on to GregKH.
>
> Nice short, clean driver. The small line count lured me into reviewing
> it ahead of
> some others in my review pile!
Jonathan, thanks for the quick review. I'll address you comments and send an
updated patch shortly.
Stefan
next prev parent reply other threads:[~2012-04-12 6:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 13:19 [PATCH] staging:iio:adc: Add SPEAr ADC driver Stefan Roese
2012-04-11 13:40 ` Jonathan Cameron
2012-04-12 6:01 ` Stefan Roese [this message]
2012-04-12 6:12 ` Viresh Kumar
2012-04-12 7:03 ` Stefan Roese
2012-04-12 7:41 ` Viresh Kumar
2012-04-12 8:15 ` Stefan Roese
2012-04-12 8:21 ` Viresh Kumar
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=201204120801.05269.sr@denx.de \
--to=sr@denx.de \
--cc=devicetree-discuss@ozlabs.org \
--cc=jic23@cam.ac.uk \
--cc=linux-iio@vger.kernel.org \
--cc=spear-devel@list.st.com \
--cc=viresh.kumar@st.com \
/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).