From: Eugen Hristev <eugen.hristev@microchip.com>
To: nicolas.ferre@microchip.com, jic23@kernel.org,
alexandre.belloni@free-electrons.com, linux-iio@vger.kernel.org,
lars@metafoo.de, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: eugen.hristev@microchip.com, ludovic.desroches@microchip.com
Subject: [PATCH v2 1/3] ARM: dts: at91: sama5d2_xplained: enable ADTRG pin
Date: Thu, 4 May 2017 15:13:18 +0300 [thread overview]
Message-ID: <1493900000-26220-2-git-send-email-eugen.hristev@microchip.com> (raw)
In-Reply-To: <1493900000-26220-1-git-send-email-eugen.hristev@microchip.com>
Enable pinctrl for ADTRG pin (PD31) for ADC hardware trigger support.
Signed-off-by: Eugen Hristev <eugen.hristev@microchip.com>
---
arch/arm/boot/dts/at91-sama5d2_xplained.dts | 16 +++++++++++++++-
1 file changed, 15 insertions(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/at91-sama5d2_xplained.dts b/arch/arm/boot/dts/at91-sama5d2_xplained.dts
index 0bef9e0..04754b1 100644
--- a/arch/arm/boot/dts/at91-sama5d2_xplained.dts
+++ b/arch/arm/boot/dts/at91-sama5d2_xplained.dts
@@ -303,7 +303,7 @@
vddana-supply = <&vdd_3v3_lp_reg>;
vref-supply = <&vdd_3v3_lp_reg>;
pinctrl-names = "default";
- pinctrl-0 = <&pinctrl_adc_default>;
+ pinctrl-0 = <&pinctrl_adc_default &pinctrl_adtrg_default>;
status = "okay";
};
@@ -322,6 +322,20 @@
bias-disable;
};
+ /*
+ * The ADTRG pin can work on any edge type.
+ * In here it's being pulled up, so need to
+ * connect it to ground to get an edge e.g.
+ * Trigger can be configured on falling, rise
+ * or any edge, and the pull-up can be changed
+ * to pull-down or left floating according to
+ * needs.
+ */
+ pinctrl_adtrg_default: adtrg_default {
+ pinmux = <PIN_PD31__ADTRG>;
+ bias-pull-up;
+ };
+
pinctrl_charger_chglev: charger_chglev {
pinmux = <PIN_PA12__GPIO>;
bias-disable;
--
2.7.4
next prev parent reply other threads:[~2017-05-04 12:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 12:13 [PATCH v2 0/3] iio: adc: sama5d2_adc hw triggers and buffers Eugen Hristev
2017-05-04 12:13 ` Eugen Hristev [this message]
2017-05-04 12:13 ` [PATCH v2 2/3] iio: adc: at91-sama5d2_adc: add hw trigger and buffer support Eugen Hristev
2017-05-07 15:01 ` Jonathan Cameron
2017-05-10 8:49 ` Eugen Hristev
2017-05-11 6:09 ` Ludovic Desroches
[not found] ` <20170511060937.pzam3drvyaci6rnv-fC2aZbRiGnsAAwgTK2POJVCF2YAvjlIb@public.gmane.org>
2017-05-14 15:12 ` Jonathan Cameron
[not found] ` <af420704-0df8-184a-4fa2-c7e509a9b15d-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-05-15 7:38 ` Eugen Hristev
2017-05-16 18:03 ` Jonathan Cameron
[not found] ` <ae4e7987-d34e-0e8b-a975-6506af49a807-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-05-17 7:47 ` Peter Rosin
[not found] ` <395e7e0a-2c04-350c-c880-84d09e98a664-koto5C5qi+TLoDKTGw+V6w@public.gmane.org>
2017-05-17 11:35 ` Eugen Hristev
2017-05-21 11:58 ` Jonathan Cameron
2017-05-04 12:13 ` [PATCH v2 3/3] iio: tools: generic_buffer: increase trigger length Eugen Hristev
2017-05-07 15:03 ` 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=1493900000-26220-2-git-send-email-eugen.hristev@microchip.com \
--to=eugen.hristev@microchip.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=nicolas.ferre@microchip.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).