tegra124: clock: Add display clocks and functions

[oweals/u-boot.git] / arch / arm / include / asm / arch-omap4 / sys_proto.h

diff --git a/arch/arm/include/asm/arch-omap4/sys_proto.h b/arch/arm/include/asm/arch-omap4/sys_proto.h
index b338a1566c6df3b02bc8c553ca1df7d23eca2991..f30f86539130ad1cb58485aa44a831202ba9537a 100644 (file)
--- a/arch/arm/include/asm/arch-omap4/sys_proto.h
+++ b/arch/arm/include/asm/arch-omap4/sys_proto.h
@@ -14,6 +14,7 @@
 #include <asm/omap_common.h>
 #include <linux/mtd/omap_gpmc.h>
 #include <asm/arch/mux_omap4.h>
+#include <asm/ti-common/sys_proto.h>
 
 DECLARE_GLOBAL_DATA_PTR;
 
@@ -21,6 +22,9 @@ extern const struct emif_regs emif_regs_elpida_200_mhz_2cs;
 extern const struct emif_regs emif_regs_elpida_380_mhz_1cs;
 extern const struct emif_regs emif_regs_elpida_400_mhz_1cs;
 extern const struct emif_regs emif_regs_elpida_400_mhz_2cs;
+extern const struct dmm_lisa_map_regs lisa_map_2G_x_1_x_2;
+extern const struct dmm_lisa_map_regs lisa_map_2G_x_2_x_2;
+extern const struct dmm_lisa_map_regs ma_lisa_map_2G_x_2_x_2;
 struct omap_sysinfo {
        char *board_string;
 };
@@ -31,10 +35,8 @@ void watchdog_init(void);
 u32 get_device_type(void);
 void do_set_mux(u32 base, struct pad_conf_entry const *array, int size);
 void set_muxconf_regs_essential(void);
-void sr32(void *, u32, u32, u32);
 u32 wait_on_value(u32, u32, void *, u32);
 void sdelay(unsigned long);
-void set_pl310_ctrl_reg(u32 val);
 void setup_clocks_for_console(void);
 void prcm_init(void);
 void bypass_dpll(u32 const base);
@@ -55,53 +57,6 @@ u32 warm_reset(void);
 void force_emif_self_refresh(void);
 void setup_warmreset_time(void);
 
-static inline u32 running_from_sdram(void)
-{
-       u32 pc;
-       asm volatile ("mov %0, pc" : "=r" (pc));
-       return ((pc >= OMAP44XX_DRAM_ADDR_SPACE_START) &&
-           (pc < OMAP44XX_DRAM_ADDR_SPACE_END));
-}
-
-static inline u8 uboot_loaded_by_spl(void)
-{
-       /*
-        * u-boot can be running from sdram either because of configuration
-        * Header or by SPL. If because of CH, then the romcode sets the
-        * CHSETTINGS executed bit to true in the boot parameter structure that
-        * it passes to the bootloader.This parameter is stored in the ch_flags
-        * variable by both SPL and u-boot.Check out for CHSETTINGS, which is a
-        * mandatory section if CH is present.
-        */
-       if ((gd->arch.omap_boot_params.ch_flags) & (CH_FLAGS_CHSETTINGS))
-               return 0;
-       else
-               return running_from_sdram();
-}
-/*
- * The basic hardware init of OMAP(s_init()) can happen in 4
- * different contexts:
- *  1. SPL running from SRAM
- *  2. U-Boot running from FLASH
- *  3. Non-XIP U-Boot loaded to SDRAM by SPL
- *  4. Non-XIP U-Boot loaded to SDRAM by ROM code using the
- *     Configuration Header feature
- *
- * This function finds this context.
- * Defining as inline may help in compiling out unused functions in SPL
- */
-static inline u32 omap_hw_init_context(void)
-{
-#ifdef CONFIG_SPL_BUILD
-       return OMAP_INIT_CONTEXT_SPL;
-#else
-       if (uboot_loaded_by_spl())
-               return OMAP_INIT_CONTEXT_UBOOT_AFTER_SPL;
-       else if (running_from_sdram())
-               return OMAP_INIT_CONTEXT_UBOOT_AFTER_CH;
-       else
-               return OMAP_INIT_CONTEXT_UBOOT_FROM_NOR;
-#endif
-}
+#define OMAP4_SERVICE_PL310_CONTROL_REG_SET    0x102
 
 #endif