Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp373159imm; Thu, 31 May 2018 01:54:21 -0700 (PDT) X-Google-Smtp-Source: ADUXVKJ1qUrNwITNcKDh86XK151rvF8Ft1YvutMX5zkWdayUSF0A4y2LkqBhDQ61E3IZUHahro3o X-Received: by 2002:a17:902:7c83:: with SMTP id y3-v6mr6159348pll.51.1527756861436; Thu, 31 May 2018 01:54:21 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1527756861; cv=none; d=google.com; s=arc-20160816; b=vMo1cKtajuPhLg1mui6KAK5huxg8D9g1anqgyFDOLTcCCrIXm4Kwof2LtJKC9e6jZT Yx5Y9VNFvyf4YZWRUxjsV7l+M12zjlZXrbM1EGoc026g3Bp6Hnxcwqze90DLogzV92Wr +oVKswSIO+yaPNRUUGk2ir1hiHbiYhjBrypAncG/mGk8mUUx4moHNGmkWtQ2mZ5Vjb9z 0Al9uzEx+xS8cP36iNDLinE7sC8rSYgS/uAconqfuZgRv3xPmlKVavSJUFCeQvBDzL1Q co9ebVpOys8ST3wu2XOHJwnKLoPRpbJ5/ViKl58hxUbWlS0+kWfyzacBI9PZX2lwvf42 5Kfw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature:arc-authentication-results; bh=pZYQ+xyHZhMAnQlwZQIeHmNo1s3eC2W4i5Ucs/zRwIk=; b=SXPqFNH3ureauUlu798PIwyCSkEUpya98qGMcrSD+iNtxCbhKPT8lvqSoZUqViah2G 4JUcT0QSzFrr9C/zha4qz/QOD06OmP36HKzKslfqOSe4MttO+j2eh9ok9Hnslu531Y0S nbLPpmf4DEu20mAqg60J6h0c55UT8mcEndRlsllcL08RN0zhqpT46fIB2pjg5KqGT7Gp /2lLGigelk27Lxhddv0S07xjT/2uDYjOfKNvz5H2iqvM0FFEZ+Kdl3fuW+Vq7pgnB8Ny BbXIrKGkrE1QUm7wKIM1aI/h1W0sAHBXd5Oy6kBSE12ertZh1S4irhVDdOHt3Fn+G/Ae VuLg== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=ecnbKn9B; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x70-v6si10186559pgx.576.2018.05.31.01.54.06; Thu, 31 May 2018 01:54:21 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=ecnbKn9B; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754198AbeEaIwx (ORCPT + 99 others); Thu, 31 May 2018 04:52:53 -0400 Received: from mail-lf0-f65.google.com ([209.85.215.65]:45065 "EHLO mail-lf0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754053AbeEaIws (ORCPT ); Thu, 31 May 2018 04:52:48 -0400 Received: by mail-lf0-f65.google.com with SMTP id n3-v6so8571834lfe.12; Thu, 31 May 2018 01:52:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=pZYQ+xyHZhMAnQlwZQIeHmNo1s3eC2W4i5Ucs/zRwIk=; b=ecnbKn9BKlXYbS1a8vSzr/nHMtrMbtn+1ebf1Y/0C/YW/hUA5yNAkHNv320W8x1HZg PIJ/aQqh/gJFwSqCzRzkEYZroh/3Ego1yovo/s9DoSQ9V1m1Rownv5mBBOLr8Dn5ii5O /e4QdlFaWLqslSd2irUbeInC9wGRZuvvws2bSb8gUmbvrzdswf/Rli1VrYiLhJAT+4gl JpL3tOqw4l7WUtIGBJffw/TLm1359BKzdKE8txyEIBbjeUunWf4wKAZuA7OA8HjLcfvR 9TpvqME7KYh9F6+FsC4Mvp7oYk6FRstxAmH2PJQRKYOn9+klONA7hyP9qLI+PhXviT9Z 2/vg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=pZYQ+xyHZhMAnQlwZQIeHmNo1s3eC2W4i5Ucs/zRwIk=; b=QU+C2FVFzdPMy42oicyqA0vqdfF6zMm7faubOURTe2+NJ1RMkhnYnEKRInvW1zUFwz 82DgFzDXJCPkpJK9bQzP+hoy8oobgCCiKNt5uqlOWm0EQW265Xwz11CY1Ytf42PVlpC2 lIHywOTPvEYp2PBDoFsHN4YoXMNs9Dy/SwnbmhVKM/4Lay+cbDxRjuoMvwzB16N8PPTH Y0qyEV6kzedSUWBoL+apSFwP9ffjzKvizMIlAfcxLmEgKfhkSKikWVCglMZUrt5b7P9f 1UsXy+QsGxfgu0qjV78WiIT212a7RbI2+NrfFTaJxhFjNRLGeOHj+qeeA4UwFiXvlZCu S4JQ== X-Gm-Message-State: ALKqPwdaJ3yOPkLCZ1ZQk0Qk+eF/lZWU/3xnjg5ytzp3vHBD5UcZk1qg YFQnzmcVgl6gOD7+aCaejJY= X-Received: by 2002:a2e:5442:: with SMTP id y2-v6mr4346230ljd.11.1527756766852; Thu, 31 May 2018 01:52:46 -0700 (PDT) Received: from xi.terra (c-8bb2e655.07-184-6d6c6d4.bbcust.telenor.se. [85.230.178.139]) by smtp.gmail.com with ESMTPSA id s4-v6sm7503102ljh.9.2018.05.31.01.52.45 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 31 May 2018 01:52:45 -0700 (PDT) Received: from johan by xi.terra with local (Exim 4.90_1) (envelope-from ) id 1fOJK6-00070P-Kx; Thu, 31 May 2018 10:52:42 +0200 Date: Thu, 31 May 2018 10:52:42 +0200 From: Johan Hovold To: Richard Cochran Cc: Johan Hovold , Greg Kroah-Hartman , Rob Herring , Mark Rutland , Andreas Kemnade , Arnd Bergmann , "H . Nikolaus Schaller" , Pavel Machek , Marcel Holtmann , Sebastian Reichel , Tony Lindgren , linux-kernel@vger.kernel.org, devicetree@vger.kernel.org Subject: Re: [PATCH v2 0/8] gnss: add new GNSS subsystem Message-ID: <20180531085242.GE3259@localhost> References: <20180530103242.20773-1-johan@kernel.org> <20180530143822.lvtwjvbqe7gvbvgq@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180530143822.lvtwjvbqe7gvbvgq@localhost> User-Agent: Mutt/1.10.0 (2018-05-17) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.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. > 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