On Fri, 28 Oct 2022 at 18:30, Tom Rini <tr...@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 <twar...@nvidia.com> > Cc: Mingming lee <mingming....@mediatek.com> > Cc: "Ying-Chun Liu (PaulLiu)" <paul....@linaro.org> > Cc: Alban Bedel <alban.be...@avionic-design.de> > Cc: Stephen Warren <swar...@nvidia.com> > Cc: Marcel Ziswiler <marcel.ziswi...@toradex.com> > Cc: Allen Martin <amar...@nvidia.com> > Signed-off-by: Tom Rini <tr...@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 <s...@chromium.org>
