linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jic23@kernel.org (Jonathan Cameron)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 3/4] dt-bindings: iio: add support for GPIO triggers
Date: Sat, 18 Feb 2017 19:22:35 +0000	[thread overview]
Message-ID: <01819bd3-3d24-b1fc-04aa-52348ff7f3bf@kernel.org> (raw)
In-Reply-To: <1487347429-31761-4-git-send-email-fabrice.gasnier@st.com>

On 17/02/17 16:03, Fabrice Gasnier wrote:
> Document Industrial I/O GPIO trigger support.
> 
> Signed-off-by: Fabrice Gasnier <fabrice.gasnier@st.com>
Whilst I think this needs redoing for the interrupt trigger driver,
please be aware that bindings must be OS agnostic i.e. you can't
name things after linux specific subsystem.  We get a lot
of stick for the iio-hwmon bindings specifically for doing this!

Which makes this 'interesting' to describe.

Once we have it updated feedback from Rob and Mark will definitely be needed on
this one.

Jonathan
> ---
>  .../bindings/iio/trigger/iio-trig-gpio.txt         | 26 ++++++++++++++++++++++
>  1 file changed, 26 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/iio/trigger/iio-trig-gpio.txt
> 
> diff --git a/Documentation/devicetree/bindings/iio/trigger/iio-trig-gpio.txt b/Documentation/devicetree/bindings/iio/trigger/iio-trig-gpio.txt
> new file mode 100644
> index 0000000..a8dbf5c
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/trigger/iio-trig-gpio.txt
> @@ -0,0 +1,26 @@
> +Industrial I/O - GPIO based trigger
> +
> +GPIOs may be used as IIO trigger provider, when trigger is connected to
> +GPIO lines.
> +
> +Required properties:
> +- compatible: Should be "iio-gpio-trigger"
> +- gpios: Should specify one GPIO line used as trigger source.
> +  See Documentation/devicetree/bindings/gpio/gpio.txt
> +- #io-trigger-cells: Should be 0, as simple trigger provider.
> +  See Documentation/devicetree/bindings/iio/iio-bindings.txt
> +
> +Optional properties:
> +- label: String to specifiy trigger name.
> +- gpio-trigger-rising-edge: A rising edge on GPIO will trigger.
> +- gpio-trigger-falling-edge: A falling edge on GPIO will trigger.
> +  Note: Both rising and falling edge may be used. In case none of
> +  rising or falling edge is selected, rising edge is selected by
> +  default.
> +
> +Example:
> +	gpiotrig0: iio-gpio-trigger0 {
> +		#io-trigger-cells = <0>;
> +		compatible = "iio-gpio-trigger";
> +		gpios = <&gpioa 11 0>;
> +	}
> 

  reply	other threads:[~2017-02-18 19:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-17 16:03 [RFC 0/4] iio: trigger: Add OF support and GPIO based trigger Fabrice Gasnier
2017-02-17 16:03 ` [RFC 1/4] dt-bindings: iio: introduce trigger providers, consumers Fabrice Gasnier
2017-02-17 16:03 ` [RFC 2/4] iio: trigger: add OF support Fabrice Gasnier
2017-02-17 16:03 ` [RFC 3/4] dt-bindings: iio: add support for GPIO triggers Fabrice Gasnier
2017-02-18 19:22   ` Jonathan Cameron [this message]
2017-02-23 15:03   ` Linus Walleij
2017-02-23 15:45     ` Fabrice Gasnier
2017-02-17 16:03 ` [RFC 4/4] iio: trigger: add GPIO trigger Fabrice Gasnier
2017-02-17 16:16   ` Lars-Peter Clausen
2017-02-18 19:19     ` Jonathan Cameron
2017-02-20 16:24       ` Fabrice Gasnier
2017-02-25 16:21         ` Jonathan Cameron
2017-02-17 16:23 ` [RFC 0/4] iio: trigger: Add OF support and GPIO based trigger Daniel Baluta
2017-02-18 19:07   ` 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=01819bd3-3d24-b1fc-04aa-52348ff7f3bf@kernel.org \
    --to=jic23@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.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 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).