From: Richard Cochran <richardcochran@gmail.com>
To: Yangbo Lu <yangbo.lu@nxp.com>
Cc: netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
"David S . Miller" <davem@davemloft.net>,
Rob Herring <robh+dt@kernel.org>, Shawn Guo <shawnguo@kernel.org>
Subject: Re: [v2, 3/5] dt-binding: ptp_qoriq: document "fsl,extts-fifo" property
Date: Thu, 17 Jan 2019 17:39:12 -0800 [thread overview]
Message-ID: <20190118013912.skj4x5wmkbouekfx@localhost> (raw)
In-Reply-To: <20190118013434.qwuiqi5iwo5gw2nk@localhost>
On Thu, Jan 17, 2019 at 05:34:34PM -0800, Richard Cochran wrote:
> > @@ -17,6 +17,7 @@ Clock Properties:
> > - fsl,tmr-fiper1 Fixed interval period pulse generator.
> > - fsl,tmr-fiper2 Fixed interval period pulse generator.
> > - fsl,max-adj Maximum frequency adjustment in parts per billion.
> > + - fsl,extts-fifo Required if hardware uses external trigger stamp FIFO.
>
> Does this take a Boolean value? Please explain the semantics.
How about this instead?
The presence of this property indicates hardware support for
the external trigger stamp FIFO.
Thanks,
Richard
next prev parent reply other threads:[~2019-01-18 1:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 1:49 [v2, 0/5] External trigger stamp fifo support for ptp_qoriq Yangbo Lu
2019-01-17 1:49 ` [v2, 1/5] ptp_qoriq: fix interrupt enabling and handling Yangbo Lu
2019-01-17 1:49 ` [v2, 2/5] ptp_qoriq: support external trigger stamp FIFO Yangbo Lu
2019-01-17 1:49 ` [v2, 3/5] dt-binding: ptp_qoriq: document "fsl,extts-fifo" property Yangbo Lu
2019-01-18 1:34 ` Richard Cochran
2019-01-18 1:39 ` Richard Cochran [this message]
2019-01-18 8:10 ` Y.b. Lu
2019-01-17 1:49 ` [v2, 4/5] ARM: dts: ls1021a: add 1588 external trigger stamp fifo support Yangbo Lu
2019-01-17 1:49 ` [v2, 5/5] ptp_qoriq: add fiper pulse loopback support Yangbo Lu
2019-01-18 1:44 ` Richard Cochran
2019-01-18 8:11 ` Y.b. Lu
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=20190118013912.skj4x5wmkbouekfx@localhost \
--to=richardcochran@gmail.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
--cc=yangbo.lu@nxp.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).