From: Eliav Farber <farbere@amazon.com>
To: <giometti@enneenne.com>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>,
<farbere@amazon.com>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: <ronenk@amazon.com>, <talel@amazon.com>, <hhhawa@amazon.com>,
<jonnyc@amazon.com>, <itamark@amazon.com>, <shellykz@amazon.com>,
<amitlavi@amazon.com>, <almogbs@amazon.com>
Subject: [PATCH 4/5] dt-bindings: pps: pps-gpio: introduce pulse-width properties
Date: Sun, 25 Jun 2023 14:21:33 +0000 [thread overview]
Message-ID: <20230625142134.33690-5-farbere@amazon.com> (raw)
In-Reply-To: <20230625142134.33690-1-farbere@amazon.com>
Add two new optional properties to calculate PPS pulse-width in nano
seconds:
- assert-pulse-width
- clear-pulse-width
Signed-off-by: Eliav Farber <farbere@amazon.com>
---
Documentation/devicetree/bindings/pps/pps-gpio.txt | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/Documentation/devicetree/bindings/pps/pps-gpio.txt b/Documentation/devicetree/bindings/pps/pps-gpio.txt
index 8d588e38c44e..9ecfd5fb3b63 100644
--- a/Documentation/devicetree/bindings/pps/pps-gpio.txt
+++ b/Documentation/devicetree/bindings/pps/pps-gpio.txt
@@ -18,6 +18,12 @@ Optional properties:
opposite of the assert edge (if assert is rising-edge then
clear is falling-edge and if assert is falling-edge then
clear is rising-edge).
+- assert-pulse-width: when present, assert pulse width will be calculated in
+ nano seconds.
+ It should be enabled only if 'capture-clear' is enabled.
+- clear-pulse-width: when present, clear pulse width will be calculated in
+ nano seconds.
+ It should be enabled only if 'capture-clear' is enabled.
Example:
pps {
--
2.40.1
next prev parent reply other threads:[~2023-06-25 14:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-25 14:21 [PATCH 0/5] Add PPS pulse-width support Eliav Farber
2023-06-25 14:21 ` [PATCH 1/5] pps: add pulse-width calculation in nsec Eliav Farber
2023-06-27 14:27 ` Rodolfo Giometti
2023-07-02 12:20 ` Farber, Eliav
2023-07-03 9:32 ` Rodolfo Giometti
2023-06-25 14:21 ` [PATCH 2/5] dt-bindings: pps: pps-gpio: introduce capture-clear property Eliav Farber
2023-06-25 15:46 ` Krzysztof Kozlowski
2023-06-28 8:47 ` Farber, Eliav
2023-07-01 8:34 ` Krzysztof Kozlowski
2023-06-25 14:21 ` [PATCH 3/5] pps: clients: gpio: add option to set capture-clear from device-tree Eliav Farber
[not found] ` <04d52b5d-700c-c5d3-07ae-d4b8ad4fc3cd@amazon.com>
2023-07-05 7:04 ` Rodolfo Giometti
2023-06-25 14:21 ` Eliav Farber [this message]
2023-06-25 15:48 ` [PATCH 4/5] dt-bindings: pps: pps-gpio: introduce pulse-width properties Krzysztof Kozlowski
2023-06-25 14:21 ` [PATCH 5/5] pps: clients: gpio: enable pps pulse-width calculations based on device-tree Eliav Farber
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=20230625142134.33690-5-farbere@amazon.com \
--to=farbere@amazon.com \
--cc=almogbs@amazon.com \
--cc=amitlavi@amazon.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=giometti@enneenne.com \
--cc=hhhawa@amazon.com \
--cc=itamark@amazon.com \
--cc=jonnyc@amazon.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=ronenk@amazon.com \
--cc=shellykz@amazon.com \
--cc=talel@amazon.com \
/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).