From: Viresh Kumar <viresh.kumar@linaro.org>
To: Gregory CLEMENT <gregory.clement@bootlin.com>
Cc: Vincent Guittot <vincent.guittot@linaro.org>,
linux-pm@vger.kernel.org,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
rjw@rjwysocki.net,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [BUG] cpufreq/armada-37xx: Parent clock issues after boot
Date: Fri, 22 Feb 2019 09:02:01 +0530 [thread overview]
Message-ID: <20190222033201.qdod733xtnwptxev@vireshk-i7> (raw)
In-Reply-To: <87imychbci.fsf@FE-laptop>
On 25-01-19, 18:54, Gregory CLEMENT wrote:
> Well the idea was to modify the DVFS register before we enable
> DVFS. Indeed modifying the parent clock of a CPU while we use it could
> be a little tricky.
>
> I have some ideas to fix this issue: I won't use anymore
> get_parent/set_parent in the cpufreq driver and I will set the DVFS
> parent clock during the initialization at the clock driver level. I need
> to do some tests to be sure of the implementation and once it was done I
> will CC you with the patch for the fix.
Hi Gregory,
I was wondering if you had any updates on this as it has been almost a
month since you shared an update.
--
viresh
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-02-22 3:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-24 10:30 [BUG] cpufreq/armada-37xx: Parent clock issues after boot Viresh Kumar
2019-01-24 10:39 ` Gregory CLEMENT
2019-01-25 17:54 ` Gregory CLEMENT
2019-02-22 3:32 ` Viresh Kumar [this message]
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=20190222033201.qdod733xtnwptxev@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=gregory.clement@bootlin.com \
--cc=ilias.apalodimas@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=thomas.petazzoni@bootlin.com \
--cc=vincent.guittot@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