From: Stefan Agner <stefan@agner.ch>
To: jic23@kernel.org, shawn.guo@linaro.org, kernel@pengutronix.de
Cc: knaack.h@gmx.de, lars@metafoo.de, pmeerw@pmeerw.net,
robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
B38611@freescale.com, maitysanchayan@gmail.com,
devicetree@vger.kernel.org, linux-iio@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Stefan Agner <stefan@agner.ch>
Subject: [PATCH v5 0/2] iio: adc: vf610: respect ADC clocking limitations
Date: Wed, 27 May 2015 14:47:50 +0200 [thread overview]
Message-ID: <1432730872-14325-1-git-send-email-stefan@agner.ch> (raw)
This revision is basically the same as v4, just some wording
improvements. I would appriciate an Ack for the device tree part.
The clock limit values are defined in the data sheet and could
be different per SoC, hence descirbe the hardware limitation...
Changes since v4:
- Remove fussy english
- Drop "iio: adc: vf610: use ADC clock within specification" since
that patch is already applied
Changes since v3:
- Move device tree bindings to driver changes
Changes since v2:
- Add sysfs ABI documentation
- Fix commit message spelling errors
Changes since v1:
- Use ext_info for conversion mode
Stefan Agner (2):
iio: adc: vf610: implement configurable conversion modes
ARM: dts: add property for maximum ADC clock frequencies
Documentation/ABI/testing/sysfs-bus-iio-vf610 | 7 +
.../devicetree/bindings/iio/adc/vf610-adc.txt | 9 ++
arch/arm/boot/dts/vfxxx.dtsi | 4 +
drivers/iio/adc/vf610_adc.c | 146 +++++++++++++++------
4 files changed, 124 insertions(+), 42 deletions(-)
create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-vf610
--
2.4.1
next reply other threads:[~2015-05-27 12:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 12:47 Stefan Agner [this message]
[not found] ` <1432730872-14325-1-git-send-email-stefan-XLVq0VzYD2Y@public.gmane.org>
2015-05-27 12:47 ` [PATCH v5 1/2] iio: adc: vf610: implement configurable conversion modes Stefan Agner
[not found] ` <1432730872-14325-2-git-send-email-stefan-XLVq0VzYD2Y@public.gmane.org>
2015-06-07 16:54 ` Jonathan Cameron
2015-06-08 17:49 ` Rob Herring
[not found] ` <CAL_JsqK0YxgJ-k8kSs6XQj9n3FSg4QBd-GdFEfcafH7Cm4NreQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-06-08 20:07 ` Stefan Agner
[not found] ` <14d469dedae9de1ce519fe90401e526e-XLVq0VzYD2Y@public.gmane.org>
2015-06-14 11:12 ` Jonathan Cameron
[not found] ` <557D6184.90105-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2015-06-23 14:27 ` Rob Herring
2015-05-27 12:47 ` [PATCH v5 2/2] ARM: dts: add property for maximum ADC clock frequencies Stefan Agner
[not found] ` <1432730872-14325-3-git-send-email-stefan-XLVq0VzYD2Y@public.gmane.org>
2015-06-07 16:56 ` Jonathan Cameron
[not found] ` <557477BE.5050108-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2015-06-07 19:23 ` Stefan Agner
2015-08-03 12:22 ` Stefan Agner
2015-08-05 13:46 ` Shawn Guo
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=1432730872-14325-1-git-send-email-stefan@agner.ch \
--to=stefan@agner.ch \
--cc=B38611@freescale.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jic23@kernel.org \
--cc=kernel@pengutronix.de \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maitysanchayan@gmail.com \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=pmeerw@pmeerw.net \
--cc=robh+dt@kernel.org \
--cc=shawn.guo@linaro.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).