mirror of https://lore.kernel.org/lkml/
 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 v6 1/4] dt-bindings: pps: descriptor-based gpio, capture-clear addition
Date: Tue, 13 Nov 2018 14:40:04 +1100	[thread overview]
Message-ID: <20181113034007.3878-2-tom@aussec.com> (raw)
In-Reply-To: <20181113034007.3878-1-tom@aussec.com>

This patch changes the devicetree bindings for the pps-gpio driver
from the integer based API to the descriptor based API.  It also adds
documentation for the device tree capture-clear option.

The change from integer based GPIO API to the descriptor based API
breaks backward compatibility for the devicetree.  This is due to
the descriptor based API appending "-gpio" or "-gpios" (see
Documentation/gpio/base.txt.)

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

diff --git a/Documentation/devicetree/bindings/pps/pps-gpio.txt b/Documentation/devicetree/bindings/pps/pps-gpio.txt
index 3683874832ae..f7789e48a022 100644
--- a/Documentation/devicetree/bindings/pps/pps-gpio.txt
+++ b/Documentation/devicetree/bindings/pps/pps-gpio.txt
@@ -5,19 +5,21 @@ a GPIO pin.
 
 Required properties:
 - compatible: should be "pps-gpio"
-- gpios: one PPS GPIO in the format described by ../gpio/gpio.txt
+- pps-gpios: one PPS GPIO in the format described by ../gpio/gpio.txt
 
 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 {
 		pinctrl-names = "default";
 		pinctrl-0 = <&pinctrl_pps>;
 
-		gpios = <&gpio1 26 GPIO_ACTIVE_HIGH>;
+		pps-gpios = <&gpio1 26 GPIO_ACTIVE_HIGH>;
 		assert-falling-edge;
+		capture-clear;
 
 		compatible = "pps-gpio";
 	};
-- 
2.12.3


  reply	other threads:[~2018-11-13  4:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-13  3:40 [PATCH v6 0/4] PPS: pps-gpio PPS ECHO implementation Tom Burkart
2018-11-13  3:40 ` Tom Burkart [this message]
2018-11-13  3:40   ` [PATCH v6 2/4] pps: descriptor-based gpio, capture-clear addition Tom Burkart
2018-11-13  3:40     ` [PATCH v6 3/4] dt-bindings: pps: pps-gpio PPS ECHO implementation Tom Burkart
2018-11-13  3:40       ` [PATCH v6 4/4] pps: pps-gpio pps-echo implementation Tom Burkart
2018-11-13 15:14     ` [PATCH v6 2/4] pps: descriptor-based gpio, capture-clear addition Richard Cochran
2018-11-14  9:25       ` tom burkart
2018-11-17 11:11     ` Philipp Zabel
2018-11-17 11:24       ` 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=20181113034007.3878-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

Powered by JetHome