ARM: AM335x: dts: Fix wrong GPMC size mapping for omaps
Patch is based on Linux upstream patch:
commit e2c5eb7
Author: Tony Lindgren <tony@atomide.com>

The GPMC binding is obviously very confusing as the values
are all over the place. People seem to confuse the GPMC partition
size for the chip select, and the device IO size within the GPMC
partition easily.

The ranges entry contains the GPMC partition size. And the
reg entry contains the size of the IO registers of the
device connected to the GPMC.

Let's fix the issue according to the following table:

Device GPMC partition size Device IO size
connected in the ranges entry in the reg entry

NAND 0x01000000 (16MB) 4
16550 0x01000000 (16MB) 8
smc91x 0x01000000 (16MB) 0xf
smc911x 0x01000000 (16MB) 0xff
OneNAND 0x01000000 (16MB) 0x20000 (128KB)
16MB NOR 0x01000000 (16MB) 0x01000000 (16MB)
32MB NOR 0x02000000 (32MB) 0x02000000 (32MB)
64MB NOR 0x04000000 (64MB) 0x04000000 (64MB)
128MB NOR 0x08000000 (128MB) 0x08000000 (128MB)
256MB NOR 0x10000000 (256MB) 0x10000000 (256MB)

Let's also add comments to the fixed entries while at it.

Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
1 parent 4dfa261 commit 76310b3e44e2d723f72e8a62fd8421e799edc499
@Daniel Schultz Daniel Schultz authored on 15 Jul 2015
Sascha Hauer committed on 16 Jul 2015
Showing 3 changed files
View
arch/arm/dts/am335x-phytec-phycard-som.dtsi
View
arch/arm/dts/am335x-phytec-phycore-som.dtsi
View
arch/arm/dts/am335x-phytec-phyflex-som.dtsi