Message ID | 20230921133202.5828-3-wsa+renesas@sang-engineering.com |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a05:612c:172:b0:3f2:4152:657d with SMTP id h50csp5324247vqi; Thu, 21 Sep 2023 21:52:44 -0700 (PDT) X-Google-Smtp-Source: AGHT+IFXHUneoZmA/qWUsRJ0mljoqbRZpswvYr3nEB2070VJaXI/2Rb9TIx7m0NPxFtXyuw/ATYV X-Received: by 2002:a05:6a20:1444:b0:140:2ec5:2bd3 with SMTP id a4-20020a056a20144400b001402ec52bd3mr2339933pzi.27.1695358364318; Thu, 21 Sep 2023 21:52:44 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1695358364; cv=none; d=google.com; s=arc-20160816; b=VjDFY7y4PsLKGfLBJIHaJFOK0zN4mnVIne9KJiURnQkTtc9mqpmxTxK//PpgLwEW8U 1Ig6mf0baPLxiRoLzPSd1thx1lsKKliRJpp5go3F/5iD/I5KoQ/w8w+I+pP5t/ViKNqZ nbVYEqsdk+FskOuw/Zr7E++qIihHDZa2c6gMn2uQvXimBfch39RlAJSyPdRoYcxEcBdu 0FsKSfZtTtwPQFQM+CP2Jqqcw9P5j9gbOFpUORRFpHkvbHv5E1VQTdPY6AYe4i0Wj0Qx 12b1JkA02tYdjaY4nlow8re3rw00mPpGEFxwdpWsJje2FHDRdyD734JNUQWQGI5PoLLu VZWQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=P2UTB5t8XD9NtlqSsq8WH+UKGF31k4LPyuXnRCJcSsU=; fh=lKIDu7o6PChJqMtvXL5KJ9TxG5mA831gYR4U/JDtSmU=; b=d1mbcut19iZTcndxFDHDi0ApkJ6dgofXvEh+Ii4k8UN7I11o+bMDepSkw6gJE/Df+9 u7Jsw98j5bJb9wjZ+4E+y2+G9Hf1MB+Wc1/bFpWCtjKGJPBFhCJiDqFLgNyF92WuwC21 5EImv9Lan/MOzCwxmNBsknSAjgtB2VZppYmvLCckzr1OZ/30MxvEdXdz3YsA/tr+plEx NZIIsvXyW0A7+eds6srCfejK+Xzr9I+uNCc7us13o2f3eKXJLwxdto/nekDHzv3pNUeQ txsDuAXS7kQwLgyUDL8DlHhU1UaFsZEm+qsbyQJ2tRCP2L0KP67OT74M1lut6HHEriJ3 XNdg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@sang-engineering.com header.s=k1 header.b=aQRTvRIo; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:3 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: from lipwig.vger.email (lipwig.vger.email. [2620:137:e000::3:3]) by mx.google.com with ESMTPS id a18-20020a63d412000000b00578b1a60710si3047250pgh.552.2023.09.21.21.52.44 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 21 Sep 2023 21:52:44 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:3 as permitted sender) client-ip=2620:137:e000::3:3; Authentication-Results: mx.google.com; dkim=pass header.i=@sang-engineering.com header.s=k1 header.b=aQRTvRIo; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:3 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by lipwig.vger.email (Postfix) with ESMTP id 68F8F83339D3; Thu, 21 Sep 2023 16:20:34 -0700 (PDT) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.10 at lipwig.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229877AbjIUXUY (ORCPT <rfc822;pwkd43@gmail.com> + 29 others); Thu, 21 Sep 2023 19:20:24 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42014 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229892AbjIUXUU (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Thu, 21 Sep 2023 19:20:20 -0400 Received: from mail.zeus03.de (www.zeus03.de [194.117.254.33]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7DAD478BF1 for <linux-kernel@vger.kernel.org>; Thu, 21 Sep 2023 10:34:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= sang-engineering.com; h=from:to:cc:subject:date:message-id :in-reply-to:references:mime-version:content-transfer-encoding; s=k1; bh=P2UTB5t8XD9NtlqSsq8WH+UKGF31k4LPyuXnRCJcSsU=; b=aQRTvR IoCDhpscqTqS5VyqB969XMkC7KAhmznJ6gBMwQb1g1R7DPY64LTt/yzJOMrq7CWD C0h6BfMfn2sR8cYw/0BCkgxE06v4opOIJA4pqlTX77OxMeMEg9ynsFhTZka6OW+g eEwQkRArMvYq3rfrFtPIktzJihiUbeUzkfQDpdF1tAQpyP4H5VxTmZt5lXDlDdDQ OnWIdM6VUbgA/WeiMQ/9BGPYRuyuv9qZhuawB+VWA1EJNZsfsd8dKhMsnCz2X0yy 51najsSf09NGgEgYyWml7ju2tHDYB+LlikF3jQn96M3Z07f5RhIRnhS4Xn+w/eFc Ft+LEjQ9mCueLt1w== Received: (qmail 964439 invoked from network); 21 Sep 2023 15:32:12 +0200 Received: by mail.zeus03.de with ESMTPSA (TLS_AES_256_GCM_SHA384 encrypted, authenticated); 21 Sep 2023 15:32:12 +0200 X-UD-Smtp-Session: l3s3148p1@qKP8hN4FxgcuciJ+ From: Wolfram Sang <wsa+renesas@sang-engineering.com> To: linux-renesas-soc@vger.kernel.org Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>, Conor Dooley <conor.dooley@microchip.com>, Geert Uytterhoeven <geert+renesas@glider.be>, Johan Hovold <johan@kernel.org>, Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, Conor Dooley <conor+dt@kernel.org>, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH v3 2/3] dt-bindings: gnss: u-blox: add "reset-gpios" binding Date: Thu, 21 Sep 2023 15:32:00 +0200 Message-Id: <20230921133202.5828-3-wsa+renesas@sang-engineering.com> X-Mailer: git-send-email 2.35.1 In-Reply-To: <20230921133202.5828-1-wsa+renesas@sang-engineering.com> References: <20230921133202.5828-1-wsa+renesas@sang-engineering.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lipwig.vger.email Precedence: bulk List-ID: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (lipwig.vger.email [0.0.0.0]); Thu, 21 Sep 2023 16:20:34 -0700 (PDT) X-getmail-retrieved-from-mailbox: INBOX X-GMAIL-THRID: 1777712092580913338 X-GMAIL-MSGID: 1777712092580913338 |
Series |
gnss: ubx: updates to support the Renesas KingFisher board
|
|
Commit Message
Wolfram Sang
Sept. 21, 2023, 1:32 p.m. UTC
Needed to enable this chip on a Renesas KingFisher board. Description copied over from the Mediatek driver which already supports it. Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com> Acked-by: Conor Dooley <conor.dooley@microchip.com> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be> --- Documentation/devicetree/bindings/gnss/u-blox,neo-6m.yaml | 5 +++++ 1 file changed, 5 insertions(+)
Comments
On Thu, Sep 21, 2023 at 03:32:00PM +0200, Wolfram Sang wrote: > Needed to enable this chip on a Renesas KingFisher board. What is needed? Please make the commit message self-contained. And what GNSS chip/module is this? This should also be included in the commit message. Do you have a link to a datasheet? None of the u-blox modules I've seen have a reset line so I'd like to where this came from and how it is intended to be used. > Description > copied over from the Mediatek driver which already supports it. The mediatek driver does not support managing a reset line, but the binding includes a description of this pin for completeness. Also you don't seem include any description of the property below (which is fine) so perhaps you can just drop this sentence. Johan
Hi Johan, > And what GNSS chip/module is this? This should also be included in the > commit message. Ok. UBlox Neo-M8. > Do you have a link to a datasheet? https://www.u-blox.com/sites/default/files/NEO-M8-FW3_DataSheet_UBX-15031086.pdf > None of the u-blox modules I've seen have a reset line so I'd like to > where this came from and how it is intended to be used. I didn't know that old modules did not have the reset pin. I thought they were simply not used, so far. This one has. Check pin8 in chapter 2.1 in the datasheet. > The mediatek driver does not support managing a reset line, but the > binding includes a description of this pin for completeness. Also you > don't seem include any description of the property below (which is fine) > so perhaps you can just drop this sentence. Correct. Kind regards, Wolfram
On Mon, Oct 23, 2023 at 08:52:25AM +0200, Wolfram Sang wrote: > > And what GNSS chip/module is this? This should also be included in the > > commit message. > > Ok. UBlox Neo-M8. > > > Do you have a link to a datasheet? > > https://www.u-blox.com/sites/default/files/NEO-M8-FW3_DataSheet_UBX-15031086.pdf > > > None of the u-blox modules I've seen have a reset line so I'd like to > > where this came from and how it is intended to be used. > > I didn't know that old modules did not have the reset pin. I thought > they were simply not used, so far. This one has. Check pin8 in chapter > 2.1 in the datasheet. Indeed. I must have looked at the datasheet of the older neo-6, which does not have a reset pin, before replying. Johan
diff --git a/Documentation/devicetree/bindings/gnss/u-blox,neo-6m.yaml b/Documentation/devicetree/bindings/gnss/u-blox,neo-6m.yaml index 4835a280b3bf..8e97e475613f 100644 --- a/Documentation/devicetree/bindings/gnss/u-blox,neo-6m.yaml +++ b/Documentation/devicetree/bindings/gnss/u-blox,neo-6m.yaml @@ -41,6 +41,9 @@ properties: description: > Backup voltage regulator + reset-gpios: + maxItems: 1 + required: - compatible - vcc-supply @@ -49,10 +52,12 @@ unevaluatedProperties: false examples: - | + #include <dt-bindings/gpio/gpio.h> serial { gnss { compatible = "u-blox,neo-8"; v-bckp-supply = <&gnss_v_bckp_reg>; vcc-supply = <&gnss_vcc_reg>; + reset-gpios = <&gpio 1 GPIO_ACTIVE_LOW>; }; };