Re: [PATCH V3 3/9] cpufreq: Cap the default transition delay value to 10 ms

From	Viresh Kumar <viresh.kumar@linaro.org>
Newsgroups	linux.kernel
Subject	Re: [PATCH V3 3/9] cpufreq: Cap the default transition delay value to 10 ms
Date	2017-08-16 08:40 +0200
Message-ID	<uf09I-3AX-9@gated-at.bofh.it> (permalink)
References	(1 earlier) <u4Ufi-79T-71@gated-at.bofh.it> <u7in8-1wt-9@gated-at.bofh.it> <u7nGa-537-9@gated-at.bofh.it> <u860x-7Vv-3@gated-at.bofh.it> <u860x-7Vv-1@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On 28-07-17, 10:58, Viresh Kumar wrote:
> At this point I really feel that this is a hardware specific problem
> and it was working by chance until now. And I am not sure if we
> shouldn't be stopping this patch from getting merged just because of
> that.
> 
> At least you can teach your distribution to go increase the sampling
> rate from userspace to make it all work.

Its been 3 weeks since my last email on this thread and no reply yet
from any of the IMX maintainers. Can someone please help here ?

@Shawn: Can you help debugging a bit here, to see what's get screwed
up due to this commit ? Its just that your platform isn't able to
change freq at 10 ms rate.

@Rafael: I am not sure, but should we be stopping this patch because
some hardware isn't able to change freq at 10ms interval and is just
faking the transition delay to start with ?

Maybe we get this merged again and the IMX guys can figure out what's
wrong on their platform and how to fix it ?

-- 
viresh

Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Re: [PATCH V3 3/9] cpufreq: Cap the default transition delay value  to 10 ms Viresh Kumar <viresh.kumar@linaro.org> - 2017-08-16 08:40 +0200
  Re: [PATCH V3 3/9] cpufreq: Cap the default transition delay value  to 10 ms Viresh Kumar <viresh.kumar@linaro.org> - 2017-08-17 05:40 +0200

csiph-web