On 8 October 2012 13:48, Viresh Kumar wrote:
> This patch tries to optimize vexpress_cpufreq_of_init() routine of vexpress_bl
> cpufreq driver.
>
> Following are the optimizations:
> - No need to allocate freq table array and copy it into struct
> cpufreq_frequency_table. This removes the need o
On Mon, 2012-10-08 at 14:02 +0530, Rajagopal Venkat wrote:
> On 8 October 2012 13:44, MyungJoo Ham wrote:
[]
> > Thank you!
[]
> Thanks for reviewing and testing this patchset.
Both of you quoted all of the original large patch.
That's quite impolite to all the rest of us on this
list.
Please c
From: Jon Medhurst
A subsequent patch will also need to obtain address-cells and
size-cells, so lets factor out this code into a handy function.
Signed-off-by: Jon Medhurst
---
semi_loader.c | 56 ++--
1 file changed, 34 insertions(+), 22 d
This mostly boils down to initialising the Cache Coherent Interconnect
(CCI). We do this by looking in the device-tree for a CCI node, that way
the same semihosting bootwrapper binary can be used on both the
big.LITTLE models and on the A15 models which don't have a CCI.
Changes sinces v1:
- Adde
Hi All,
Sorry for asking one of the most basic question of cpufreq :(
I couldn't get the difference between affected (policy->cpus) and
related cpus (policy->related_cpus) in cpufreq...
As per Documentation/code:
affected_cpus(policy->cpus):
- List of CPUs that require software coordination of
From: Jon Medhurst
Check all the CPU affinity fields of MPIDR, so we select only
the first CPU of the first cluster as the one to boot on.
Signed-off-by: Jon Medhurst
---
boot.S |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/boot.S b/boot.S
index 727119a..40ebd33 100644
From: Jon Medhurst
The A15xA7 models simulate a Cache Coherent Interconnect (CCI) and this
needs to be initialised correctly for Linux to boot.
To perform this initiation we add the new function configure_from_fdt()
which will look in the fdt for devices to initialise. In this first case
we look
Hi Everyone,
The switch over happened at 8:00 AM UTC, and all seems to be ok, except that
DNS changes don't seem to have universally filtered through as yet. As a
consequence I can't put a board online to test just yet, because health checks
push their results to v.l.o.
All other services are
> On 8 October 2012 03:31, Rafael J. Wysocki wrote:
> > On Thursday 04 of October 2012 14:58:33 Rajagopal Venkat wrote:
> >> Add devfreq suspend/resume apis for devfreq users. This patch
> >> supports suspend and resume of devfreq load monitoring, required
> >> for devices which can idle.
> >>
> >
Hi Tushar,
On 10/08/2012 08:04 AM, Tushar Behera wrote:
On 10/06/2012 02:37 AM, Andrey Konovalov wrote:
Greetings,
Minor change to the plan:
* The current llct is *llct-20121006.0*
* October 9: ll rebuild based on llct-20121006.0
* October 16: ll rebuild based on llct-20121012., ll code
On 8 October 2012 03:31, Rafael J. Wysocki wrote:
> On Thursday 04 of October 2012 14:58:33 Rajagopal Venkat wrote:
>> Add devfreq suspend/resume apis for devfreq users. This patch
>> supports suspend and resume of devfreq load monitoring, required
>> for devices which can idle.
>>
>> Signed-off-b
On 8 October 2012 13:44, MyungJoo Ham wrote:
>> Prepare devfreq core framework to support devices which
>> can idle. When device idleness is detected perhaps through
>> runtime-pm, need some mechanism to suspend devfreq load
>> monitoring and resume back when device is online. Present
>> code cont
This patch tries to optimize vexpress_cpufreq_of_init() routine of vexpress_bl
cpufreq driver.
Following are the optimizations:
- No need to allocate freq table array and copy it into struct
cpufreq_frequency_table. This removes the need of
_cpufreq_copy_table_from_array() routine too.
- Use g
> Prepare devfreq core framework to support devices which
> can idle. When device idleness is detected perhaps through
> runtime-pm, need some mechanism to suspend devfreq load
> monitoring and resume back when device is online. Present
> code continues monitoring unless device is removed from
> de
14 matches
Mail list logo