[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <943C21CA-EEC6-45E2-997E-A6E1FA0549EB@goldelico.com>
Date: Thu, 31 May 2018 11:52:18 +0200
From: "H. Nikolaus Schaller" <hns@...delico.com>
To: Johan Hovold <johan@...nel.org>
Cc: Richard Cochran <richardcochran@...il.com>,
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>, 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
> Am 31.05.2018 um 10:52 schrieb Johan Hovold <johan@...nel.org>:
>
> 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.
This seems to be duplicating functionality that is already solved by
https://elixir.bootlin.com/linux/v4.17-rc7/source/Documentation/devicetree/bindings/pps/pps-gpio.txt
and
https://elixir.bootlin.com/linux/v4.17-rc7/source/drivers/pps/clients/pps-gpio.c
Or what is bad with just using that?
BR,
Nikolaus
Powered by blists - more mailing lists