devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Johan Hovold <johan@kernel.org>
Cc: linux-kernel@vger.kernel.org,
	Linus Walleij <linus.walleij@linaro.org>,
	devicetree@vger.kernel.org, Krzysztof Kozlowski <krzk@kernel.org>
Subject: [PATCH 2/5 v2] dt-bindings: gnss: Modify u-blox to use common bindings
Date: Thu, 17 Mar 2022 23:58:41 +0100	[thread overview]
Message-ID: <20220317225844.1262643-2-linus.walleij@linaro.org> (raw)
In-Reply-To: <20220317225844.1262643-1-linus.walleij@linaro.org>

This modifies the existing U-Blox GNSS bindings to reference
the common GNSS YAML bindings.

Fixed an unrelated whitespace error while at it.

Cc: devicetree@vger.kernel.org
Cc: Krzysztof Kozlowski <krzk@kernel.org>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
---
ChangeLog v1->v2:
- Change additionalProperties to unevaluatedProperties and
  cut the :true insertion of properties from the common
  props so new common properties get available immediately.
---
 .../devicetree/bindings/gnss/u-blox,neo-6m.yaml    | 14 +++++---------
 1 file changed, 5 insertions(+), 9 deletions(-)

diff --git a/Documentation/devicetree/bindings/gnss/u-blox,neo-6m.yaml b/Documentation/devicetree/bindings/gnss/u-blox,neo-6m.yaml
index 396101a223e7..35a760cfd343 100644
--- a/Documentation/devicetree/bindings/gnss/u-blox,neo-6m.yaml
+++ b/Documentation/devicetree/bindings/gnss/u-blox,neo-6m.yaml
@@ -6,6 +6,9 @@ $schema: http://devicetree.org/meta-schemas/core.yaml#
 
 title: U-blox GNSS Receiver Device Tree Bindings
 
+allOf:
+  - $ref: gnss-common.yaml#
+
 maintainers:
   - Johan Hovold <johan@kernel.org>
 
@@ -29,27 +32,20 @@ properties:
     description: >
       Main voltage regulator
 
-  timepulse-gpios:
-    maxItems: 1
-    description: >
-      Time pulse GPIO
-
   u-blox,extint-gpios:
     maxItems: 1
     description: >
       GPIO connected to the "external interrupt" input pin
-  
+
   v-bckp-supply:
     description: >
       Backup voltage regulator
 
-  current-speed: true
-
 required:
   - compatible
   - vcc-supply
 
-additionalProperties: false
+unevaluatedProperties: false
 
 examples:
   - |
-- 
2.35.1


  reply	other threads:[~2022-03-17 23:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-17 22:58 [PATCH 1/5 v2] dt-bindings: gnss: Rewrite common bindings in YAML Linus Walleij
2022-03-17 22:58 ` Linus Walleij [this message]
2022-03-18  9:13   ` [PATCH 2/5 v2] dt-bindings: gnss: Modify u-blox to use common bindings Krzysztof Kozlowski
2022-03-20 18:54   ` Rob Herring
2022-03-17 22:58 ` [PATCH 3/5 v2] dt-bindings: gnss: Rewrite sirfstar binding in YAML Linus Walleij
2022-03-18  9:29   ` Krzysztof Kozlowski
2022-03-20 18:58     ` Rob Herring
2022-03-22  0:01       ` Linus Walleij
2022-03-17 22:58 ` [PATCH 4/5 v2] dt-bindings: gnss: Add two more chips Linus Walleij
2022-03-18  9:29   ` Krzysztof Kozlowski
2022-03-21 18:59   ` Rob Herring
2022-03-17 22:58 ` [PATCH 5/5 v2] dt-bindings: gnss: Rewrite Mediatek bindings in YAML Linus Walleij
2022-03-18  9:33   ` Krzysztof Kozlowski
2022-03-20 18:53 ` [PATCH 1/5 v2] dt-bindings: gnss: Rewrite common " Rob Herring

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220317225844.1262643-2-linus.walleij@linaro.org \
    --to=linus.walleij@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=johan@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).