From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751804AbdCCMst (ORCPT ); Fri, 3 Mar 2017 07:48:49 -0500 Received: from www381.your-server.de ([78.46.137.84]:51048 "EHLO www381.your-server.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751518AbdCCMsr (ORCPT ); Fri, 3 Mar 2017 07:48:47 -0500 Subject: Re: [PATCH v3 6/6] iio: adc: stm32: add support for EXTI trigger To: Fabrice Gasnier , jic23@kernel.org, linux@armlinux.org.uk, robh+dt@kernel.org, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org References: <1488300679-3259-1-git-send-email-fabrice.gasnier@st.com> <1488300679-3259-7-git-send-email-fabrice.gasnier@st.com> Cc: linux-iio@vger.kernel.org, mark.rutland@arm.com, mcoquelin.stm32@gmail.com, alexandre.torgue@st.com, knaack.h@gmx.de, pmeerw@pmeerw.net, benjamin.gaignard@linaro.org, benjamin.gaignard@st.com, linus.walleij@linaro.org From: Lars-Peter Clausen Message-ID: <5be44ed9-2c86-ac51-d964-d231d5ca62fa@metafoo.de> Date: Fri, 3 Mar 2017 12:45:54 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.6.0 MIME-Version: 1.0 In-Reply-To: <1488300679-3259-7-git-send-email-fabrice.gasnier@st.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Authenticated-Sender: lars@metafoo.de Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 02/28/2017 05:51 PM, Fabrice Gasnier wrote: > EXTi (external interrupt) signal can be routed internally as trigger > source for ADC conversions: STM32F4 ADC can use EXTI11. > > Retrieve interrupt trigger from DT, so it can be muxed into ADC IP, > via extsel. Hi, Sorry, I have some trouble understanding the specifics of this. Is EXTI a hardware input signal into the ADC that automatically triggers a conversion when asserted? If yes how is it configured which external signal is used here. Your bindings suggest that any GPIO can be used, but the driver only differentiates between EXTI on or EXTI off. Or is this just a software triggered conversion? The GPIO triggers a software interrupt routine and the interrupt routine than triggers conversion?