Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp637993imm; Thu, 31 May 2018 06:57:20 -0700 (PDT) X-Google-Smtp-Source: ADUXVKJxOOCvdO6BziPPkcykoec7/cfkeS8KiFPcbs7GYTivOqGairIyZld+klsvSXLHAv0GQv/3 X-Received: by 2002:a62:b03:: with SMTP id t3-v6mr6924460pfi.32.1527775040494; Thu, 31 May 2018 06:57:20 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1527775040; cv=none; d=google.com; s=arc-20160816; b=Q8gmHf+u9iy3KRpg7N6d+0uy/xmoobAzgdZSMtRyJnzBcu6rdt90Y7ApjSIphh0PwB 1MQVNC21WAHQGlHj8fa0NgFjCBSBCKWn4J50W74azBT53C5wNIyppZ98hGWTJw40cv0Y gORrSU5VRHTTgQ/ab+ZtqACMvmuFOS5qrOaMvoGvGwr1keLACHylmPtOHmxffHuUuZgL YWTcnVPUwYZKYxCfNRH1Ja2/LFpb2vKMYkI+Fj/qRuM2dFBBrrzgoPb8NxrP7kpzaIx7 c/VpSjWFD1vVAhLCyCflNX31K0jinA+o9QTUtPstqogELuq0bm9X0HofkSo1XGzdnUS1 zV5Q== 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 :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=CfD246VTQGO9Tj0E9Yo8rcmKfplgZ73JCIphmK3zU68=; b=ZZtzzNamTS14g+C7eGDjQIrpEa2Qp787VuUiwSOd0/nqz4+ebBKOPnaFEKT0O4kUbl qby1T38I4xmGaJfMBehBfW6Cun5ABO81+Z3Ev4Q8nWpFiF0h0KyjcXbRWHjB4F6JNEdQ DjoDlJyTQg/z1gmojF25Qxq/5sxJ2LoLaJKBF38Y2IrZ0yBgBxyayt550I8SCy1SYKrN wDI1i0QWj1RUx8ATKIsP5/BTowP//eZ+Q61rbrhIIq1bSJ0+3RFBgJ1l5RxBwNdP7krb 1+GjVclFF8T6cNWqda0cDePneSIpDf7QVg5kLQ4eCKCORdYvvCdgbugiarUVOfKrUisy YQNQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=utX1USII; 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 g2-v6si38626223pli.48.2018.05.31.06.57.06; Thu, 31 May 2018 06:57:20 -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=pass header.i=@kernel.org header.s=default header.b=utX1USII; 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 S1755369AbeEaNzh (ORCPT + 99 others); Thu, 31 May 2018 09:55:37 -0400 Received: from mail.kernel.org ([198.145.29.99]:34972 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755155AbeEaNzc (ORCPT ); Thu, 31 May 2018 09:55:32 -0400 Received: from mail-qt0-f178.google.com (mail-qt0-f178.google.com [209.85.216.178]) (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 1B3F8208B0; Thu, 31 May 2018 13:55:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1527774932; bh=yAmeJjYscS3ZgJa7p7aUMbidgqra5D6qs8RRWZ4thgQ=; h=In-Reply-To:References:From:Date:Subject:To:Cc:From; b=utX1USII5unwMikjiSxpC97k7rYy2aGrsMGYW51hGNJg6crMDvbumJtYXGwmLRFla LMiVTlgmFVSn7lIhTQxfFwZjVXlnnMt+cvzlyz1ncyOvlxRMxpVXQwuqtcH4TY+JYG WEpzEOdGMW7qM6UKD0th9xGQcHSBIQnvF4tFPwxc= Received: by mail-qt0-f178.google.com with SMTP id x34-v6so14627647qtk.5; Thu, 31 May 2018 06:55:32 -0700 (PDT) X-Gm-Message-State: APt69E1MGW3mbTbb6cOzZZiGCixuxZ06A/EddugVYaUbLwZXExVzoxM0 I6fkBQCrhiIS6q9YknPhLoJ1z35ZW5DizfMjsw== X-Received: by 2002:ac8:266f:: with SMTP id v44-v6mr7036317qtv.354.1527774931281; Thu, 31 May 2018 06:55:31 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a0c:9b02:0:0:0:0:0 with HTTP; Thu, 31 May 2018 06:55:10 -0700 (PDT) In-Reply-To: <20180531082241.GD3259@localhost> References: <20180530103242.20773-1-johan@kernel.org> <20180530103242.20773-5-johan@kernel.org> <20180531035805.GA16906@rob-hp-laptop> <20180531082241.GD3259@localhost> From: Rob Herring Date: Thu, 31 May 2018 08:55:10 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v2 4/8] dt-bindings: gnss: add u-blox binding To: Johan Hovold Cc: Greg Kroah-Hartman , 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 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 Thu, May 31, 2018 at 3:22 AM, Johan Hovold wrote: > On Wed, May 30, 2018 at 10:58:05PM -0500, Rob Herring wrote: >> On Wed, May 30, 2018 at 12:32:38PM +0200, Johan Hovold wrote: >> > Add binding for u-blox GNSS receivers. >> > >> > Note that the u-blox product names encodes form factor (e.g. "neo"), >> > chipset (e.g. "8") and variant (e.g. "q"), but that only formfactor and >> > chipset is used for the compatible strings (for now). >> > >> > Signed-off-by: Johan Hovold >> > --- >> > .../devicetree/bindings/gnss/u-blox.txt | 44 +++++++++++++++++++ >> > .../devicetree/bindings/vendor-prefixes.txt | 1 + >> > 2 files changed, 45 insertions(+) >> > create mode 100644 Documentation/devicetree/bindings/gnss/u-blox.txt >> > >> > diff --git a/Documentation/devicetree/bindings/gnss/u-blox.txt b/Documentation/devicetree/bindings/gnss/u-blox.txt >> > new file mode 100644 >> > index 000000000000..caef9ace0b0c >> > --- /dev/null >> > +++ b/Documentation/devicetree/bindings/gnss/u-blox.txt >> > @@ -0,0 +1,44 @@ >> > +u-blox GNSS Receiver DT binding >> > + >> > +The u-blox GNSS receivers can use UART, DDC (I2C), SPI and USB interfaces. >> > + >> > +Please see Documentation/devicetree/bindings/gnss/gnss.txt for generic >> > +properties. >> > + >> > +Required properties: >> > + >> > +- compatible : Must be one of >> >> mixture of space and tab here. > > Oops. Same single space character before the tab here in all three > binding docs (and in the in-tree slave_devices.txt which I think I used > as a template). Who wrote that crap? ;) > Do you want me to fix this even if this turns out to be the only thing > that needs to be addressed in a v3? No > >> > + >> > + "u-blox,neo-8" >> > + "u-blox,neo-m8" >> > + >> > +- vcc-supply : Main voltage regulator >> > + >> > +Required properties (DDC): >> > +- reg : DDC (I2C) slave address >> > + >> > +Required properties (SPI): >> > +- reg : SPI chip select address >> > + >> > +Required properties (USB): >> > +- reg : Number of the USB hub port or the USB host-controller port >> > + to which this device is attached >> > + >> > +Optional properties: >> > + >> > +- timepulse-gpios : Time pulse GPIO >> > +- u-blox,extint-gpios : External interrupt GPIO >> >> This should be interrupts property instead of a gpio. > > Contrary to what the name may suggest, this pin is actually an input > which can be used to control active power or to provide time or > frequency aiding data to the receiver (see section 1.13 in [1]). > > I only added it for completeness as the driver does not use it > currently. Remove, leave as is, or add "input" to the description as in: > > - u-blox,extint-gpios : External interrupt input GPIO Yes. You should also define the active level. Rob