ARM: OMAP2+: Convert ONENAND to retrieve GPMC settings from DT
authorJon Hunter <jon-hunter@ti.com>
Mon, 25 Feb 2013 17:37:58 +0000 (11:37 -0600)
committerJon Hunter <jon-hunter@ti.com>
Thu, 4 Apr 2013 01:13:39 +0000 (20:13 -0500)
commit32cde0b5141030030f950a3c7e971018c81a9360
treea7f1e6b0af06947a0e32fe5aceb4f030e925dba2
parentacc79980c92ca9e8a39115b60ca832718a8156df
ARM: OMAP2+: Convert ONENAND to retrieve GPMC settings from DT

When booting with device-tree, retrieve GPMC settings for ONENAND from
the device-tree blob. This will allow us to remove all static settings
stored in the gpmc-nand.c in the future once the migration to
device-tree is complete.

The user must now specify the ONENAND device width in the device-tree
binding so that the GPMC can be programmed correctly. Therefore, update
the device-tree binding documentation for ONENAND devices connected to
the GPMC to reflect this.

Please note that this does not include GPMC timings for ONENAND. The
timings are being calculated at runtime.

There is some legacy code that only enables read wait monitoring for
non-OMAP3 devices. There are no known OMAP3 device issues that prevent
this feature being enabled and so when booting with device-tree use the
wait-monitoring settings described in the device-tree blob.

Signed-off-by: Jon Hunter <jon-hunter@ti.com>
Tested-by: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
Documentation/devicetree/bindings/mtd/gpmc-onenand.txt
arch/arm/mach-omap2/gpmc-onenand.c