[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5303C018.1020707@wwwdotorg.org>
Date: Tue, 18 Feb 2014 13:18:32 -0700
From: Stephen Warren <swarren@...dotorg.org>
To: Viresh Kumar <viresh.kumar@...aro.org>
CC: "Rafael J. Wysocki" <rjw@...ysocki.net>,
Lists linaro-kernel <linaro-kernel@...ts.linaro.org>,
"cpufreq@...r.kernel.org" <cpufreq@...r.kernel.org>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Nishanth Menon <nm@...com>, Kgene Kim <kgene.kim@...sung.com>,
jinchoi@...adcom.com, Lan Tianyu <tianyu.lan@...el.com>,
Sebastian Capella <sebastian.capella@...aro.org>,
Jonghwan Choi <jhbird.choi@...sung.com>
Subject: Re: [PATCH V5 0/7] cpufreq: suspend early/resume late: dpm_{suspend|resume}()
On 02/17/2014 02:20 AM, Viresh Kumar wrote:
> On 15 February 2014 05:33, Stephen Warren <swarren@...dotorg.org> wrote:
>> On 02/14/2014 03:23 PM, Rafael J. Wysocki wrote:
>
>>> Well, it would be good to verify which part, then.
>>
>> Patch 2/7 appears to stop that message from being printed during
>> suspend, and perhaps reduce the number of times it's printed during
>> resume. Patch 7/7 stops the message being printed at all.
>>
>> Looking at patch 7, I wonder if it's simply because tegra_target() was
>> modified never to return -EBUSY, so the bug is still there, but it's
>> just been hidden.
>
> No, the bug is removed now. Its hidden in current linus/master :)
I'm not sure what that means; I still see the message:
cpufreq: __cpufreq_driver_target: Failed to change cpu frequency: -16
... in Linus's tree (805937cf45f9 "Merge tag 'ext4_for_linus_stable' of
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4").
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists