From: Rob Herring <robh@kernel.org>
To: Lee Jones <lee@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Joel Stanley <joel@jms.id.au>, Andrew Jeffery <andrew@aj.id.au>
Cc: devicetree@vger.kernel.org, openbmc@lists.ozlabs.org,
linux-gpio@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] Convert Aspeed SCU to DT schema
Date: Wed, 10 Aug 2022 10:16:33 -0600 [thread overview]
Message-ID: <20220810161635.73936-1-robh@kernel.org> (raw)
This short series converts the aspeed,ast2x00-scu binding to DT schema.
The binding is already in use in examples which unsurprisingly need fixes
with the schema added.
If someone wants to convert the remaining child node bindings, that would
be nice.
This is part of getting rid of the remaining ~40 cases of compatibles
without a schema in the examples.
Rob
Rob Herring (2):
dt-bindings: pinctrl: aspeed: Add missing properties to examples
dt-bindings: mfd: aspeed,ast2x00-scu: Convert to DT schema format
.../bindings/mfd/aspeed,ast2x00-scu.yaml | 110 ++++++++++++++++++
.../devicetree/bindings/mfd/aspeed-scu.txt | 48 --------
.../pinctrl/aspeed,ast2400-pinctrl.yaml | 6 +
.../pinctrl/aspeed,ast2500-pinctrl.yaml | 4 +
.../pinctrl/aspeed,ast2600-pinctrl.yaml | 6 +
5 files changed, 126 insertions(+), 48 deletions(-)
create mode 100644 Documentation/devicetree/bindings/mfd/aspeed,ast2x00-scu.yaml
delete mode 100644 Documentation/devicetree/bindings/mfd/aspeed-scu.txt
--
2.34.1
next reply other threads:[~2022-08-10 16:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 16:16 Rob Herring [this message]
2022-08-10 16:16 ` [PATCH 1/2] dt-bindings: pinctrl: aspeed: Add missing properties to examples Rob Herring
2022-08-22 11:13 ` Linus Walleij
2022-08-10 16:16 ` [PATCH 2/2] dt-bindings: mfd: aspeed,ast2x00-scu: Convert to DT schema format Rob Herring
2022-08-11 6:45 ` Krzysztof Kozlowski
2022-08-11 7:01 ` Lee Jones
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=20220810161635.73936-1-robh@kernel.org \
--to=robh@kernel.org \
--cc=andrew@aj.id.au \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.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).