[PATCH 0/2] ARM: dts: OMAP3: Add GPMC controller and NAND memory to Overo
florian.vaussard at epfl.ch
Mon Jan 28 12:54:06 EST 2013
This is more an RFC serie, as an issue is still unclear to me.
Building on the work of Daniel Mack for the GPMC controller (staged
in Tony's tree ), it was easy to add the GPMC controller to OMAP3.
The issue comes from the Overo on-board NAND, as the amount of flash
depends on the revision. Currently, partitions are handled in the board
file using MTDPART_SIZ_FULL, but looking at the ofpart parser, the size
given to the parser must be fixed.
So how should we handle such case? Having several dtsi depending
on the Overo's revision would be a mess to my sense, considering
the non-conditional include inside the expansion boards' dts.
Or would it make sense to extend the DT binding for partitions?
This serie was tested on an Overo with 512MB of NAND.
 git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git omap-for-v3.9/gpmc
Florian Vaussard (2):
ARM: dts: OMAP3: Add GPMC controller
ARM: dts: OMAP3: Add NAND memory for Overo products
arch/arm/boot/dts/omap3-overo.dtsi | 49 ++++++++++++++++++++++++++++++++++++
arch/arm/boot/dts/omap3.dtsi | 11 ++++++++
2 files changed, 60 insertions(+), 0 deletions(-)
More information about the linux-arm-kernel