Re: [PATCH AUTOSEL 4.19 123/158] cpufreq: Don't skip frequency validation for has_target() drivers

2019-07-21 Thread Sasha Levin
On Tue, Jul 16, 2019 at 11:21:34AM +0200, Rafael J. Wysocki wrote: On 7/15/2019 4:17 PM, Sasha Levin wrote: From: Viresh Kumar [ Upstream commit 9801522840cc1073f8064b4c979b7b6995c74bca ] CPUFREQ_CONST_LOOPS was introduced in a very old commit from pre-2.6 kernel release by commit 6a4a93f9c0d

Re: [PATCH AUTOSEL 4.19 123/158] cpufreq: Don't skip frequency validation for has_target() drivers

2019-07-16 Thread Rafael J. Wysocki
On 7/15/2019 4:17 PM, Sasha Levin wrote: From: Viresh Kumar [ Upstream commit 9801522840cc1073f8064b4c979b7b6995c74bca ] CPUFREQ_CONST_LOOPS was introduced in a very old commit from pre-2.6 kernel release by commit 6a4a93f9c0d5 ("[CPUFREQ] Fix 'out of sync' issue"). Basically, that commit doe

[PATCH AUTOSEL 4.19 123/158] cpufreq: Don't skip frequency validation for has_target() drivers

2019-07-15 Thread Sasha Levin
From: Viresh Kumar [ Upstream commit 9801522840cc1073f8064b4c979b7b6995c74bca ] CPUFREQ_CONST_LOOPS was introduced in a very old commit from pre-2.6 kernel release by commit 6a4a93f9c0d5 ("[CPUFREQ] Fix 'out of sync' issue"). Basically, that commit does two things: - It adds the frequency ver