Quoting Stephen Boyd (2020-04-08 23:44:13) > Enable build testing and configuration control of the common clk > framework so that more code coverage and testing can be done on the > common clk framework across various architectures. This also nicely > removes the requirement that architectures must select the framework > when they don't use it in architecture code. > > There's one snag with doing this, and that's making sure that randconfig > builds don't select this option when some architecture or platform > implements 'struct clk' outside of the common clk framework. Introduce a > new config option 'HAVE_LEGACY_CLK' to indicate those platforms that > haven't migrated to the common clk framework and therefore shouldn't be > allowed to select this new config option. Also add a note that we hope > one day to remove this config entirely. > > Based on a patch by Mark Brown <[email protected]>. > > Cc: Mark Brown <[email protected]> > Cc: Geert Uytterhoeven <[email protected]> > Cc: Mark Salter <[email protected]> > Cc: Aurelien Jacquiot <[email protected]> > Cc: Jiaxun Yang <[email protected]> > Cc: Guan Xuetao <[email protected]> > Cc: Russell King <[email protected]> > Cc: Arnd Bergmann <[email protected]> > Cc: Yoshinori Sato <[email protected]> > Cc: Rich Felker <[email protected]> > Cc: Thomas Bogendoerfer <[email protected]> > Cc: <[email protected]> > Cc: <[email protected]> > Cc: <[email protected]> > Cc: <[email protected]> > Cc: <[email protected]> > Link: > https://lore.kernel.org/r/[email protected] > Signed-off-by: Stephen Boyd <[email protected]> > ---
Applied to clk-next
