omap-common: Rename set_muxconf_regs_essential to set_muxconf_regs
There is no distinction between essential and non-essential mux configuration, so it doesn't make sense to have an "essential" prefix. Signed-off-by: Paul Kocialkowski <contact@paulk.fr>
This commit is contained in:
committed by
Tom Rini
parent
ed5ddebe96
commit
3ef56e61c8
@@ -30,7 +30,7 @@
|
||||
DECLARE_GLOBAL_DATA_PTR;
|
||||
|
||||
#if !defined(CONFIG_SPL_BUILD)
|
||||
inline void set_muxconf_regs_essential(void){};
|
||||
inline void set_muxconf_regs(void){};
|
||||
#endif
|
||||
|
||||
const struct omap_sysinfo sysinfo = {
|
||||
|
||||
@@ -75,10 +75,10 @@ const struct pad_conf_entry wkup_padconf_array_essential[] = {
|
||||
};
|
||||
|
||||
/*
|
||||
* Routine: set_muxconf_regs_essential
|
||||
* Routine: set_muxconf_regs
|
||||
* Description: setup board pinmux configuration.
|
||||
*/
|
||||
void set_muxconf_regs_essential(void)
|
||||
void set_muxconf_regs(void)
|
||||
{
|
||||
do_set_mux((*ctrl)->control_padconf_core_base,
|
||||
core_padconf_array_essential,
|
||||
|
||||
Reference in New Issue
Block a user