aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTony Lindgren2014-11-03 17:45:01 -0800
committerTony Lindgren2014-11-03 17:45:01 -0800
commit9995772a6d70196ccf0295e4a1cfbb7e4c4a0ef1 (patch)
tree05372680506ce4d143ab2c3d7956632241cb5215
parent35ac051e019431ccdfdaa9d71e08123870770de2 (diff)
ARM: OMAP2+: Require proper GPMC timings for devices
Now that we have timings in the .dts files for smc91x and 8250, we can remove the device specific checks and just print out the bootloader timings for devices that may not have timings in the .dts files. Acked-by: Roger Quadros <rogerq@ti.com> Signed-off-by: Tony Lindgren <tony@atomide.com>
-rw-r--r--arch/arm/mach-omap2/gpmc.c16
1 files changed, 0 insertions, 16 deletions
diff --git a/arch/arm/mach-omap2/gpmc.c b/arch/arm/mach-omap2/gpmc.c
index eee7065a5020..a7554ac3f37c 100644
--- a/arch/arm/mach-omap2/gpmc.c
+++ b/arch/arm/mach-omap2/gpmc.c
@@ -1713,22 +1713,6 @@ static int gpmc_probe_generic_child(struct platform_device *pdev,
}
/*
- * For some GPMC devices we still need to rely on the bootloader
- * timings because the devices can be connected via FPGA. So far
- * the list is smc91x on the omap2 SDP boards, and 8250 on zooms.
- * REVISIT: Add timing support from slls644g.pdf and from the
- * lan91c96 manual.
- */
- if (of_device_is_compatible(child, "ns16550a") ||
- of_device_is_compatible(child, "smsc,lan91c94") ||
- of_device_is_compatible(child, "smsc,lan91c111")) {
- dev_warn(&pdev->dev,
- "%s using bootloader timings on CS%d\n",
- child->name, cs);
- goto no_timings;
- }
-
- /*
* FIXME: gpmc_cs_request() will map the CS to an arbitary
* location in the gpmc address space. When booting with
* device-tree we want the NOR flash to be mapped to the