All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Johan Hovold <johan@kernel.org>,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 3/5 v2] dt-bindings: gnss: Rewrite sirfstar binding in YAML
Date: Sun, 20 Mar 2022 14:58:44 -0400	[thread overview]
Message-ID: <Yjd5ZFzTHIl+NAWV@robh.at.kernel.org> (raw)
In-Reply-To: <67600921-a4ea-367e-6b45-c4a1a12ae88b@kernel.org>

On Fri, Mar 18, 2022 at 10:29:03AM +0100, Krzysztof Kozlowski wrote:
> On 17/03/2022 23:58, Linus Walleij wrote:
> > This rewrites the SiRFstar DT bindings in YAML.
> > 
> > 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: false to uneavaluatedProperties: false
> >   so new common properties get available immediately
> > - This should also make the checker robot happy about
> >   lna-supply
> > ---
> >  .../devicetree/bindings/gnss/sirfstar.txt     | 46 ------------
> >  .../devicetree/bindings/gnss/sirfstar.yaml    | 71 +++++++++++++++++++
> >  2 files changed, 71 insertions(+), 46 deletions(-)
> >  delete mode 100644 Documentation/devicetree/bindings/gnss/sirfstar.txt
> >  create mode 100644 Documentation/devicetree/bindings/gnss/sirfstar.yaml
> > 
> > diff --git a/Documentation/devicetree/bindings/gnss/sirfstar.txt b/Documentation/devicetree/bindings/gnss/sirfstar.txt
> > deleted file mode 100644
> > index f4252b6b660b..000000000000
> > --- a/Documentation/devicetree/bindings/gnss/sirfstar.txt
> > +++ /dev/null
> > @@ -1,46 +0,0 @@
> > -SiRFstar-based GNSS Receiver DT binding
> > -
> > -SiRFstar chipsets are used in GNSS-receiver modules produced by several
> > -vendors and can use UART, SPI or I2C interfaces.
> > -
> > -Please see Documentation/devicetree/bindings/gnss/gnss.txt for generic
> > -properties.
> > -
> > -Required properties:
> > -
> > -- compatible	: Must be one of
> > -
> > -			"fastrax,uc430"
> > -			"linx,r4"
> > -			"wi2wi,w2sg0004"
> > -			"wi2wi,w2sg0008i"
> > -			"wi2wi,w2sg0084i"
> > -
> > -- vcc-supply	: Main voltage regulator (pin name: 3V3_IN, VCC, VDD)
> > -
> > -Required properties (I2C):
> > -- reg		: I2C slave address
> > -
> > -Required properties (SPI):
> > -- reg		: SPI chip select address
> > -
> > -Optional properties:
> > -
> > -- sirf,onoff-gpios	: GPIO used to power on and off device (pin name: ON_OFF)
> > -- sirf,wakeup-gpios	: GPIO used to determine device power state
> > -			  (pin name: RFPWRUP, WAKEUP)
> > -- timepulse-gpios	: Time pulse GPIO (pin name: 1PPS, TM)
> > -
> > -Example:
> > -
> > -serial@1234 {
> > -	compatible = "ns16550a";
> > -
> > -	gnss {
> > -		compatible = "wi2wi,w2sg0084i";
> > -
> > -		vcc-supply = <&gnss_reg>;
> > -		sirf,onoff-gpios = <&gpio0 16 GPIO_ACTIVE_HIGH>;
> > -		sirf,wakeup-gpios = <&gpio0 17 GPIO_ACTIVE_HIGH>;
> > -	};
> > -};
> > diff --git a/Documentation/devicetree/bindings/gnss/sirfstar.yaml b/Documentation/devicetree/bindings/gnss/sirfstar.yaml
> > new file mode 100644
> > index 000000000000..9f80add3e61b
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/gnss/sirfstar.yaml
> > @@ -0,0 +1,71 @@
> > +# SPDX-License-Identifier: GPL-2.0
> > +%YAML 1.2
> > +---
> > +$id: http://devicetree.org/schemas/gnss/sirfstar.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: SiRFstar GNSS Receiver Device Tree Bindings
> > +
> > +allOf:
> > +  - $ref: gnss-common.yaml#
> 
> The allOf should be just before "properties:" (also in patch #2).
> 
> > +
> > +maintainers:
> > +  - Johan Hovold <johan@kernel.org>
> > +
> > +description:
> > +  The SiRFstar GNSS receivers have incarnated over the years in different
> > +  chips, starting from the SiRFstarIII which was a chip that was introduced in
> > +  2004 and used in a lot of dedicated GPS devices. In 2009 SiRF was acquired
> > +  by CSR (Cambridge Silicon Radio) and in 2012 the CSR GPS business was
> > +  acquired by Samsung, while some products remained with CSR. In 2014 CSR
> > +  was acquired by Qualcomm who still sell some of the SiRF products.
> > +
> > +  SiRF chips can be used over UART, I2C or SPI buses.
> > +
> > +properties:
> > +  compatible:
> > +    enum:
> > +      - fastrax,uc430
> > +      - linx,r4
> > +      - wi2wi,w2sg0004
> > +      - wi2wi,w2sg0008i
> > +      - wi2wi,w2sg0084i
> > +
> > +  reg:
> > +    description:
> > +      The I2C Address, SPI chip select address. Not required on UART buses.
> > +
> > +  vcc-supply:
> > +    description:
> > +      Main voltage regulator, pin names such as 3V3_IN, VCC, VDD.
> > +
> > +  timepulse-gpios:
> > +    description: Comes with pin names such as 1PPS or TM
> 
> You don't need this, I think. It's coming from gnss-common.yaml.

I fixed up both and applied.

Rob

  reply	other threads:[~2022-03-20 18:58 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 ` [PATCH 2/5 v2] dt-bindings: gnss: Modify u-blox to use common bindings Linus Walleij
2022-03-18  9:13   ` 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 [this message]
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=Yjd5ZFzTHIl+NAWV@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=johan@kernel.org \
    --cc=krzk@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.