[PATCH] OMAP3: Beagle: NAND: Specifying partition offsets directly.

Hrishikesh Bhandiwad hrishikesh.b at ti.com
Mon Jul 25 09:07:23 EDT 2011


In the nand partition table specifying the offset addresses
directly instead of using the macro MTDPART_OFS_APPEND to gain
runtime efficiency while nand initialization.
MTDPART_OFS_APPEND has the value (-1) ,if assigned to offset,
a runtime calculation of actual offset happens each time nand is
initialized [ Refer: drivers/mtd/mtdpart.c: allocate_partition()].
To avoid this , specify actual offset.

Signed-off-by: Hrishikesh Bhandiwad <hrishikesh.b at ti.com>
---
 arch/arm/mach-omap2/board-omap3beagle.c |    8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/arch/arm/mach-omap2/board-omap3beagle.c b/arch/arm/mach-omap2/board-omap3beagle.c
index 7f21d24..09f7571 100644
--- a/arch/arm/mach-omap2/board-omap3beagle.c
+++ b/arch/arm/mach-omap2/board-omap3beagle.c
@@ -140,23 +140,23 @@ static struct mtd_partition omap3beagle_nand_partitions[] = {
 	},
 	{
 		.name		= "U-Boot",
-		.offset		= MTDPART_OFS_APPEND,	/* Offset = 0x80000 */
+		.offset		= 0x80000
 		.size		= 15 * NAND_BLOCK_SIZE,
 		.mask_flags	= MTD_WRITEABLE,	/* force read-only */
 	},
 	{
 		.name		= "U-Boot Env",
-		.offset		= MTDPART_OFS_APPEND,	/* Offset = 0x260000 */
+		.offset		= 0x260000
 		.size		= 1 * NAND_BLOCK_SIZE,
 	},
 	{
 		.name		= "Kernel",
-		.offset		= MTDPART_OFS_APPEND,	/* Offset = 0x280000 */
+		.offset		= 0x280000
 		.size		= 32 * NAND_BLOCK_SIZE,
 	},
 	{
 		.name		= "File System",
-		.offset		= MTDPART_OFS_APPEND,	/* Offset = 0x680000 */
+		.offset		= 0x680000
 		.size		= MTDPART_SIZ_FULL,
 	},
 };
-- 
1.6.2.4




More information about the linux-mtd mailing list