[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180531133730.GJ3259@localhost>
Date: Thu, 31 May 2018 15:37:30 +0200
From: Johan Hovold <johan@...nel.org>
To: "H. Nikolaus Schaller" <hns@...delico.com>
Cc: Johan Hovold <johan@...nel.org>,
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
On Thu, May 31, 2018 at 03:33:41PM +0200, H. Nikolaus Schaller wrote:
> > Am 31.05.2018 um 13:47 schrieb Johan Hovold <johan@...nel.org>:
> > Using pps-gpio would not allow you to describe the hardware properly,
> > something which, for example, may be needed for power management (e.g.
> > to power on the GNSS receiver when the pps device is being accessed).
>
> Yes, that is indeed a very valid reason to do it that way as the pps-gpio
> seems to assume an always-on impulse source.
>
> On the other hand it looks as if the pps framework can't tell the
> source when to power on/off because it does not notify when it
> is being accessed or not:
>
> https://elixir.bootlin.com/linux/v4.17-rc7/source/drivers/pps/pps.c#L305
Yeah, we may need to address that when/if we get there.
Thanks,
Johan
Powered by blists - more mailing lists