From: "Rob Herring (Arm)" <robh@kernel.org>
To: Harshit Shah <hshah@axiado.com>
Cc: Conor Dooley <conor+dt@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
soc@lists.linux.dev, Krzysztof Kozlowski <krzk+dt@kernel.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
linux-gpio@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3/6] dt-bindings: gpio: gpio-cdns: convert to YAML
Date: Sat, 14 Jun 2025 21:55:05 -0500 [thread overview]
Message-ID: <174995610418.3364372.5364960681855010915.robh@kernel.org> (raw)
In-Reply-To: <20250614-axiado-ax3000-soc-and-evaluation-board-support-v1-3-327ab344c16d@axiado.com>
On Sat, 14 Jun 2025 18:12:49 -0700, Harshit Shah wrote:
> Convert Cadence family GPIO controller bindings to DT schema.
>
> Changes during conversion:
> - update the naming as per the other files.
> - add gpio maintainers
>
> Signed-off-by: Harshit Shah <hshah@axiado.com>
> ---
> .../devicetree/bindings/gpio/cdns,gpio.txt | 43 ------------
> .../devicetree/bindings/gpio/gpio-cdns.yaml | 81 ++++++++++++++++++++++
> 2 files changed, 81 insertions(+), 43 deletions(-)
>
My bot found errors running 'make dt_binding_check' on your patch:
yamllint warnings/errors:
dtschema/dtc warnings/errors:
doc reference errors (make refcheckdocs):
See https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20250614-axiado-ax3000-soc-and-evaluation-board-support-v1-3-327ab344c16d@axiado.com
The base for the series is generally the latest rc1. A different dependency
should be noted in *this* patch.
If you already ran 'make dt_binding_check' and didn't see the above
error(s), then make sure 'yamllint' is installed and dt-schema is up to
date:
pip3 install dtschema --upgrade
Please check and re-submit after running the above command yourself. Note
that DT_SCHEMA_FILES can be set to your schema file to speed up checking
your schema. However, it must be unset to test all examples with your schema.
next prev parent reply other threads:[~2025-06-15 2:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-15 1:12 [PATCH 0/6] Axiado AX3000 SoC and Evaluation Board Support Harshit Shah
2025-06-15 1:12 ` [PATCH 1/6] dt-bindings: vendor-prefixes: Add Axiado Corporation Harshit Shah
2025-06-15 1:12 ` [PATCH 2/6] dt-bindings: arm: axiado: add AX3000 EVK compatible strings Harshit Shah
2025-06-15 2:55 ` Rob Herring (Arm)
2025-06-16 2:35 ` Harshit Shah
2025-06-15 1:12 ` [PATCH 3/6] dt-bindings: gpio: gpio-cdns: convert to YAML Harshit Shah
2025-06-15 2:55 ` Rob Herring (Arm) [this message]
2025-06-16 2:09 ` Harshit Shah
2025-06-15 1:12 ` [PATCH 4/6] arm64: dts: axiado: Add initial support for AX3000 SoC and eval board Harshit Shah
2025-06-15 1:12 ` [PATCH 5/6] arm64: add support for ARCH_AXIADO Harshit Shah
2025-06-15 1:12 ` [PATCH 6/6] MAINTAINERS: Add entry for AXIADO Harshit Shah
2025-06-15 2:25 ` kernel test robot
2025-06-16 4:25 ` 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=174995610418.3364372.5364960681855010915.robh@kernel.org \
--to=robh@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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox