All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Lübbe" <jlu@pengutronix.de>
To: "Gary E. Miller" <gem@rellim.com>
Cc: linux-kernel@vger.kernel.org,
	Rodolfo Giometti <giometti@enneenne.com>,
	Ricardo Martin s <rasm@fe.up.pt>,
	James Nus s <jamesnuss@nanometrics.ca>
Subject: Re: [PATCH] PPS: Restore lost capture-clear option to pps-gpio module.
Date: Thu, 09 Apr 2015 15:05:09 +0200	[thread overview]
Message-ID: <1428584709.7346.25.camel@pengutronix.de> (raw)
In-Reply-To: <201504022004.t32K4xbW013508@spidey.rellim.com>

Hi Gary,

On Do, 2015-04-02 at 12:21 -0700, Gary E. Miller wrote:
> In the conversion from platform to device tree the capture-clear
> option was lost.
> 
> capture-clear is needed so that time_pps_fetch() will report both
> edges of each PPS pulse.  Both edges are needed so that userland
> programs, like gpsd, can autodetect the leading and trailing PPS
> edges.

This is intentional. The userspace program can configure which edges it
wants to capture at runtime. Only the polarity (assert-falling-edge) is
actually determined by the hardware and must be described in the device
tree.

Regards,
Jan
-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |


  reply	other threads:[~2015-04-09 13:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-02 19:21 [PATCH] PPS: Restore lost capture-clear option to pps-gpio module Gary E. Miller
2015-04-09 13:05 ` Jan Lübbe [this message]
2015-04-09 19:49   ` Gary E. Miller
2015-04-10  8:15     ` Jan Lübbe
2015-04-10 18:13       ` Gary E. Miller

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=1428584709.7346.25.camel@pengutronix.de \
    --to=jlu@pengutronix.de \
    --cc=gem@rellim.com \
    --cc=giometti@enneenne.com \
    --cc=jamesnuss@nanometrics.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rasm@fe.up.pt \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.