From: Krzysztof Kozlowski <krzk@kernel.org>
To: Harshit Shah <hshah@axiado.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Arnd Bergmann <arnd@arndb.de>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-gpio@vger.kernel.org,
soc@lists.linux.dev
Subject: Re: [PATCH v2 3/6] dt-bindings: gpio: gpio-cdns: convert to YAML
Date: Mon, 16 Jun 2025 08:05:05 +0200 [thread overview]
Message-ID: <67b1a8d3-e695-4ea6-8405-1a8563cbf5f2@kernel.org> (raw)
In-Reply-To: <20250615-axiado-ax3000-soc-and-evaluation-board-support-v2-3-341502d38618@axiado.com>
On 16/06/2025 06:31, Harshit Shah wrote:
> Convert Cadence family GPIO controller bindings to DT schema.
>
> Changes during conversion:
> - update the naming as per the other files.
You made it entirely different than every other file and review.
> - add gpio maintainers
Not really, you need to find someone interested in that hardware, not
subsystem maintainers.
>
> Signed-off-by: Harshit Shah <hshah@axiado.com>
> ---
> .../devicetree/bindings/gpio/cdns,gpio.txt | 43 ------------
> .../devicetree/bindings/gpio/gpio-cdns.yaml | 81 ++++++++++++++++++++++
Previous filename was correct.
> 2 files changed, 81 insertions(+), 43 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/gpio/cdns,gpio.txt b/Documentation/devicetree/bindings/gpio/cdns,gpio.txt
> deleted file mode 100644
> index 706ef00f5c64951bb29c79a5541db4397e8b2733..0000000000000000000000000000000000000000
> --- a/Documentation/devicetree/bindings/gpio/cdns,gpio.txt
> +++ /dev/null
> @@ -1,43 +0,0 @@
> -Cadence GPIO controller bindings
> -
...
> diff --git a/Documentation/devicetree/bindings/gpio/gpio-cdns.yaml b/Documentation/devicetree/bindings/gpio/gpio-cdns.yaml
> new file mode 100644
> index 0000000000000000000000000000000000000000..e71f0137912f88e69fb3fa20f096e1572211591c
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/gpio/gpio-cdns.yaml
> @@ -0,0 +1,81 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/gpio/gpio-cdns.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Cadence GPIO Controller
> +
> +maintainers:
> + - Linus Walleij <linus.walleij@linaro.org>
> + - Bartosz Golaszewski <brgl@bgdev.pl>
> +
> +properties:
> + compatible:
> + const: cdns,gpio-r1p02
> +
> + reg:
> + minItems: 1
Why this is min and unconstrained...
> +
> + clocks:
> + maxItems: 1
But this is max?
maxItems: 1 in both cases (so clocks are correct, but why writing
similar things entirely different?).
> +
> + ngpios:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description: Number of GPIO lines supported, maximum 32.
> +
> + gpio-controller: true
> +
> + "#gpio-cells":
> + const: 2
> + description: |
> + - First cell is the GPIO line number.
> + - Second cell is flags as defined in <dt-bindings/gpio/gpio.h>,
> + only GPIO_ACTIVE_HIGH and GPIO_ACTIVE_LOW supported.
> +
> + interrupt-controller: true
> +
> + "#interrupt-cells":
> + const: 2
> + description: |
> + - First cell is the GPIO line number used as IRQ.
> + - Second cell is the trigger type, as defined in
> + <dt-bindings/interrupt-controller/irq.h>.
> +
> + interrupts:
> + maxItems: 1
> +
> +required:
> + - compatible
> + - reg
> + - clocks
> + - gpio-controller
> + - "#gpio-cells"
> +
> +if:
> + required: [interrupt-controller]
> +then:
> + required:
> + - interrupts
> + - "#interrupt-cells"
Drop last one, core schema requires it.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-06-16 6:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 4:31 [PATCH v2 0/6] Axiado AX3000 SoC and Evaluation Board Support Harshit Shah
2025-06-16 4:31 ` [PATCH v2 1/6] dt-bindings: vendor-prefixes: Add Axiado Corporation Harshit Shah
2025-06-16 4:31 ` [PATCH v2 2/6] dt-bindings: arm: axiado: add AX3000 EVK compatible strings Harshit Shah
2025-06-16 6:05 ` Krzysztof Kozlowski
2025-06-16 21:13 ` Harshit Shah
2025-06-17 6:08 ` Krzysztof Kozlowski
2025-06-16 4:31 ` [PATCH v2 3/6] dt-bindings: gpio: gpio-cdns: convert to YAML Harshit Shah
2025-06-16 6:05 ` Krzysztof Kozlowski [this message]
2025-06-18 21:09 ` Harshit Shah
2025-06-16 4:31 ` [PATCH v2 4/6] arm64: dts: axiado: Add initial support for AX3000 SoC and eval board Harshit Shah
2025-06-16 6:09 ` Krzysztof Kozlowski
2025-06-19 22:41 ` Harshit Shah
2025-06-20 6:08 ` Krzysztof Kozlowski
2025-06-20 21:18 ` Harshit Shah
2025-06-22 9:49 ` Krzysztof Kozlowski
2025-06-23 5:56 ` Harshit Shah
2025-06-23 6:04 ` Krzysztof Kozlowski
2025-06-16 6:10 ` Krzysztof Kozlowski
2025-06-19 23:52 ` Harshit Shah
2025-06-16 13:57 ` Rob Herring
2025-06-19 23:09 ` Harshit Shah
2025-06-16 4:31 ` [PATCH v2 5/6] arm64: add support for ARCH_AXIADO Harshit Shah
2025-06-16 4:31 ` [PATCH v2 6/6] MAINTAINERS: Add entry for AXIADO Harshit Shah
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=67b1a8d3-e695-4ea6-8405-1a8563cbf5f2@kernel.org \
--to=krzk@kernel.org \
--cc=arnd@arndb.de \
--cc=brgl@bgdev.pl \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hshah@axiado.com \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=soc@lists.linux.dev \
--cc=will@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.