From: Johan Hovold <johan@kernel.org>
To: "H. Nikolaus Schaller" <hns@goldelico.com>
Cc: Johan Hovold <johan@kernel.org>,
Richard Cochran <richardcochran@gmail.com>,
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>, 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 15:37:30 +0200 [thread overview]
Message-ID: <20180531133730.GJ3259@localhost> (raw)
In-Reply-To: <598825FD-67A5-4016-BCE8-A50517472B8F@goldelico.com>
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@kernel.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
prev parent reply other threads:[~2018-05-31 13:37 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
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 [this message]
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=20180531133730.GJ3259@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).