From: Johan Hovold <johan@kernel.org>
To: Richard Cochran <richardcochran@gmail.com>
Cc: Johan Hovold <johan@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Andreas Kemnade <andreas@kemnade.info>,
Arnd Bergmann <arnd@arndb.de>,
"H . Nikolaus Schaller" <hns@goldelico.com>,
Pavel Machek <pavel@ucw.cz>,
Marcel Holtmann <marcel@holtmann.org>,
Sebastian Reichel <sebastian.reichel@collabora.co.uk>,
Tony Lindgren <tony@atomide.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 0/8] gnss: add new GNSS subsystem
Date: Thu, 31 May 2018 10:52:42 +0200 [thread overview]
Message-ID: <20180531085242.GE3259@localhost> (raw)
In-Reply-To: <20180530143822.lvtwjvbqe7gvbvgq@localhost>
On Wed, May 30, 2018 at 07:38:22AM -0700, Richard Cochran wrote:
> 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.
Registering a PPS child device is what I had in mind for this.
> 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.
Ok.
> (Come to think of it, modeling the GNSS as PHC would also give you the
> interface for #1 as well.)
Thanks
Johan
next prev parent reply other threads:[~2018-05-31 8:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 10:32 [PATCH v2 0/8] gnss: add new GNSS subsystem Johan Hovold
2018-05-30 10:32 ` [PATCH v2 1/8] gnss: add GNSS receiver subsystem Johan Hovold
2018-05-30 10:32 ` [PATCH v2 2/8] dt-bindings: add generic gnss binding Johan Hovold
2018-05-30 10:32 ` [PATCH v2 3/8] gnss: add generic serial driver Johan Hovold
2018-05-30 10:32 ` [PATCH v2 4/8] dt-bindings: gnss: add u-blox binding Johan Hovold
2018-05-31 3:58 ` Rob Herring
2018-05-31 8:22 ` Johan Hovold
2018-05-31 13:55 ` Rob Herring
2018-05-31 14:34 ` Johan Hovold
2018-05-31 15:58 ` Rob Herring
2018-06-01 8:15 ` Johan Hovold
2018-05-30 10:32 ` [PATCH v2 5/8] gnss: add driver for u-blox receivers Johan Hovold
2018-06-02 6:07 ` kbuild test robot
2018-06-02 6:07 ` [RFC PATCH] gnss: ubx_gserial_ops can be static kbuild test robot
2018-05-30 10:32 ` [PATCH v2 6/8] dt-bindings: gnss: add sirfstar binding Johan Hovold
2018-05-30 10:32 ` [PATCH v2 7/8] gnss: add driver for sirfstar-based receivers Johan Hovold
2018-05-30 10:32 ` [PATCH v2 8/8] gnss: add device type support Johan Hovold
2018-05-30 14:38 ` [PATCH v2 0/8] gnss: add new GNSS subsystem Richard Cochran
2018-05-31 8:52 ` Johan Hovold [this message]
2018-05-31 9:52 ` H. Nikolaus Schaller
2018-05-31 11:47 ` Johan Hovold
2018-05-31 13:33 ` H. Nikolaus Schaller
2018-05-31 13:37 ` Johan Hovold
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=20180531085242.GE3259@localhost \
--to=johan@kernel.org \
--cc=andreas@kemnade.info \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hns@goldelico.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=mark.rutland@arm.com \
--cc=pavel@ucw.cz \
--cc=richardcochran@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sebastian.reichel@collabora.co.uk \
--cc=tony@atomide.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).