devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tom Burkart <tom@aussec.com>
To: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Cc: Tom Burkart <tom@aussec.com>, devicetree@vger.kernel.org
Subject: [PATCH v9 1/4] dt-bindings: pps: capture-clear addition
Date: Thu, 22 Nov 2018 20:45:59 +1100	[thread overview]
Message-ID: <20181122094602.5156-2-tom@aussec.com> (raw)
In-Reply-To: <20181122094602.5156-1-tom@aussec.com>

It adds documentation for the device tree capture-clear option.

Signed-off-by: Tom Burkart <tom@aussec.com>
---
 Documentation/devicetree/bindings/pps/pps-gpio.txt | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/Documentation/devicetree/bindings/pps/pps-gpio.txt b/Documentation/devicetree/bindings/pps/pps-gpio.txt
index 3683874832ae..1155d49c2699 100644
--- a/Documentation/devicetree/bindings/pps/pps-gpio.txt
+++ b/Documentation/devicetree/bindings/pps/pps-gpio.txt
@@ -10,6 +10,7 @@ Required properties:
 Optional properties:
 - assert-falling-edge: when present, assert is indicated by a falling edge
                        (instead of by a rising edge)
+- capture-clear: when present, also capture the PPS clear event
 
 Example:
 	pps {
@@ -18,6 +19,7 @@ Example:
 
 		gpios = <&gpio1 26 GPIO_ACTIVE_HIGH>;
 		assert-falling-edge;
+		capture-clear;
 
 		compatible = "pps-gpio";
 	};
-- 
2.12.3

       reply	other threads:[~2018-11-22  9:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20181122094602.5156-1-tom@aussec.com>
2018-11-22  9:45 ` Tom Burkart [this message]
     [not found]   ` <20181122094602.5156-3-tom@aussec.com>
2018-11-22  9:46     ` [PATCH v9 3/4] dt-bindings: pps: pps-gpio PPS ECHO implementation Tom Burkart
2018-11-26 19:42       ` Rob Herring
2018-11-27  4:06         ` tom burkart
2018-12-07 17:06           ` Rob Herring
2018-12-09  3:07             ` tom burkart
2018-12-11  2:17             ` tom burkart
2018-12-11 15:29               ` Rob Herring
2018-12-12  2:25                 ` tom burkart

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=20181122094602.5156-2-tom@aussec.com \
    --to=tom@aussec.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.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 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).