[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220504082249.anrvkf2ssbxyzz5m@vireshk-i7>
Date: Wed, 4 May 2022 13:52:49 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Rex-BC Chen <rex-bc.chen@...iatek.com>
Cc: rafael@...nel.org, robh+dt@...nel.org, krzk+dt@...nel.org,
matthias.bgg@...il.com, jia-wei.chang@...iatek.com,
roger.lu@...iatek.com, hsinyi@...gle.com, khilman@...libre.com,
angelogioacchino.delregno@...labora.com, linux-pm@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org,
Project_Global_Chrome_Upstream_Group@...iatek.com
Subject: Re: [PATCH V4 07/14] cpufreq: mediatek: Add .get function
On 03-05-22, 19:33, Rex-BC Chen wrote:
> Our observation tells us cpufreq_online is setting only once at boot
> for one cpu cluster.
> But we can see the problem repeatly occurs once cpufreq_get is invoked.
>
> e.g.
> [ 71.154560] cpufreq: Warning: CPU frequency out of sync: cpufreq and
> timing core thinks of 500000, is 499999 kHz
> [ 71.155880] cpufreq: notification 0 of frequency transition to 499999
> kHz
> [ 71.156777] cpufreq: notification 1 of frequency transition to 499999
> kHz
> [ 71.187241] cpufreq: target for CPU 0: 500000 kHz, relation 0,
> requested 500000 kHz
> [ 71.188246] cpufreq: target_freq/policy->cur: 500000/499999 kHz
Lemme know if this helps:
https://lore.kernel.org/lkml/39e39a7d30c8ee6af81fb64670a330abeb87402e.1651652493.git.viresh.kumar@linaro.org/
--
viresh
Powered by blists - more mailing lists