[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAKohpoks+XA0bb33D53ZRxJaHzNk66++tBOrVhzMEhaM=7sbWA@mail.gmail.com>
Date: Fri, 8 Feb 2013 08:15:17 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Valdis.Kletnieks@...edu
Cc: "Rafael J. Wysocki" <rjw@...k.pl>, linux-kernel@...r.kernel.org,
cpufreq@...r.kernel.org, linux-pm@...r.kernel.org
Subject: Re: next-20130206 cpufreq - WARN in sysfs_add_one
On 8 February 2013 00:48, <Valdis.Kletnieks@...edu> wrote:
> On Thu, 07 Feb 2013 13:11:52 +0530, Viresh Kumar said:
>
>> First of all i want to confirm something about your system. I am sure it is a
>> multi-policy system (or multi cluster system). i.e. there are more than one
>> clock line for different cpus ? And so multiple struct policy exist
>> simultaneously.
>
> Hmm.. it's a bog-standard Dell Latitude E6500 laptop, with a single
> Core2 Duo P8700 CPU (one die, 2 cores, no HT). It's apparently able
> to clock both cores at different speeds (one core running busy at 2540mhz
> and the other idling at 800mhz), if that's what you mean by multiple
> clock lines.
Perfect!! So, when the cpus can manage different freqs, we have multiple
struct policies for them per cpu.
> In any case, next-20130206 complained, and with this patch added I see
> nothing in dmesg and cpufreq is acting properly on both cores, so:
>
> Tested-By: Valdis Kletnieks <valdis.kletnieks@...edu>
Thanks.
> (btw - I had to hand-apply your patch, as it showed up white-space
> damaged. Three lines wrapped, and tabs converted to spaces).
I know that and feeling bad for you :(
I gave you this because of my mails issue :)
http://git.linaro.org/gitweb?p=people/vireshk/linux.git;a=shortlog;h=refs/heads/for-valdis
--
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