On Thu, Jan 10, 2013 at 1:32 PM, Daniel Lezcano wrote:
> On 01/10/2013 09:07 PM, amit daniel kachhap wrote:
>> Hi Daniel,
>
> Hi Amit Daniel,
>
>> This hotplug noifiers looks fine. I suppose it should add extra state
>> C1 in cpu0. If it is done like below than for normal cases(when all
>> cpu's a
On 01/10/2013 09:07 PM, amit daniel kachhap wrote:
> Hi Daniel,
Hi Amit Daniel,
> This hotplug noifiers looks fine. I suppose it should add extra state
> C1 in cpu0. If it is done like below than for normal cases(when all
> cpu's are online) there wont be any statistics for C0 state
I guess you
Hi Daniel,
This hotplug noifiers looks fine. I suppose it should add extra state
C1 in cpu0. If it is done like below than for normal cases(when all
cpu's are online) there wont be any statistics for C0 state also which
is required. Other patches look good.
Thanks,
Amit
On Fri, Jan 4, 2013 at 8:
On Thu, 2013-01-10 at 12:10 +, Punit Agrawal wrote:
> This patch fixes incorrect range check for the number of PMU counters. This
> caused the number of counters to be off-by-1.
>
> Signed-off-by: Punit Agrawal
> ---
> Hi Tixy,
>
> I discovered an embarassing range check issue in the CCI dri
On 10/01/13 12:14, Jon Medhurst (Tixy) wrote:
[...]
I had to fix the line which gets the script called at boot:
-service setirqaffinity /set_irq_affinity 0xc07
+service setirqaffinity /set_irq_affinity.sh 0xc07
Thanks for fixing this. I was debating different names and looks like
submitted th
On Wed, 2013-01-09 at 16:04 +, Punit Agrawal wrote:
> >>
> >> I am not quite sure where to send this patch to get it included in Linaro.
> >> But
> >> you seem to have a few patches in this repo, so maybe you can apply this
> >> one.
> >
> > Yes, I can do that. It looks like it copes OK for d
This patch fixes incorrect range check for the number of PMU counters. This
caused the number of counters to be off-by-1.
Signed-off-by: Punit Agrawal
---
Hi Tixy,
I discovered an embarassing range check issue in the CCI driver. It would allow
only 3 of the 4 CCI PMU counters to be used. This pa
Hello
As some of you know I created a team of ARM Chromebook hackers on
Launchpad. We concentrate on getting misc things working on those devices.
One is Mali T604 OpenGLES driver. It works but there are some bugs in
it. The problem is: where to report them? As Chromium OS bugtracker is
not prope
On 9 January 2013 16:50, Viresh Kumar wrote:
> diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
> +static void update_policy_cpu(struct cpufreq_policy *policy, unsigned int
> cpu)
> +{
> + cpufreq_frequency_table_update_policy_cpu(old_cpu, cpu);
> + cpufreq_stats_up
On 10 January 2013 16:05, Viresh Kumar wrote:
> Another thing, can i have a tested-by from you for both my patches ? remove
> and
> add dev?
>
For both:
Tested-by: Shawn Guo
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.
On 10 January 2013 13:24, Shawn Guo wrote:
> On Wed, Jan 09, 2013 at 04:50:44PM +0530, Viresh Kumar wrote:
>> @Shawn: I believe your driver don't require that ugly code anymore (Though i
>> know there is a situation for that to happen, if we have two cpus, you remove
>> second one and then add it
On 10 January 2013 13:24, Shawn Guo wrote:
> Yes, just played it and it works for me. However, I would have to keep
> that little ugly code in my patch to save the dependency on your patch.
> Will send a follow-up to clean that up once your patch hits mainline.
Good. Hopefully, patches from both
12 matches
Mail list logo
