[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180530143822.lvtwjvbqe7gvbvgq@localhost>
Date: Wed, 30 May 2018 07:38:22 -0700
From: Richard Cochran <richardcochran@...il.com>
To: Johan Hovold <johan@...nel.org>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Andreas Kemnade <andreas@...nade.info>,
Arnd Bergmann <arnd@...db.de>,
"H . Nikolaus Schaller" <hns@...delico.com>,
Pavel Machek <pavel@....cz>,
Marcel Holtmann <marcel@...tmann.org>,
Sebastian Reichel <sebastian.reichel@...labora.co.uk>,
Tony Lindgren <tony@...mide.com>, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org
Subject: Re: [PATCH v2 0/8] gnss: add new GNSS subsystem
On Wed, May 30, 2018 at 12:32:34PM +0200, Johan Hovold wrote:
> Another possible extension is to add generic 1PPS support.
There are two possibilities to consider.
1. If the PPS causes an interrupt, then it should hook into the PPS
subsystem.
2. If the PPS is a HW signal routed for example to the input pin of a
MAC based PTP Hardware Clock (PHC), then it would make sense to
model the GNSS device as a PHC as well. This PHC would be readable
but not writable, and more importantly it would offer an output
signal. Then user space could use the existing interfaces to
dial the PPS signal from one device the another.
(Come to think of it, modeling the GNSS as PHC would also give you the
interface for #1 as well.)
Thanks,
Richard
Powered by blists - more mailing lists