Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp4323047imj; Tue, 12 Feb 2019 13:51:24 -0800 (PST) X-Google-Smtp-Source: AHgI3IaBXP/ySA/FSXMWsa397ZOwpUPi8tn9bAXBrAMD2zO59mBz1MaCMgRPs/P/5Gzm7RVBSarq X-Received: by 2002:a17:902:449:: with SMTP id 67mr6187764ple.310.1550008284015; Tue, 12 Feb 2019 13:51:24 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550008284; cv=none; d=google.com; s=arc-20160816; b=DhxkD5leYugp7eltIWiJckPR+aLliKKej6LdNmJpJH+UolXJ3F/TsqdWh60NPLqOtP EQ4ZmFMo7Rccg3k70EALWO8fSQDpsBvDjlL3CPTpeemYvS7ONjX0UqW1AiMmWCPLFegw UE8Qmie+14m81Yo96P5e5GWjGmq6nCIk5kNRoX0azJYK3Ht4naO+AfgnKHSjLe5heqmd RQ52BN5+NNgpBnX0JpcO1h5Buky9DfumfXHBZ+Yt9AA9r0sq5NBFKJ4RN4tO6skkijVI b1fyNY29CVJ0XGBvKC5D6uq/vi3jQZeVf4FuqSDHNb4Zo6avm1Fff1Qk508gXs66xJ6T 2Kwg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=jzqhJUdbuUQydYUT8mRay6HlN1YdfLqHqaH87cg3JQc=; b=nJicgHKvzH4ohIDeow1MWTAG65Gz/k0qKZYf9YjQjgmWGoxl3wTlUKMhdi0qKMGiTs 4ovbxzC/GuzwDDnyVIiQR29bXNs53FqM5AF1WN8k+Ze/62IosbIGasLna+jFHp0Gpla+ LihtOIRp1e/BmdJ5FAtqPCJh1Kmoek8xH8VvS8BCMB/f1ufsJnUN1cpW1b4rkIQy+Fb7 5V2su4jb66CUyXyphPUOW1ITlRFXeIo2M0QXhY9ylPxaFRuzsSD+GE9FTonwcKeOgSTL b3JJLrsqOKAsJqv6iPAhAB8hNQP10swTh0KaBH3k5y/VtpSs+KOFLiLWpQXOooDfhE2j cmdA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=QdssbfCL; 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=pass (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 34si6079870pgt.455.2019.02.12.13.51.08; Tue, 12 Feb 2019 13:51:23 -0800 (PST) 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=pass header.i=@kernel.org header.s=default header.b=QdssbfCL; 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=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732431AbfBLVTC (ORCPT + 99 others); Tue, 12 Feb 2019 16:19:02 -0500 Received: from mail.kernel.org ([198.145.29.99]:54788 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726565AbfBLVTC (ORCPT ); Tue, 12 Feb 2019 16:19:02 -0500 Received: from mail-qk1-f172.google.com (mail-qk1-f172.google.com [209.85.222.172]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 2A3B32081B; Tue, 12 Feb 2019 21:19:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1550006340; bh=b8USUSrg3lJKX89ykkFcbjrdlAPDyKVL3G6hd2eIKTM=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=QdssbfCLQx+1NjM8RrOrm7erZtinwVjJSa4a+r6GZrAp0tadbkmNAFQKP8lDSnx2t /fk514a292jF6WGM0psVno9umMFG/65mLK8EARg2npiOQmvQdMy1Q8UhhgODYecGFV vxO9Ieagwq/6/nV2T08oKRAQ1CVyeaZ5HjX38sIw= Received: by mail-qk1-f172.google.com with SMTP id x9so118980qkf.0; Tue, 12 Feb 2019 13:19:00 -0800 (PST) X-Gm-Message-State: AHQUAuZUuD74N0bLG91TBijdsBlo/1g7bjedM21EM7Me82bYhjE1vPDS OfGmJd46Ld+eXkvhxrMeHj/sfChzh4ph5XMWpQ== X-Received: by 2002:a37:5686:: with SMTP id k128mr3941140qkb.29.1550006339312; Tue, 12 Feb 2019 13:18:59 -0800 (PST) MIME-Version: 1.0 References: <1548693481-1162-1-git-send-email-lollivier@baylibre.com> <1548693481-1162-3-git-send-email-lollivier@baylibre.com> <20190130155016.GA26536@bogus> <20190211092251.GV4686@localhost> In-Reply-To: <20190211092251.GV4686@localhost> From: Rob Herring Date: Tue, 12 Feb 2019 15:18:46 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v3 2/4] dt-bindings: gnss: add mediatek binding To: Johan Hovold Cc: Loys Ollivier , devicetree@vger.kernel.org, Mark Rutland , "linux-kernel@vger.kernel.org" , Kevin Hilman , linux-amlogic@lists.infradead.org, "moderated list:ARM/Mediatek SoC support" , "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" , Martin Blumenstingl Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Feb 11, 2019 at 3:23 AM Johan Hovold wrote: > > On Wed, Jan 30, 2019 at 09:50:16AM -0600, Rob Herring wrote: > > On Mon, Jan 28, 2019 at 05:37:59PM +0100, Loys Ollivier wrote: > > > Add binding for Mediatek-based GNSS receivers. > > > > > > Signed-off-by: Loys Ollivier > > > --- > > > > > > v3: > > > Removed the I2C and SPI interfaces references. > > > Removed the "mediatek,mt3339" compatible line. > > > Added the optional propertied (reset, fix) > > > Added the pin names for the optional properties. > > > > > > v2: > > > Renamed bindings from Globaltop/gtop to Mediatek/mtk. > > > Moved current-speed as an optional propertie. > > > Removed the status line in the example. > > > Added "mediatek,mt3339" compatible. > > > > > > .../devicetree/bindings/gnss/mediatek.txt | 37 ++++++++++++++++++++++ > > > 1 file changed, 37 insertions(+) > > > create mode 100644 Documentation/devicetree/bindings/gnss/mediatek.txt > > > > > > diff --git a/Documentation/devicetree/bindings/gnss/mediatek.txt b/Documentation/devicetree/bindings/gnss/mediatek.txt > > > new file mode 100644 > > > index 000000000000..00650d81c5c8 > > > --- /dev/null > > > +++ b/Documentation/devicetree/bindings/gnss/mediatek.txt > > > @@ -0,0 +1,37 @@ > > > +Mediatek-based GNSS Receiver DT binding > > > + > > > +Mediatek chipsets are used in GNSS-receiver modules produced by several > > > +vendors and can use an UART interface. > > s/an/a/ > > > > + > > > +Please see Documentation/devicetree/bindings/gnss/gnss.txt for generic > > > +properties. > > > + > > > +Required properties: > > > + > > > +- compatible : Must be > > > + > > > + "globaltop,pa6h" > > > + > > > +- vcc-supply : Main voltage regulator (pin name: VCC) > > > + > > > +Optional properties: > > > + > > > +- gtop,reset-gpios : GPIO used to reset the device > > > + (pin name: RESET, NRESET) > > > > reset-gpios is the standard name. > > > > > +- gtop,fix-gpios : GPIO used to determine device position fix state > > > + (pin name: FIX, 3D_FIX) > > I'm thinking we might need a standard name for fix-gpios as well. This > isn't a feature that is globaltop (or mediatek) specific, and other > manufacturers provide similar functionality through pins named UI_FIX, > or even LCKIND (lock indicator). > > The pin is typically used to drive an indicator LED AFAIU, but the > characteristics of the signal varies from device to device (fw to fw), > for example, pulse when no lock and low otherwise, or pulse when a 2d or > 3d-fix is acquired, etc. > > I'm not sure how useful the pulsing would be for software, but someone > might find a use for it in some form. > > Rob, is this something we want to keep in the binding, and if so, how > about using a generic name such as "gnss-fix-gpios"? Sure. As long as details like being a pulse and when the pulse occurs are implied by compatible string. So we don't get an endless addition of properties to describe those. Rob