From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vladimir Zapolskiy Subject: [PATCH 0/7] ARM: dts: lpc32xx: nonfunctional updates to ea3250 and phy3250 dts Date: Tue, 26 Apr 2016 03:37:23 +0300 Message-ID: <1461631050-10479-1-git-send-email-vz@mleia.com> Return-path: Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Rob Herring , Pawel Moll , Mark Rutland , Sylvain Lemieux , Russell King Cc: Arnd Bergmann , Roland Stigge , devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org List-Id: devicetree@vger.kernel.org The change updates DTS files of PHY3250 and EA3250 boards powered by NXP LPC3250 SoC: * flatten board DTS files by exploiting device node labels, * add 'partitions' device node for MTD OF, * correct Atmel vendor prefix, * rename board DTS files by adding SoC name prefix. The change is wanted to have to prevent similar issues on copy-paste in case if more DTS files for LPC32xx boards are submitted. No functional changes are intended. Vladimir Zapolskiy (7): ARM: dts: lpc32xx: ea3250: avoid extension of device nodes by absolute path ARM: dts: lpc32xx: ea3250: add NAND partitions device node ARM: dts: lpc32xx: ea3250: fix Atmel at24 eeprom vendor ARM: dts: lpc32xx: ea3250: add SoC name prefix to board dts file ARM: dts: lpc32xx: phy3250: avoid extension of device nodes by absolute path ARM: dts: lpc32xx: phy3250: add NAND partitions device node ARM: dts: lpc32xx: phy3250: add SoC name prefix to board dts file arch/arm/boot/dts/Makefile | 3 +- .../boot/dts/{ea3250.dts => lpc3250-ea3250.dts} | 229 ++++++++--------- .../boot/dts/{phy3250.dts => lpc3250-phy3250.dts} | 285 ++++++++++----------- 3 files changed, 256 insertions(+), 261 deletions(-) rename arch/arm/boot/dts/{ea3250.dts => lpc3250-ea3250.dts} (61%) rename arch/arm/boot/dts/{phy3250.dts => lpc3250-phy3250.dts} (43%) -- 2.1.4 -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html