From: Krzysztof Kozlowski <krzk@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>,
Johan Hovold <johan@kernel.org>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 2/4] dt-bindings: gnss: Modify u-blox to use common bindings
Date: Sat, 12 Mar 2022 12:41:35 +0100 [thread overview]
Message-ID: <61df8371-c5ef-9e68-f9ae-19c8d20c64dc@kernel.org> (raw)
In-Reply-To: <20220311235119.523374-2-linus.walleij@linaro.org>
On 12/03/2022 00:51, Linus Walleij wrote:
> 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
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> .../devicetree/bindings/gnss/u-blox,neo-6m.yaml | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 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..5dffe722777f 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,16 +32,13 @@ properties:
> description: >
> Main voltage regulator
>
> - timepulse-gpios:
> - maxItems: 1
> - description: >
> - Time pulse GPIO
> + timepulse-gpios: true
>
> u-blox,extint-gpios:
> maxItems: 1
> description: >
> GPIO connected to the "external interrupt" input pin
> -
> +
> v-bckp-supply:
> description: >
> Backup voltage regulator
I propose to change additionalProperties->unevaluatedProperties and
remove current-speed and timepulse-gpios. This way also new properties
from gnss-common can be easily used.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-03-12 11:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 23:51 [PATCH 1/4] dt-bindings: gnss: Rewrite common bindings in YAML Linus Walleij
2022-03-11 23:51 ` [PATCH 2/4] dt-bindings: gnss: Modify u-blox to use common bindings Linus Walleij
2022-03-12 11:41 ` Krzysztof Kozlowski [this message]
2022-03-11 23:51 ` [PATCH 3/4] dt-bindings: gnss: Rewrite sirfstar binding in YAML Linus Walleij
2022-03-12 3:41 ` Rob Herring
2022-03-11 23:51 ` [PATCH 4/4] dt-bindings: gnss: Add two more chips Linus Walleij
2022-03-12 11:44 ` Krzysztof Kozlowski
2022-03-12 11:39 ` [PATCH 1/4] dt-bindings: gnss: Rewrite common bindings in YAML Krzysztof Kozlowski
2022-03-17 17:54 ` Linus Walleij
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=61df8371-c5ef-9e68-f9ae-19c8d20c64dc@kernel.org \
--to=krzk@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=johan@kernel.org \
--cc=linus.walleij@linaro.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).