From: Shawn Guo <shawnguo2@yeah.net>
To: Fabio Estevam <festevam@gmail.com>
Cc: shawnguo@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, lukma@denx.de,
Fabio Estevam <festevam@denx.de>
Subject: Re: [PATCH] ARM: dts: imx23/8: Rename apbh and apbx nodes
Date: Tue, 3 Sep 2024 16:23:39 +0800 [thread overview]
Message-ID: <ZtbHi+vWQHIhBM3X@dragon> (raw)
In-Reply-To: <20240828194919.3192996-1-festevam@gmail.com>
On Wed, Aug 28, 2024 at 04:49:19PM -0300, Fabio Estevam wrote:
> From: Fabio Estevam <festevam@denx.de>
>
> According to simple-bus.yaml, apbh and apbx are not valid bus names.
>
> Rename them to apbh-bus and apbx-bus to fix the following dt-schema
> warnings:
>
> 'apbh@80000000' does not match '^([a-z][a-z0-9\\-]+-bus|bus|localbus|soc|axi|ahb|apb)(@.+)?$'
> 'apbx@80040000' does not match '^([a-z][a-z0-9\\-]+-bus|bus|localbus|soc|axi|ahb|apb)(@.+)?$'
>
> Signed-off-by: Fabio Estevam <festevam@denx.de>
> ---
> arch/arm/boot/dts/nxp/mxs/imx23-evk.dts | 4 ++--
> arch/arm/boot/dts/nxp/mxs/imx23-olinuxino.dts | 4 ++--
> arch/arm/boot/dts/nxp/mxs/imx23-sansa.dts | 4 ++--
> arch/arm/boot/dts/nxp/mxs/imx23-stmp378x_devb.dts | 4 ++--
> arch/arm/boot/dts/nxp/mxs/imx23-xfi3.dts | 4 ++--
> arch/arm/boot/dts/nxp/mxs/imx23.dtsi | 4 ++--
> arch/arm/boot/dts/nxp/mxs/imx28-cfa10037.dts | 2 +-
I think imx28-cfa10037.dts missed the change below.
@@ -14,7 +14,7 @@ / {
compatible = "crystalfontz,cfa10037", "crystalfontz,cfa10036", "fsl,imx28";
apb@80000000 {
- apbh@80000000 {
+ apbh-bus@80000000 {
pinctrl@80018000 {
usb_pins_cfa10037: usb-10037@0 {
reg = <0>;
I fixed it up.
Shawn
> arch/arm/boot/dts/nxp/mxs/imx28.dtsi | 4 ++--
> 8 files changed, 15 insertions(+), 15 deletions(-)
prev parent reply other threads:[~2024-09-03 8:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 19:49 [PATCH] ARM: dts: imx23/8: Rename apbh and apbx nodes Fabio Estevam
2024-08-29 9:08 ` Lukasz Majewski
2024-09-02 0:25 ` Shawn Guo
2024-09-03 8:23 ` Shawn Guo [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=ZtbHi+vWQHIhBM3X@dragon \
--to=shawnguo2@yeah.net \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@denx.de \
--cc=festevam@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lukma@denx.de \
--cc=robh@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).