ARM: OMAP4: remove control module address space from PHY and OTG

Now that we have a separate driver for the control module,
stop populating the control module device data in other modules
(PHY and OTG) device info.

Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
Acked-by: Tony Lindgren <tony@atomide.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

diff --git a/arch/arm/mach-omap2/omap_hwmod_44xx_data.c b/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
index 793f54ac7d14b7cae5117404a564d527414d3e50..624a7e84a68503dacc0424ab733f856ccea01dd4 100644 (file)
--- a/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
+++ b/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
@@ -2702,13 +2702,6 @@ static struct resource omap44xx_usb_phy_and_pll_addrs[] = {
                .end            = 0x4a0ae000,
                .flags          = IORESOURCE_MEM,
        },
-       {
-               /* XXX: Remove this once control module driver is in place */
-               .name           = "ctrl_dev",
-               .start          = 0x4a002300,
-               .end            = 0x4a002303,
-               .flags          = IORESOURCE_MEM,
-       },
        { }
 };
 
@@ -6156,12 +6149,6 @@ static struct omap_hwmod_addr_space omap44xx_usb_otg_hs_addrs[] = {
                .pa_end         = 0x4a0ab7ff,
                .flags          = ADDR_TYPE_RT
        },
-       {
-               /* XXX: Remove this once control module driver is in place */
-               .pa_start       = 0x4a00233c,
-               .pa_end         = 0x4a00233f,
-               .flags          = ADDR_TYPE_RT
-       },
        { }
 };