diff options
| author | Tom Rini <[email protected]> | 2023-02-08 10:18:26 -0500 |
|---|---|---|
| committer | Tom Rini <[email protected]> | 2023-02-08 10:18:26 -0500 |
| commit | 948d3999bfcdf91ef7a10c3eee9c763ed1323bd2 (patch) | |
| tree | 263ef0c010bd88b7373d72acef7a34e7e20a7ea5 /lib/Kconfig | |
| parent | 94fe4ed9455d559ccca45865c195fe4ecdaffb51 (diff) | |
Revert "lmb: Default to not-LMB_USE_MAX_REGIONS"
As explained by Philippe Schenker, I was misinterpreting what happened
in the case where we do not set LMB_USE_MAX_REGIONS and so had
re-introduced the problem I was attempting to more widely resolve.
This reverts commit 007ae5d108a37564905ea1588cb279f3a522cc3d.
Reported-by: Philippe Schenker <[email protected]>
Signed-off-by: Tom Rini <[email protected]>
Diffstat (limited to 'lib/Kconfig')
| -rw-r--r-- | lib/Kconfig | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/lib/Kconfig b/lib/Kconfig index 59e4304afd1..549bd357785 100644 --- a/lib/Kconfig +++ b/lib/Kconfig @@ -1028,6 +1028,7 @@ config LMB config LMB_USE_MAX_REGIONS bool "Use a common number of memory and reserved regions in lmb lib" depends on LMB + default y help Define the number of supported memory regions in the library logical memory blocks. |