From: Sanchayan Maity <maitysanchayan@gmail.com>
To: jic23@kernel.org
Cc: shawn.guo@linaro.org, kernel@pengutronix.de, robh+dt@kernel.org,
pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
B38611@freescale.com, devicetree@vger.kernel.org,
linux-iio@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, stefan@agner.ch,
Sanchayan Maity <maitysanchayan@gmail.com>
Subject: [PATCH v3 2/2] ARM: dts: vf-colibri: Add property for minimum sample time
Date: Tue, 14 Jul 2015 19:23:23 +0530 [thread overview]
Message-ID: <20e2cfad3fbb1a45332e9936ea493ddc8bfaf51d.1436880513.git.maitysanchayan@gmail.com> (raw)
In-Reply-To: <cover.1436880513.git.maitysanchayan@gmail.com>
In-Reply-To: <cover.1436880513.git.maitysanchayan@gmail.com>
Add a device tree property which allows to specify the minimum sample
time which can be used to calculate the actual ADC cycles required
depending on the hardware.
Signed-off-by: Sanchayan Maity <maitysanchayan@gmail.com>
---
arch/arm/boot/dts/vf-colibri.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/vf-colibri.dtsi b/arch/arm/boot/dts/vf-colibri.dtsi
index ab10d2e..59f5deb 100644
--- a/arch/arm/boot/dts/vf-colibri.dtsi
+++ b/arch/arm/boot/dts/vf-colibri.dtsi
@@ -16,10 +16,12 @@
};
&adc0 {
+ min-sample-time = <1000>;
status = "okay";
};
&adc1 {
+ min-sample-time = <1000>;
status = "okay";
};
--
2.4.5
next prev parent reply other threads:[~2015-07-14 13:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 13:53 [PATCH v3 0/2] Implement sample time consideration for Vybrid's ADC Sanchayan Maity
2015-07-14 13:53 ` [PATCH v3 1/2] iio: adc: vf610: Determine sampling frequencies by using minimum sample time Sanchayan Maity
2015-07-19 12:48 ` Jonathan Cameron
2015-07-14 13:53 ` Sanchayan Maity [this message]
2015-07-15 1:57 ` [PATCH v3 2/2] ARM: dts: vf-colibri: Add property for " Shawn Guo
2015-07-15 13:02 ` Stefan Agner
2015-07-19 12:44 ` 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=20e2cfad3fbb1a45332e9936ea493ddc8bfaf51d.1436880513.git.maitysanchayan@gmail.com \
--to=maitysanchayan@gmail.com \
--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=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=shawn.guo@linaro.org \
--cc=stefan@agner.ch \
/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
all inboxes | Powered by JetHome®