Re: [PATCH v2] selftests: create cpufreq kconfig fragments

[Naresh Kamboju]

+ Mailing list

On 22 March 2017 at 09:44, Viresh Kumar <viresh.kumar@xxxxxxxxxx> wrote:
> On 21-03-17, 21:06, naresh.kamboju@xxxxxxxxxx wrote:
>> From: Naresh Kamboju <naresh.kamboju@xxxxxxxxxx>
>>
>> For the better test coverage of cpufreq driver code these extra configurations
>> are needed. Enable cpufreq governors and stats.
>>
>> Signed-off-by: Naresh Kamboju <naresh.kamboju@xxxxxxxxxx>
>> ---
>>  tools/testing/selftests/cpufreq/config | 15 +++++++++++++++
>>  1 file changed, 15 insertions(+)
>>  create mode 100644 tools/testing/selftests/cpufreq/config
>>
>> diff --git a/tools/testing/selftests/cpufreq/config b/tools/testing/selftests/cpufreq/config
>> new file mode 100644
>> index 000000000000..27ff72ebd0f5
>> --- /dev/null
>> +++ b/tools/testing/selftests/cpufreq/config
>> @@ -0,0 +1,15 @@
>> +CONFIG_CPU_FREQ=y
>> +CONFIG_CPU_FREQ_STAT=y
>> +CONFIG_CPU_FREQ_GOV_POWERSAVE=y
>> +CONFIG_CPU_FREQ_GOV_USERSPACE=y
>> +CONFIG_CPU_FREQ_GOV_ONDEMAND=y
>> +CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y
>> +CONFIG_CPU_FREQ_GOV_SCHEDUTIL=y
>> +CONFIG_DEBUG_RT_MUTEXES=y
>> +CONFIG_DEBUG_PI_LIST=y
>> +CONFIG_DEBUG_SPINLOCK=y
>> +CONFIG_DEBUG_MUTEXES=y
>> +CONFIG_DEBUG_LOCK_ALLOC=y
>> +CONFIG_PROVE_LOCKING=y
>> +CONFIG_LOCKDEP=y
>> +CONFIG_DEBUG_ATOMIC_SLEEP=y
>
> Acked-by: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
>
> --
> viresh