On Thu, 2014-11-13 at 02:47 +0100, Rafael J. Wysocki wrote:
On Wednesday, November 12, 2014 09:40:43 AM Viresh Kumar wrote:
CPUFreq driver's Kconfig entries are added in Kconfig.<arch> files and they are all included from the main Kconfig file using a menu entry. This creates another level of (unnecessary) hierarchy within the menuconfig entries.
The problem occurs when there are drivers usable across architectures. Either their config entry is duplicated in all the supported architectures or is put into the main Kconfig entry. With the later one, we have menuconfig entries for drivers at two levels then.
Fix these issues by getting rid of another level of menuconfig entries and populate all drivers within the main cpufreq menu.
Won't this be confusing?
Why would it be confusing? It's already in a not-too-large "CPU Frequency scaling" menu, the names of the individual options should be clear enough, and they'd all be grouped at the end of the menu.
FWIW, there's already "Generic DT based cpufreq driver" under that menu.
Can we at least have a "CPU frequency scaling drivers" menu for drivers the *contents* of which will depend on the architecture?
That works too -- I just don't see the confusion aspect.
-Scott