From: Meelis Roos <mroos@linux.ee>
To: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
Cc: rjw@rjwysocki.net, viresh.kumar@linaro.org,
cpufreq@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] Cpufreq frequency serialization fixes
Date: Fri, 25 Apr 2014 20:29:04 +0300 (EEST) [thread overview]
Message-ID: <alpine.SOC.1.00.1404252028410.11626@math.ut.ee> (raw)
In-Reply-To: <20140425081728.10258.63980.stgit@srivatsabhat.in.ibm.com>
> Meelis Roos reported hangs during boot in the longhaul cpufreq driver, after
> commit 12478cf0c55 (cpufreq: Make sure frequency transitions are serialized).
> The root-cause of this issue is the extra invocation of the
> cpufreq_freq_transition_begin() and cpufreq_freq_transition_end() APIs in the
> longhaul driver. I found similar issues in the powernow-k6 and powernow-k7
> drivers as well. This patchset fixes the issue in all the 3 drivers.
>
> Srivatsa S. Bhat (3):
> cpufreq, powernow-k7: Fix double invocation of cpufreq_freq_transition_begin/end
> cpufreq, powernow-k6: Fix double invocation of cpufreq_freq_transition_begin/end
> cpufreq, longhaul: Fix double invocation of cpufreq_freq_transition_begin/end
This set fixes it for me on VIA EPIA with longhaul.
--
Meelis Roos (mroos@linux.ee)
next prev parent reply other threads:[~2014-04-25 17:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-25 8:17 Srivatsa S. Bhat
2014-04-25 8:18 ` [PATCH 1/3] cpufreq, longhaul: Fix double invocation of cpufreq_freq_transition_begin/end Srivatsa S. Bhat
2014-04-25 8:37 ` Viresh Kumar
2014-04-25 8:39 ` Srivatsa S. Bhat
2014-04-25 8:18 ` [PATCH 2/3] cpufreq, powernow-k6: " Srivatsa S. Bhat
2014-04-25 8:28 ` Viresh Kumar
2014-04-25 8:42 ` Srivatsa S. Bhat
2014-04-25 8:18 ` [PATCH 3/3] cpufreq, powernow-k7: " Srivatsa S. Bhat
2014-04-25 8:24 ` Viresh Kumar
2014-04-25 17:29 ` Meelis Roos [this message]
2014-04-28 18:47 ` [PATCH 0/3] Cpufreq frequency serialization fixes Srivatsa S. Bhat
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=alpine.SOC.1.00.1404252028410.11626@math.ut.ee \
--to=mroos@linux.ee \
--cc=cpufreq@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=srivatsa.bhat@linux.vnet.ibm.com \
--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
all inboxes | Powered by JetHome®