From: Tony Lindgren Date: Tue, 4 Nov 2014 01:45:01 +0000 (-0800) Subject: ARM: OMAP2+: Require proper GPMC timings for devices X-Git-Tag: v3.19-rc1~166^2~2^2~3 X-Git-Url: https://git.karo-electronics.de/?a=commitdiff_plain;h=9995772a6d70196ccf0295e4a1cfbb7e4c4a0ef1;p=karo-tx-linux.git 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 Signed-off-by: Tony Lindgren --- 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 @@ -1712,22 +1712,6 @@ static int gpmc_probe_generic_child(struct platform_device *pdev, goto no_timings; } - /* - * 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