On 23-10-19, 10:06, Sudeep Holla wrote:
> I agree, we shouldn't. But this is in IKS which is built in the merged
> table by the driver. We can fix that, but found this easier and simple.
> And since it was allowed when the driver was merged, just thought of
> checking the details with you.
That wa
On Wed, Oct 23, 2019 at 08:56:08AM +0530, Viresh Kumar wrote:
> On 22-10-19, 18:32, Sudeep Holla wrote:
> > Currently if we encounter duplicate frequency table entries, we abort
> > the validation and return error immediately. Instead of failing, we
> > can mark the entry as invalid and continue to
On 22-10-19, 18:32, Sudeep Holla wrote:
> Currently if we encounter duplicate frequency table entries, we abort
> the validation and return error immediately. Instead of failing, we
> can mark the entry as invalid and continue to function normal.
>
> Cc: "Rafael J. Wysocki"
> Cc: Viresh Kumar
>
Currently if we encounter duplicate frequency table entries, we abort
the validation and return error immediately. Instead of failing, we
can mark the entry as invalid and continue to function normal.
Cc: "Rafael J. Wysocki"
Cc: Viresh Kumar
Signed-off-by: Sudeep Holla
---
drivers/cpufreq/freq
4 matches
Mail list logo