From: Rob Herring <robh@kernel.org>
To: Michael Walle <michael@walle.cc>
Cc: devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-kernel@vger.kernel.org, Shawn Guo <shawnguo@kernel.org>,
Li Yang <leoyang.li@nxp.com>
Subject: Re: [PATCH v2] dt-bindings: fsl: convert fsl,layerscape-dcfg to YAML
Date: Mon, 25 Apr 2022 15:30:24 -0500 [thread overview]
Message-ID: <YmcE4K/qM5Xy0ADj@robh.at.kernel.org> (raw)
In-Reply-To: <20220425140433.33936-1-michael@walle.cc>
On Mon, 25 Apr 2022 16:04:33 +0200, Michael Walle wrote:
> Convert the fsl,layerscape-dcfg binding to the new YAML format.
>
> In the device trees, the device node always have a "syscon"
> compatible, which wasn't mentioned in the previous binding.
>
> One thing added here, compared to the original binding is the clock
> controller subnode of the LS1028A SoC and its "simple-mfd" compatible as
> used in arch/arm64/boot/dts/freescale/fsl-ls1028a.dtsi as well as the
> little-endian and big-endian properties.
>
> Signed-off-by: Michael Walle <michael@walle.cc>
> ---
> changes since v1:
> - moved to soc/fsl/fsl,layerscape-dcfg.yaml
> - generic name for node in example
> - mention added "syscon" compatible in commit message
> - reference specific clock controller
>
> .../arm/freescale/fsl,layerscape-dcfg.txt | 19 ------
> .../bindings/soc/fsl/fsl,layerscape-dcfg.yaml | 68 +++++++++++++++++++
> 2 files changed, 68 insertions(+), 19 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/arm/freescale/fsl,layerscape-dcfg.txt
> create mode 100644 Documentation/devicetree/bindings/soc/fsl/fsl,layerscape-dcfg.yaml
>
Applied, thanks!
prev parent reply other threads:[~2022-04-25 20:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 14:04 [PATCH v2] dt-bindings: fsl: convert fsl,layerscape-dcfg to YAML Michael Walle
2022-04-25 18:38 ` Krzysztof Kozlowski
2022-04-25 20:30 ` Rob Herring [this message]
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=YmcE4K/qM5Xy0ADj@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=leoyang.li@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@walle.cc \
--cc=robh+dt@kernel.org \
--cc=shawnguo@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).