From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: imx28-tx28: Fix alias DTC warnings
Date: Tue, 15 May 2018 14:42:36 +0800 [thread overview]
Message-ID: <20180515064234.GJ26863@dragon> (raw)
In-Reply-To: <1525693192-3579-1-git-send-email-festevam@gmail.com>
On Mon, May 07, 2018 at 08:39:52AM -0300, Fabio Estevam wrote:
> From: Fabio Estevam <fabio.estevam@nxp.com>
>
> Remove underscore from alias entries to fix the following DTC warnings
> with W=1:
>
> arch/arm/boot/dts/imx28-tx28.dtb: Warning (alias_paths): /aliases: aliases property name must include only lowercase and '-'
>
> Cc: Lothar Wa?mann <LW@KARO-electronics.de>
> Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com>
> ---
> arch/arm/boot/dts/imx28-tx28.dts | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/arch/arm/boot/dts/imx28-tx28.dts b/arch/arm/boot/dts/imx28-tx28.dts
> index e4f19f9b..a5d6c97 100644
> --- a/arch/arm/boot/dts/imx28-tx28.dts
> +++ b/arch/arm/boot/dts/imx28-tx28.dts
> @@ -56,11 +56,11 @@
> ds1339 = &ds1339;
> gpio5 = &gpio5;
> lcdif = &lcdif;
> - lcdif_23bit_pins = &tx28_lcdif_23bit_pins;
> - lcdif_24bit_pins = &lcdif_24bit_pins_a;
> - reg_can_xcvr = ®_can_xcvr;
> - spi_gpio = &spi_gpio;
> - spi_mxs = &ssp3;
> + lcdif-23bit-pins = &tx28_lcdif_23bit_pins;
> + lcdif-24bit-pins = &lcdif_24bit_pins_a;
> + reg-can-xcvr = ®_can_xcvr;
> + spigpio = &spi_gpio;
> + spi-mxs = &ssp3;
> stk5led = &user_led;
> usbotg = &usb0;
> };
> @@ -220,7 +220,7 @@
> linux,no-autorepeat;
> };
>
> - spi_gpio: spi-gpio {
> + spi_gpio: spi {
Not sure why the node name needs to be changed here.
Shawn
> compatible = "spi-gpio";
> #address-cells = <1>;
> #size-cells = <0>;
> --
> 2.7.4
>
next prev parent reply other threads:[~2018-05-15 6:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 11:39 [PATCH] ARM: dts: imx28-tx28: Fix alias DTC warnings Fabio Estevam
2018-05-15 6:42 ` Shawn Guo [this message]
2018-05-15 16:57 ` Fabio Estevam
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=20180515064234.GJ26863@dragon \
--to=shawnguo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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).