From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gregory CLEMENT Subject: [PATCH 0/2] Fix various issue on CPU freq for Armada 37xx Date: Fri, 8 Mar 2019 17:47:08 +0100 Message-ID: <20190308164710.10597-1-gregory.clement@bootlin.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: "Rafael J. Wysocki" , Viresh Kumar , linux-pm@vger.kernel.org Cc: Andrew Lunn , Vincent Guittot , Jason Cooper , Christian Neubert , Antoine Tenart , Gregory CLEMENT , Ilias Apalodimas , Maxime Chevallier , Thomas Petazzoni , =?UTF-8?q?Miqu=C3=A8l=20Raynal?= , linux-arm-kernel@lists.infradead.org, Sebastian Hesselbarth List-Id: linux-pm@vger.kernel.org Hello, A few weeks ago an issue was reported on the cpufreq driver, in the meantime Christian Neubert got the same issue on a ambian kernel and proposed a patch to fix it. His fix seemed to address the issue seen, and I only added more context about what was done. Christian also reported an other issue about the way the frequency was calculated. This issue is visible only when the default frequency was low (600MHz). Based on this I proposed to no more use the CPU frequency as base for the calculation but on the parent clock frequency Gregory Christian Neubert (1): cpufreq: armada-37xx: fix clock parenting Gregory CLEMENT (1): cpufreq: armada-37xx: fix frequency calculation for opp drivers/cpufreq/armada-37xx-cpufreq.c | 42 +++++++++++++++++++++++---- 1 file changed, 36 insertions(+), 6 deletions(-) -- 2.20.1