[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <06f74b54-91fa-31c5-f015-52a6524059ef@metafoo.de>
Date: Fri, 17 Feb 2017 17:16:26 +0100
From: Lars-Peter Clausen <lars@...afoo.de>
To: Fabrice Gasnier <fabrice.gasnier@...com>, jic23@...nel.org,
linux@...linux.org.uk, robh+dt@...nel.org,
linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Cc: linux-iio@...r.kernel.org, mark.rutland@....com,
mcoquelin.stm32@...il.com, alexandre.torgue@...com,
knaack.h@....de, pmeerw@...erw.net, benjamin.gaignard@...aro.org,
benjamin.gaignard@...com, linus.walleij@...aro.org
Subject: Re: [RFC 4/4] iio: trigger: add GPIO trigger
On 02/17/2017 05:03 PM, Fabrice Gasnier wrote:
> GPIOs can be used to generate triggers for any IIO device.
> Introduce generic GPIO trigger driver. It offers some options
> to tune polarity (e.g. rising/falling edge), and label so trigger
> name may be customized.
> By default, gpio triggers will be named gpiotrigX, where X is gpio
> number as returned by desc_to_gpio() call.
> Rising edge is selected if polarity isn't set.
If you want to use the GPIO only as an interrupt, just use it as an
interrupt directly, no need to go the route via the GPIO.
Powered by blists - more mailing lists