All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars-Peter Clausen <lars@metafoo.de>
To: Fabrice Gasnier <fabrice.gasnier@st.com>,
	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
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
Subject: Re: [PATCH v3 6/6] iio: adc: stm32: add support for EXTI trigger
Date: Fri, 3 Mar 2017 12:45:54 +0100	[thread overview]
Message-ID: <5be44ed9-2c86-ac51-d964-d231d5ca62fa@metafoo.de> (raw)
In-Reply-To: <1488300679-3259-7-git-send-email-fabrice.gasnier@st.com>

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?

WARNING: multiple messages have this Message-ID (diff)
From: Lars-Peter Clausen <lars@metafoo.de>
To: Fabrice Gasnier <fabrice.gasnier@st.com>,
	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
Cc: mark.rutland@arm.com, mcoquelin.stm32@gmail.com,
	benjamin.gaignard@linaro.org, alexandre.torgue@st.com,
	linux-iio@vger.kernel.org, linus.walleij@linaro.org,
	pmeerw@pmeerw.net, knaack.h@gmx.de, benjamin.gaignard@st.com
Subject: Re: [PATCH v3 6/6] iio: adc: stm32: add support for EXTI trigger
Date: Fri, 3 Mar 2017 12:45:54 +0100	[thread overview]
Message-ID: <5be44ed9-2c86-ac51-d964-d231d5ca62fa@metafoo.de> (raw)
In-Reply-To: <1488300679-3259-7-git-send-email-fabrice.gasnier@st.com>

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?

WARNING: multiple messages have this Message-ID (diff)
From: lars@metafoo.de (Lars-Peter Clausen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 6/6] iio: adc: stm32: add support for EXTI trigger
Date: Fri, 3 Mar 2017 12:45:54 +0100	[thread overview]
Message-ID: <5be44ed9-2c86-ac51-d964-d231d5ca62fa@metafoo.de> (raw)
In-Reply-To: <1488300679-3259-7-git-send-email-fabrice.gasnier@st.com>

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?

  reply	other threads:[~2017-03-03 12:48 UTC|newest]

Thread overview: 78+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-28 16:51 [PATCH v3 0/6] Add EXTI GPIO trigger support to STM32 ADC Fabrice Gasnier
2017-02-28 16:51 ` Fabrice Gasnier
2017-02-28 16:51 ` Fabrice Gasnier
2017-02-28 16:51 ` [PATCH v3 1/6] dt-bindings: iio: introduce trigger providers, consumers Fabrice Gasnier
2017-02-28 16:51   ` Fabrice Gasnier
2017-02-28 16:51   ` Fabrice Gasnier
2017-03-03  6:21   ` Rob Herring
2017-03-03  6:21     ` Rob Herring
2017-03-03  6:21     ` Rob Herring
2017-03-03  9:32     ` Fabrice Gasnier
2017-03-03  9:32       ` Fabrice Gasnier
2017-03-03  9:32       ` Fabrice Gasnier
2017-03-05 11:45       ` Jonathan Cameron
2017-03-05 11:45         ` Jonathan Cameron
2017-03-05 11:45         ` Jonathan Cameron
2017-03-05 11:43     ` Jonathan Cameron
2017-03-05 11:43       ` Jonathan Cameron
2017-03-05 11:43       ` Jonathan Cameron
2017-03-05 12:13       ` Jonathan Cameron
2017-03-05 12:13         ` Jonathan Cameron
2017-03-15 19:25         ` Rob Herring
2017-03-15 19:25           ` Rob Herring
2017-03-15 19:25           ` Rob Herring
2017-03-17 15:59           ` Fabrice Gasnier
2017-03-17 15:59             ` Fabrice Gasnier
2017-03-17 15:59             ` Fabrice Gasnier
2017-03-19 22:58             ` Jonathan Cameron
2017-03-19 22:58               ` Jonathan Cameron
2017-03-19 22:58               ` Jonathan Cameron
2017-02-28 16:51 ` [PATCH v3 2/6] iio: trigger: add OF support Fabrice Gasnier
2017-02-28 16:51   ` Fabrice Gasnier
2017-02-28 16:51   ` Fabrice Gasnier
2017-03-05 12:11   ` Jonathan Cameron
2017-03-05 12:11     ` Jonathan Cameron
2017-03-05 12:11     ` Jonathan Cameron
2017-03-14 15:22   ` Linus Walleij
2017-03-14 15:22     ` Linus Walleij
2017-03-14 15:22     ` Linus Walleij
2017-03-14 15:22     ` Linus Walleij
2017-02-28 16:51 ` [PATCH v3 3/6] dt-bindings: iio: document interrupt trigger support Fabrice Gasnier
2017-02-28 16:51   ` Fabrice Gasnier
2017-02-28 16:51   ` Fabrice Gasnier
2017-03-05 12:16   ` Jonathan Cameron
2017-03-05 12:16     ` Jonathan Cameron
2017-03-05 12:16     ` Jonathan Cameron
2017-03-15 19:29     ` Rob Herring
2017-03-15 19:29       ` Rob Herring
2017-03-15 19:29       ` Rob Herring
2017-02-28 16:51 ` [PATCH v3 4/6] iio: iio-interrupt-trigger: device-tree support Fabrice Gasnier
2017-02-28 16:51   ` Fabrice Gasnier
2017-02-28 16:51   ` Fabrice Gasnier
2017-03-05 12:18   ` Jonathan Cameron
2017-03-05 12:18     ` Jonathan Cameron
2017-03-05 12:18     ` Jonathan Cameron
2017-02-28 16:51 ` [PATCH v3 5/6] dt-bindings: iio: stm32-adc: add external interrupt trigger Fabrice Gasnier
2017-02-28 16:51   ` Fabrice Gasnier
2017-02-28 16:51   ` Fabrice Gasnier
2017-02-28 16:51 ` [PATCH v3 6/6] iio: adc: stm32: add support for EXTI trigger Fabrice Gasnier
2017-02-28 16:51   ` Fabrice Gasnier
2017-02-28 16:51   ` Fabrice Gasnier
2017-03-03 11:45   ` Lars-Peter Clausen [this message]
2017-03-03 11:45     ` Lars-Peter Clausen
2017-03-03 11:45     ` Lars-Peter Clausen
2017-03-03 13:00     ` Fabrice Gasnier
2017-03-03 13:00       ` Fabrice Gasnier
2017-03-03 13:00       ` Fabrice Gasnier
2017-03-03 15:46       ` Lars-Peter Clausen
2017-03-03 15:46         ` Lars-Peter Clausen
2017-03-03 15:46         ` Lars-Peter Clausen
2017-03-03 15:47         ` Lars-Peter Clausen
2017-03-03 15:47           ` Lars-Peter Clausen
2017-03-03 15:47           ` Lars-Peter Clausen
2017-03-05 12:21   ` Jonathan Cameron
2017-03-05 12:21     ` Jonathan Cameron
2017-03-05 12:21     ` Jonathan Cameron
2017-03-05 12:28     ` Jonathan Cameron
2017-03-05 12:28       ` Jonathan Cameron
2017-03-05 12:28       ` 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=5be44ed9-2c86-ac51-d964-d231d5ca62fa@metafoo.de \
    --to=lars@metafoo.de \
    --cc=alexandre.torgue@st.com \
    --cc=benjamin.gaignard@linaro.org \
    --cc=benjamin.gaignard@st.com \
    --cc=devicetree@vger.kernel.org \
    --cc=fabrice.gasnier@st.com \
    --cc=jic23@kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=mcoquelin.stm32@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.