From: Florian Vaussard <florian.vaussard@epfl.ch>
To: Benoit Cousson <b-cousson@ti.com>
Cc: Tony Lindgren <tony@atomide.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Javier Martinez Canillas <javier.martinez@collabora.co.uk>,
Anil Kumar <anilk4.v@gmail.com>,
linux-omap@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org,
Florian Vaussard <florian.vaussard@epfl.ch>
Subject: [PATCH 0/3] ARM: dts: OMAP3: Use constants with MTD devices
Date: Tue, 11 Jun 2013 16:48:55 +0200 [thread overview]
Message-ID: <1370962138-9631-1-git-send-email-florian.vaussard@epfl.ch> (raw)
Hello,
Legacy board files use constants from sizes.h and mtd/partitions.h
to declare MTD partitions. This series performs the same with DT.
Necessary headers are added (patch 1), a NAND node is added to
omap3-overo (patch 2), and remaining DTS are converted (patch 3).
Patch 2 was tested on the real hardware. For patch 3, the resulting
DTB were diff'ed. The MTDPART_SIZ_FULL constant was used in DTS, when
it was the case in legacy board files. The size cell is thus changed
inside the binary output, so testing on the hardware is welcome, even
if it should work transparently.
Note that inside omap3430-sdp.dts (nor@0,0), it appears with
this series that partitions 'kernel-nor' and 'filesystem-nor' overlaps
by (2*SZ_128K), which is probably not desired.
Regards,
Florian
Florian Vaussard (3):
ARM: dts: Add headers with constants for MTD partitions
ARM: dts: Add omap3-overo NAND flash memory binding
ARM: dts: OMAP3: Use MTD constants for OMAP3 boards
arch/arm/boot/dts/omap3-devkit8000.dts | 10 +++---
arch/arm/boot/dts/omap3-igep0020.dts | 10 +++---
arch/arm/boot/dts/omap3-igep0030.dts | 10 +++---
arch/arm/boot/dts/omap3-overo.dtsi | 50 ++++++++++++++++++++++++++++++
arch/arm/boot/dts/omap3.dtsi | 2 +
arch/arm/boot/dts/omap3430-sdp.dts | 28 ++++++++--------
include/dt-bindings/mtd/partitions.h | 12 +++++++
include/dt-bindings/sizes.h | 52 ++++++++++++++++++++++++++++++++
8 files changed, 145 insertions(+), 29 deletions(-)
create mode 100644 include/dt-bindings/mtd/partitions.h
create mode 100644 include/dt-bindings/sizes.h
--
1.7.5.4
next reply other threads:[~2013-06-11 14:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-11 14:48 Florian Vaussard [this message]
2013-06-11 14:48 ` [PATCH 1/3] ARM: dts: Add headers with constants for MTD partitions Florian Vaussard
2013-06-11 16:24 ` Stephen Warren
2013-06-11 17:28 ` Florian Vaussard
2013-06-12 13:05 ` Grant Likely
2013-06-19 9:19 ` Florian Vaussard
2013-06-11 14:48 ` [PATCH 2/3] ARM: dts: Add omap3-overo NAND flash memory binding Florian Vaussard
2013-06-11 14:48 ` [PATCH 3/3] ARM: dts: OMAP3: Use MTD constants for OMAP3 boards Florian Vaussard
2013-06-11 15:29 ` Javier Martinez Canillas
2013-06-11 17:30 ` Florian Vaussard
2013-06-12 13:11 ` Grant Likely
2013-06-11 16:27 ` Stephen Warren
2013-06-11 17:31 ` Florian Vaussard
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=1370962138-9631-1-git-send-email-florian.vaussard@epfl.ch \
--to=florian.vaussard@epfl.ch \
--cc=anilk4.v@gmail.com \
--cc=b-cousson@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=javier.martinez@collabora.co.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=swarren@wwwdotorg.org \
--cc=tony@atomide.com \
/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).