From: Rob Herring <robh@kernel.org>
To: Horatiu Vultur <horatiu.vultur@microchip.com>
Cc: robh+dt@kernel.org, UNGLinuxDriver@microchip.com,
linux-arm-kernel@lists.infradead.org, p.zabel@pengutronix.de,
devicetree@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org, Steen.Hegelund@microchip.com,
lars.povlsen@microchip.com, linus.walleij@linaro.org
Subject: Re: [PATCH v5 1/2] dt-bindings: pinctrl: pinctrl-microchip-sgpio: Add reset binding
Date: Fri, 15 Oct 2021 16:45:31 -0500 [thread overview]
Message-ID: <1634334331.621918.2254016.nullmailer@robh.at.kernel.org> (raw)
In-Reply-To: <20211015144259.219909-2-horatiu.vultur@microchip.com>
On Fri, 15 Oct 2021 16:42:58 +0200, Horatiu Vultur wrote:
> This describes the new binding which allows to call a reset driver from
> the pinctrl-microchip-sgpio driver.
>
> Signed-off-by: Horatiu Vultur <horatiu.vultur@microchip.com>
> ---
> .../devicetree/bindings/pinctrl/microchip,sparx5-sgpio.yaml | 3 +++
> 1 file changed, 3 insertions(+)
>
Running 'make dtbs_check' with the schema in this patch gives the
following warnings. Consider if they are expected or the schema is
incorrect. These may not be new warnings.
Note that it is not yet a requirement to have 0 warnings for dtbs_check.
This will change in the future.
Full log is available here: https://patchwork.ozlabs.org/patch/1541735
gpio@61101036c: 'reset-names' does not match any of the regexes: '^gpio@[0-1]$', 'pinctrl-[0-9]+'
arch/arm64/boot/dts/microchip/sparx5_pcb125.dt.yaml
arch/arm64/boot/dts/microchip/sparx5_pcb134.dt.yaml
arch/arm64/boot/dts/microchip/sparx5_pcb134_emmc.dt.yaml
arch/arm64/boot/dts/microchip/sparx5_pcb135.dt.yaml
arch/arm64/boot/dts/microchip/sparx5_pcb135_emmc.dt.yaml
gpio@611010484: 'reset-names' does not match any of the regexes: '^gpio@[0-1]$', 'pinctrl-[0-9]+'
arch/arm64/boot/dts/microchip/sparx5_pcb125.dt.yaml
arch/arm64/boot/dts/microchip/sparx5_pcb134.dt.yaml
arch/arm64/boot/dts/microchip/sparx5_pcb134_emmc.dt.yaml
arch/arm64/boot/dts/microchip/sparx5_pcb135.dt.yaml
arch/arm64/boot/dts/microchip/sparx5_pcb135_emmc.dt.yaml
gpio@61101059c: 'reset-names' does not match any of the regexes: '^gpio@[0-1]$', 'pinctrl-[0-9]+'
arch/arm64/boot/dts/microchip/sparx5_pcb125.dt.yaml
arch/arm64/boot/dts/microchip/sparx5_pcb134.dt.yaml
arch/arm64/boot/dts/microchip/sparx5_pcb134_emmc.dt.yaml
arch/arm64/boot/dts/microchip/sparx5_pcb135.dt.yaml
arch/arm64/boot/dts/microchip/sparx5_pcb135_emmc.dt.yaml
next prev parent reply other threads:[~2021-10-15 21:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 14:42 [PATCH v5 0/2] pinctrl: pinctrl-microchip-sgpio: Extend to call reset driver Horatiu Vultur
2021-10-15 14:42 ` [PATCH v5 1/2] dt-bindings: pinctrl: pinctrl-microchip-sgpio: Add reset binding Horatiu Vultur
2021-10-15 21:45 ` Rob Herring [this message]
2021-10-15 14:42 ` [PATCH v5 2/2] pinctrl: microchip sgpio: use reset driver Horatiu Vultur
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=1634334331.621918.2254016.nullmailer@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=Steen.Hegelund@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=horatiu.vultur@microchip.com \
--cc=lars.povlsen@microchip.com \
--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=p.zabel@pengutronix.de \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).