From: Shawn Guo <shawnguo@kernel.org>
To: Peng Fan <peng.fan@nxp.com>
Cc: "robh+dt@kernel.org" <robh+dt@kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"festevam@gmail.com" <festevam@gmail.com>,
dl-linux-imx <linux-imx@nxp.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] ARM: dts: imx: use generic name bus
Date: Thu, 13 Feb 2020 10:39:41 +0800 [thread overview]
Message-ID: <20200213023330.GK11096@dragon> (raw)
In-Reply-To: <1579156408-23739-2-git-send-email-peng.fan@nxp.com>
On Thu, Jan 16, 2020 at 06:37:57AM +0000, Peng Fan wrote:
> From: Peng Fan <peng.fan@nxp.com>
>
> Per devicetree specification, generic names
> are recommended to be used, such as bus.
>
> i.MX AIPS is a AHB - IP bridge bus, so
> we could use bus as node name.
>
> Script:
> sed -i "s/\<aips@/bus@/" arch/arm/boot/dts/imx*.dtsi
> sed -i "s/\<aips-bus@/bus@/" arch/arm/boot/dts/imx*.dtsi
>
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> ---
> arch/arm/boot/dts/imx25.dtsi | 4 ++--
> arch/arm/boot/dts/imx31.dtsi | 4 ++--
> arch/arm/boot/dts/imx35.dtsi | 4 ++--
> arch/arm/boot/dts/imx50.dtsi | 4 ++--
> arch/arm/boot/dts/imx51.dtsi | 4 ++--
> arch/arm/boot/dts/imx53.dtsi | 4 ++--
> arch/arm/boot/dts/imx6dl.dtsi | 4 ++--
> arch/arm/boot/dts/imx6q.dtsi | 2 +-
> arch/arm/boot/dts/imx6qdl.dtsi | 4 ++--
> arch/arm/boot/dts/imx6qp.dtsi | 2 +-
> arch/arm/boot/dts/imx6sl.dtsi | 4 ++--
> arch/arm/boot/dts/imx6sll.dtsi | 4 ++--
> arch/arm/boot/dts/imx6sx.dtsi | 6 +++---
> arch/arm/boot/dts/imx6ul.dtsi | 4 ++--
> arch/arm/boot/dts/imx6ull.dtsi | 2 +-
> arch/arm/boot/dts/imx7s.dtsi | 6 +++---
> 16 files changed, 31 insertions(+), 31 deletions(-)
We may want to cover Vybrid family (see vf500.dtsi, vfxxx.dtsi) as well.
Shawn
next prev parent reply other threads:[~2020-02-13 2:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 6:37 [PATCH 0/2] ARM/arm64: dts: freescale: use generic name bus Peng Fan
2020-01-16 6:37 ` [PATCH 1/2] ARM: dts: imx: " Peng Fan
2020-02-13 2:39 ` Shawn Guo [this message]
2020-02-13 3:15 ` Peng Fan
2020-01-16 6:38 ` [PATCH 2/2] arm64: dts: freescale: s32v234: " Peng Fan
2020-02-13 2:30 ` Shawn Guo
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=20200213023330.GK11096@dragon \
--to=shawnguo@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=peng.fan@nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.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).