diff options
| author | Tom Rini <trini@konsulko.com> | 2017-05-13 02:33:17 (GMT) |
|---|---|---|
| committer | Tom Rini <trini@konsulko.com> | 2017-05-15 14:39:57 (GMT) |
| commit | d87f82967fc90ca23672451f55eeb2a36f2f36c7 (patch) | |
| tree | a2773f14be19e9b94b3836918cda885f8428102f /README | |
| parent | 89024ddc9ea63be4f71815a6a915fb3a58268d81 (diff) | |
| download | u-boot-d87f82967fc90ca23672451f55eeb2a36f2f36c7.tar.xz | |
omap5: Migrate CONFIG_OMAP_PLATFORM_RESET_TIME_MAX_USEC to Kconfig
While in theory this value could be used in places outside of "omap5"
(such as OMAP4), we only make use of it today in OMAP5, so place the
Kconfig entry there. Given that Kconfig lets us provide a default, we
drop CONFIG_DEFAULT_OMAP_RESET_TIME_MAX_USEC entirely. The contents of
doc/README.omap-reset-time make a good help entry, so adjust them
slightly and delete the file. Move the comment about range to where we
use the value now, and have Kconfig enforce the upper bound.
Signed-off-by: Tom Rini <trini@konsulko.com>
Diffstat (limited to 'README')
| -rw-r--r-- | README | 5 |
1 files changed, 0 insertions, 5 deletions
@@ -3708,11 +3708,6 @@ Configuration Settings: If defined, don't allow the -f switch to env set override variable access flags. -- CONFIG_OMAP_PLATFORM_RESET_TIME_MAX_USEC (OMAP only) - This is set by OMAP boards for the max time that reset should - be asserted. See doc/README.omap-reset-time for details on how - the value can be calculated on a given board. - - CONFIG_USE_STDINT If stdint.h is available with your toolchain you can define this option to enable it. You can provide option 'USE_STDINT=1' when |