coreboot ARM: Get rid of HAVE_INIT_TIMER config option
There is redundancy in terms of use of init_timer. We have a Kconfig option to decide whether a board has init_timer as well as we use stub for init_timer in places where we do not have any init_timer defined. Thus, removing the Kconfig option. Henceforth, all boards that do not have init_timer functionality can include include a stub_timer if required. BUG=None BRANCH=None TEST=Compiled successfully for all mainboard/google/ boards as well as all the other boards that were compiling fine before this change using abuild still compile fine. No additional errors introduced because of this change Change-Id: Iaffec9ce92107e55d65cc7c9f317feeeba700242 Reviewed-on: https://chromium-review.googlesource.com/195250 Tested-by: Furquan Shaikh <furquan@chromium.org> Reviewed-by: Stefan Reinauer <reinauer@chromium.org> Commit-Queue: Furquan Shaikh <furquan@chromium.org>
This commit is contained in:
parent
d9558852c4
commit
9518c5d508
9 changed files with 4 additions and 32 deletions
|
|
@ -1,11 +1,7 @@
|
|||
#ifndef DELAY_H
|
||||
#define DELAY_H
|
||||
|
||||
#if CONFIG_HAVE_INIT_TIMER
|
||||
void init_timer(void);
|
||||
#else
|
||||
#define init_timer() do{} while(0)
|
||||
#endif
|
||||
|
||||
void udelay(unsigned usecs);
|
||||
void mdelay(unsigned msecs);
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue