mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: alejandroe1@geotab.com, Johan Hovold <johan@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2] dt-bindings: gnss: add u-blox,neo-9m compatible
Date: Thu, 22 May 2025 19:36:28 +0200	[thread overview]
Message-ID: <ab6bfdd7-13af-4abd-94e1-25fb3d0edb1c@kernel.org> (raw)
In-Reply-To: <20250522-ubx-m9-v2-1-6ecd470527bc@geotab.com>

On 22/05/2025 18:18, Alejandro Enrique via B4 Relay wrote:
> From: Alejandro Enrique <alejandroe1@geotab.com>
> 
> Add compatible for u-blox NEO-9M GPS module.
> 
> Signed-off-by: Alejandro Enrique <alejandroe1@geotab.com>
> ---
> This series just add the compatible string for u-blox NEO-9M module,
> using neo-m8 as fallback. I have tested the driver with such a module
> and it is working fine.
> ---
> Changes in v2:
> - Modify the binding to allow falling back to neo-m8
> - Remove compatible string from u-blox driver
> - Link to v1: https://lore.kernel.org/r/20250514-ubx-m9-v1-0-193973a4f3ca@geotab.com
> ---
>  Documentation/devicetree/bindings/gnss/u-blox,neo-6m.yaml | 25 +++++++++++++++++++++----
>  1 file changed, 21 insertions(+), 4 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/gnss/u-blox,neo-6m.yaml b/Documentation/devicetree/bindings/gnss/u-blox,neo-6m.yaml
> index 7d4b6d49e5eea2201ac05ba6d54b1c1721172f26..215f8931ca08c1b0954fc2f70eabe3ec8d89edea 100644
> --- a/Documentation/devicetree/bindings/gnss/u-blox,neo-6m.yaml
> +++ b/Documentation/devicetree/bindings/gnss/u-blox,neo-6m.yaml
> @@ -18,10 +18,16 @@ description: >
>  
>  properties:
>    compatible:
> -    enum:
> -      - u-blox,neo-6m
> -      - u-blox,neo-8
> -      - u-blox,neo-m8
> +    oneOf:
> +      - items:

Drop items here, just enum directly.

> +          - enum:
> +              - u-blox,neo-6m
> +              - u-blox,neo-8
> +              - u-blox,neo-m8
> +

Drop blank line.

> +      - items:
> +          - const: u-blox,neo-m9
> +          - const: u-blox,neo-m8
>  
>    reg:
>      description: >
> @@ -63,3 +69,14 @@ examples:
>              reset-gpios = <&gpio 1 GPIO_ACTIVE_LOW>;
>          };
>      };
> +  - |
> +    #include <dt-bindings/gpio/gpio.h>
> +
> +    serial {
> +        gnss {
> +            compatible = "u-blox,neo-m9", "u-blox,neo-m8";

No need for new example, it's the same as previous.


Best regards,
Krzysztof

  reply	other threads:[~2025-05-22 17:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-22 16:18 Alejandro Enrique via B4 Relay
2025-05-22 17:36 ` Krzysztof Kozlowski [this message]
2025-05-23 11:11   ` Alejandro Enrique

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=ab6bfdd7-13af-4abd-94e1-25fb3d0edb1c@kernel.org \
    --to=krzk@kernel.org \
    --cc=alejandroe1@geotab.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=johan@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@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

all inboxes | Powered by JetHome®