From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Michael Walle <michael@walle.cc>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Marc Zyngier <maz@kernel.org>,
linuxppc-dev@lists.ozlabs.org, Li Yang <leoyang.li@nxp.com>,
Thomas Gleixner <tglx@linutronix.de>,
Shawn Guo <shawnguo@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 2/2] dt-bindings: fsl: convert fsl,layerscape-scfg to YAML
Date: Mon, 25 Apr 2022 20:21:13 +0200 [thread overview]
Message-ID: <edcd5a65-26ef-a8de-be44-56aa63e485c3@linaro.org> (raw)
In-Reply-To: <20220425140214.32448-2-michael@walle.cc>
On 25/04/2022 16:02, Michael Walle wrote:
> Convert the fsl,layerscape-scfg 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.
>
> Also added, compared to the original binding, is the
> interrupt-controller subnode as used in arch/arm/boot/dts/ls1021a.dtsi
> as well as the litte-endian and big-endian properties.
>
> Signed-off-by: Michael Walle <michael@walle.cc>
> ---
> changes since v1:
> - moved to soc/fsl/fsl,layerscape-scfg.yaml
> - generic name for node in example
> - mention added "syscon" compatible in commit message
> - reference specific interrupt controller
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-04-25 18:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 14:02 [PATCH v2 1/2] dt-bindings: interrupt-controller: fsl, ls-extirq: convert to YAML Michael Walle
2022-04-25 14:02 ` [PATCH v2 2/2] dt-bindings: fsl: convert fsl,layerscape-scfg " Michael Walle
2022-04-25 18:21 ` Krzysztof Kozlowski [this message]
2022-04-25 18:36 ` [PATCH v2 1/2] dt-bindings: interrupt-controller: fsl, ls-extirq: convert " Krzysztof Kozlowski
2022-04-25 21:58 ` Michael Walle
2022-04-26 6:53 ` Krzysztof Kozlowski
2022-04-26 7:28 ` Michael Walle
2022-04-26 15:59 ` Krzysztof Kozlowski
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=edcd5a65-26ef-a8de-be44-56aa63e485c3@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maz@kernel.org \
--cc=michael@walle.cc \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
--cc=tglx@linutronix.de \
/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).