linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Aleksander Jan Bajkowski <olek2@wp.pl>
Cc: linus.walleij@linaro.org, bgolaszewski@baylibre.com,
	john@phrozen.org, linux-gpio@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] dt-bindings: gpio: stp: add gphy3 and gphy4 properties
Date: Mon, 17 May 2021 20:19:57 -0500	[thread overview]
Message-ID: <20210518011957.GA3586154@robh.at.kernel.org> (raw)
In-Reply-To: <20210513210340.10466-2-olek2@wp.pl>

On Thu, May 13, 2021 at 11:03:40PM +0200, Aleksander Jan Bajkowski wrote:
> The xRX300 family has 3 and the xRX330 has 4 gphs. They can also control
> some pins of the gpio cascade. This patch documents the missing properties.
> 
> Signed-off-by: Aleksander Jan Bajkowski <olek2@wp.pl>
> ---
>  .../devicetree/bindings/gpio/gpio-stp-xway.yaml  | 16 ++++++++++++++++
>  1 file changed, 16 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/gpio/gpio-stp-xway.yaml b/Documentation/devicetree/bindings/gpio/gpio-stp-xway.yaml
> index a36acc98898c..beb755edf639 100644
> --- a/Documentation/devicetree/bindings/gpio/gpio-stp-xway.yaml
> +++ b/Documentation/devicetree/bindings/gpio/gpio-stp-xway.yaml
> @@ -84,6 +84,22 @@ properties:
>      minimum: 0x0
>      maximum: 0x7
>  
> +  lantiq,phy3:
> +    description:
> +      The gphy3 core can control 3 bits of the gpio cascade. Available on
> +      the xRX300 and xRX330 family.
> +    $ref: /schemas/types.yaml#/definitions/uint32
> +    minimum: 0x0
> +    maximum: 0x7
> +
> +  lantiq,phy4:

You could make these a pattern under patternProperties instead.

> +    description:
> +      The gphy4 core can control 3 bits of the gpio cascade. Available on
> +      the xRX330 family.
> +    $ref: /schemas/types.yaml#/definitions/uint32
> +    minimum: 0x0
> +    maximum: 0x7
> +
>    lantiq,rising:
>      description:
>        Use rising instead of falling edge for the shift register.
> -- 
> 2.30.2
> 

  reply	other threads:[~2021-05-18  1:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-13 21:03 [PATCH 1/2] dt-bindings: gpio: stp: convert to json-schema Aleksander Jan Bajkowski
2021-05-13 21:03 ` [PATCH 2/2] dt-bindings: gpio: stp: add gphy3 and gphy4 properties Aleksander Jan Bajkowski
2021-05-18  1:19   ` Rob Herring [this message]
2021-05-18  1:19 ` [PATCH 1/2] dt-bindings: gpio: stp: convert to json-schema 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=20210518011957.GA3586154@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=bgolaszewski@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=john@phrozen.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olek2@wp.pl \
    /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).