On Fri, 28 Oct 2022 at 18:30, Tom Rini trini@konsulko.com wrote:
This converts the following to Kconfig: CONFIG_SYS_NONCACHED_MEMORY
To do this we introduce CONFIG_SYS_HAS_NONCACHED_MEMORY as a bool to gate if we are going to have noncached_... functions available and then continue to use CONFIG_SYS_NONCACHED_MEMORY to store the size of said cache. We make this new option depend on both the architectures which implement support and the drivers which make use of it.
Cc: Tom Warren twarren@nvidia.com Cc: Mingming lee mingming.lee@mediatek.com Cc: "Ying-Chun Liu (PaulLiu)" paul.liu@linaro.org Cc: Alban Bedel alban.bedel@avionic-design.de Cc: Stephen Warren swarren@nvidia.com Cc: Marcel Ziswiler marcel.ziswiler@toradex.com Cc: Allen Martin amartin@nvidia.com Signed-off-by: Tom Rini trini@konsulko.com
I'm cc'ing a bunch of board maintainers here because restricting the noncached support to these drivers results in the noncached framework not being used, but also doesn't change anything else about the binary. Is there some other use case here I'm missing?
README | 19 ----------------- arch/Kconfig | 24 ++++++++++++++++++++++
Reviewed-by: Simon Glass sjg@chromium.org