From: Stefan Agner <stefan@agner.ch>
To: jic23@kernel.org
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 v2 0/3] iio: adc: vf610: respect ADC clocking limitations
Date: Mon, 16 Mar 2015 16:10:11 +0100 [thread overview]
Message-ID: <1426518614-20201-1-git-send-email-stefan@agner.ch> (raw)
Respect ADC clocking limitations. The current clock settings lead
to bogous reading on a 500MHz clocked Vybrid SoC's. Additionally,
also implement a sysfs-property to configure the conversion mode
available in this ADC peripherial.
Changes since v1:
- Use ext_info for conversion mode
Stefan Agner (3):
iio: adc: vf610: use ADC clock within specification
iio: adc: vf610: implement configurable conversion modes
ARM: dts: add property for maximum ADC clock frequencies
.../devicetree/bindings/iio/adc/vf610-adc.txt | 9 +
arch/arm/boot/dts/vfxxx.dtsi | 4 +
drivers/iio/adc/vf610_adc.c | 225 +++++++++++++++------
3 files changed, 172 insertions(+), 66 deletions(-)
--
2.3.3
next reply other threads:[~2015-03-16 15:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-16 15:10 Stefan Agner [this message]
[not found] ` <1426518614-20201-1-git-send-email-stefan-XLVq0VzYD2Y@public.gmane.org>
2015-03-16 15:10 ` [PATCH v2 1/3] iio: adc: vf610: use ADC clock within specification Stefan Agner
2015-03-16 15:10 ` [PATCH v2 3/3] ARM: dts: add property for maximum ADC clock frequencies Stefan Agner
2015-03-16 15:17 ` Stefan Agner
2015-03-23 13:30 ` Shawn Guo
2015-03-16 15:10 ` [PATCH v2 2/3] iio: adc: vf610: implement configurable conversion modes Stefan Agner
2015-03-21 12:11 ` Jonathan Cameron
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=1426518614-20201-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=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 \
/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).