Received: by 10.192.165.148 with SMTP id m20csp5074731imm; Tue, 24 Apr 2018 13:14:59 -0700 (PDT) X-Google-Smtp-Source: AIpwx49vVWL+nfXGZBvaZ2hMIohSn7jPLzcAV2qvvef3WbHpN5PJB3NIhwkXsBAUR9ypnGw0H0FP X-Received: by 2002:a17:902:14cb:: with SMTP id y11-v6mr26254182plg.23.1524600899686; Tue, 24 Apr 2018 13:14:59 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1524600899; cv=none; d=google.com; s=arc-20160816; b=W8b7n/eny3WYeYH96FeeGThC7Brs/XqoDIlqZ4hkYkX35vKVTucSTBOwVZSoIDHkFG c9r9NEd2xE5dsrpyYVXwPl4+CreMjpbFbiBSu3lA7YXpSXj88VXWbj42Vpy/zldAfACp 6vpEVwXLVXKBhkGQL6eKshSAT5stp+sVvMIEBQlwbsVKq0xSph6ZVevMA/Px53nq5XoZ T4KbzaQiRxlkbR3DzwZI5MkdI0rpWL8sXSe69YPE/OEa2sbK5R5fhC+8L3HV5jabrz5O 0r0DZ4Mf3SvmQ/VKqVJkcJL3ObtpPQ/m/lyTlZGsZztPANlynqXsP06S8QhFKjVltIkj HEnw== 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:arc-authentication-results; bh=m8WaxDZmGfRwlecfV0adlt/s9x39yhyBcb6t8KoFqt8=; b=XGaAsuyIaip8W0BR9TcQ60OVXWShM3c07qYQjWDJqK8CJQhtC5aZfWDCCHWehmGV01 mVwaEyWT/vmUmOPKSVd8f9k+PEo8MQ8dd8nYlg3Z2W0vUp9VU8viZPBVuEWnA+NlsVcL DUhDUBl+SHvomItCMLB/HcKVs5BRdOt/tGxUMnh4SXp6Smx/9CaaYr8JSfnAFnivy3uR LDUxT2b99F2Zl19ix9XtjcxTbCRWfZe2RSzpyCnaoxRMgQkofKmnAIl/4eXo8iV/lHJn /hk5VPybHDVNnGJbVrJF/jOpM7DWO5bwf2rDT0JZTsi/YUl5sseFbZRfgRNx2YYD3rBa QyMA== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q15si12262519pgc.303.2018.04.24.13.14.44; Tue, 24 Apr 2018 13:14:59 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751037AbeDXUNW (ORCPT + 99 others); Tue, 24 Apr 2018 16:13:22 -0400 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:56501 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750766AbeDXUNU (ORCPT ); Tue, 24 Apr 2018 16:13:20 -0400 Received: by atrey.karlin.mff.cuni.cz (Postfix, from userid 512) id E758E8039C; Tue, 24 Apr 2018 22:13:18 +0200 (CEST) Date: Tue, 24 Apr 2018 22:13:19 +0200 From: Pavel Machek To: Johan Hovold Cc: Greg Kroah-Hartman , Rob Herring , Mark Rutland , Andreas Kemnade , Arnd Bergmann , "H . Nikolaus Schaller" , linux-kernel@vger.kernel.org, devicetree@vger.kernel.org Subject: Re: [PATCH 0/7] gnss: add new GNSS subsystem Message-ID: <20180424201318.GA14390@amd> References: <20180424163458.11947-1-johan@kernel.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="X1bOJ3K7DJ5YkBrT" Content-Disposition: inline In-Reply-To: <20180424163458.11947-1-johan@kernel.org> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --X1bOJ3K7DJ5YkBrT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! > This series adds a new subsystem for GNSS receivers (e.g. GPS > receivers). Actually... I'd just call it GPS subsystem. Yes, GPS is a bit misleading, but so is GNSS. We'd like Loran to use similar interface, right? We'd like to QZSS to use similar interface, too... https://www.pcworld.com/article/205325/japan_launches_its_first_gps_satelli= te.html =2E QZSS is not _global_ positioning system. Still they call it GPS. I'd call it GPS too. (Alternatively, we could have drivers/position and /dev/pos0...) Looking closer... I'm not sure if it makes sense to push different protocols (SiRF, NMEA, ...) through one device. Userland should know what protocol to expect... Yes, there will be common code between /dev/nmea0 and /dev/sirf0... I don't know. I'd really like to see '/dev/input/event0'-like layer, so that userland would not need to know about different protocols. But your work solves some problems we have now... Pavel --=20 (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo= g.html --X1bOJ3K7DJ5YkBrT Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlrfj94ACgkQMOfwapXb+vID3wCfaYeCgIwFkq8aiao6DhY5zrPh 2+QAoL9evS+5bkUhFLJOsItcsQ2fpDAh =x62g -----END PGP SIGNATURE----- --X1bOJ3K7DJ5YkBrT--