linux-kernel - Re: [PATCH] PPS: Restore lost capture-clear option to pps-gpio module.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 09 Apr 2015 15:05:09 +0200
From:	Jan Lübbe <jlu@...gutronix.de>
To:	"Gary E. Miller" <gem@...lim.com>
Cc:	linux-kernel@...r.kernel.org,
	Rodolfo Giometti <giometti@...eenne.com>,
	Ricardo Martin s <rasm@...up.pt>,
	James Nus s <jamesnuss@...ometrics.ca>
Subject: Re: [PATCH] PPS: Restore lost capture-clear option to pps-gpio
 module.

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 |

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/