linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	linux-pm@vger.kernel.org
Cc: "Andrew Lunn" <andrew@lunn.ch>,
	"Vincent Guittot" <vincent.guittot@linaro.org>,
	"Jason Cooper" <jason@lakedaemon.net>,
	"Christian Neubert" <christian.neubert.86@gmail.com>,
	"Antoine Tenart" <antoine.tenart@bootlin.com>,
	"Gregory CLEMENT" <gregory.clement@bootlin.com>,
	"Ilias Apalodimas" <ilias.apalodimas@linaro.org>,
	"Maxime Chevallier" <maxime.chevallier@bootlin.com>,
	"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
	"Miquèl Raynal" <miquel.raynal@bootlin.com>,
	linux-arm-kernel@lists.infradead.org,
	"Sebastian Hesselbarth" <sebastian.hesselbarth@gmail.com>
Subject: [PATCH 0/2] Fix various issue on CPU freq for Armada 37xx
Date: Fri,  8 Mar 2019 17:47:08 +0100	[thread overview]
Message-ID: <20190308164710.10597-1-gregory.clement@bootlin.com> (raw)

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


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2019-03-08 16:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-08 16:47 Gregory CLEMENT [this message]
2019-03-08 16:47 ` [PATCH 1/2] cpufreq: armada-37xx: fix clock parenting Gregory CLEMENT
2019-03-11  5:31   ` Viresh Kumar
2019-03-13 16:39     ` Gregory CLEMENT
2019-03-14 12:13   ` Ilias Apalodimas
2019-03-08 16:47 ` [PATCH 2/2] cpufreq: armada-37xx: fix frequency calculation for opp Gregory CLEMENT
2019-03-11  5:33   ` Viresh Kumar
2019-04-29  9:53   ` Viresh Kumar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190308164710.10597-1-gregory.clement@bootlin.com \
    --to=gregory.clement@bootlin.com \
    --cc=andrew@lunn.ch \
    --cc=antoine.tenart@bootlin.com \
    --cc=christian.neubert.86@gmail.com \
    --cc=ilias.apalodimas@linaro.org \
    --cc=jason@lakedaemon.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=maxime.chevallier@bootlin.com \
    --cc=miquel.raynal@bootlin.com \
    --cc=rjw@rjwysocki.net \
    --cc=sebastian.hesselbarth@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=vincent.guittot@linaro.org \
    --cc=viresh.kumar@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).