Skip to content
Snippets Groups Projects
  • Kipisz, Steven's avatar
    93e6253d
    ARM: OMAP4/5: Centralize early clock initialization · 93e6253d
    Kipisz, Steven authored
    
    Early clock initialization is currently done in two stages for OMAP4/5
    SoCs. The first stage is the initialization of console clocks and
    then we initialize basic clocks for functionality necessary for SoC
    initialization and basic board functionality.
    
    By splitting up prcm_init and centralizing this clock initialization,
    we setup the code for follow on patches that can do board specific
    initialization such as board detection which will depend on these
    basic clocks.
    
    As part of this change, since the early clock initialization
    is centralized, we no longer need to expose the console clock
    initialization.
    
    NOTE: we change the sequence slightly by initializing console clocks
    timer after the io settings are complete, but this is not expected
    to have any functioanlity impact since we setup the basic IO drive
    strength initialization as part of do_io_settings.
    
    Signed-off-by: default avatarSteve Kipisz <s-kipisz2@ti.com>
    Reviewed-by: default avatarTom Rini <trini@konsulko.com>
    Reviewed-by: default avatarLokesh Vutla <lokeshvutla@ti.com>
    Reviewed-by: default avatarTom Rini <trini@konsulko.com>
    93e6253d
    History
    ARM: OMAP4/5: Centralize early clock initialization
    Kipisz, Steven authored
    
    Early clock initialization is currently done in two stages for OMAP4/5
    SoCs. The first stage is the initialization of console clocks and
    then we initialize basic clocks for functionality necessary for SoC
    initialization and basic board functionality.
    
    By splitting up prcm_init and centralizing this clock initialization,
    we setup the code for follow on patches that can do board specific
    initialization such as board detection which will depend on these
    basic clocks.
    
    As part of this change, since the early clock initialization
    is centralized, we no longer need to expose the console clock
    initialization.
    
    NOTE: we change the sequence slightly by initializing console clocks
    timer after the io settings are complete, but this is not expected
    to have any functioanlity impact since we setup the basic IO drive
    strength initialization as part of do_io_settings.
    
    Signed-off-by: default avatarSteve Kipisz <s-kipisz2@ti.com>
    Reviewed-by: default avatarTom Rini <trini@konsulko.com>
    Reviewed-by: default avatarLokesh Vutla <lokeshvutla@ti.com>
    Reviewed-by: default avatarTom Rini <trini@konsulko.com>
sys_proto.h 1.75 KiB