Hi Tomasz,
On 18 April 2014 19:42, Tomasz Figa wrote:
> Hi Chander,
>
>
> On 15.04.2014 09:38, Chander Kashyap wrote:
>>
>> Currently status/configuration power register values are hard-coded for
>> cpu1.
>>
>> Make it generic so that it is useful for SoC's with more than two cpus.
>>
>> Signed-o
Hi Chander,
On 15.04.2014 09:38, Chander Kashyap wrote:
Currently status/configuration power register values are hard-coded for cpu1.
Make it generic so that it is useful for SoC's with more than two cpus.
Signed-off-by: Chander Kashyap
---
changes in v3:
1. Move cpunr calculation to
Currently status/configuration power register values are hard-coded for cpu1.
Make it generic so that it is useful for SoC's with more than two cpus.
Signed-off-by: Chander Kashyap
---
changes in v3:
1. Move cpunr calculation to a macro
2. Changed printk format specifier from uns
Hi Tomasz,
Thanks for the review comments,
On 14 April 2014 22:58, Tomasz Figa wrote:
> Hi Chander,
>
> Few more comments inline.
>
>
> On 09.04.2014 13:09, Chander Kashyap wrote:
>>
>> Currently status/configuration power register values are hard-coded for
>> cpu1.
>>
>> Make it generic so that
Hi Chander,
Few more comments inline.
On 09.04.2014 13:09, Chander Kashyap wrote:
Currently status/configuration power register values are hard-coded for cpu1.
Make it generic so that it is useful for SoC's with more than two cpus.
Signed-off-by: Chander Kashyap
---
changes in v2 : Used exis
On 14.04.2014 06:27, Chander Kashyap wrote:
Hi,
On 10 April 2014 11:18, Chander Kashyap wrote:
Hi Tomasz,
On 9 April 2014 20:15, Tomasz Figa wrote:
On 09.04.2014 15:49, Chander Kashyap wrote:
Hi Tomasz,
On 9 April 2014 17:19, Tomasz Figa wrote:
Hi Chander,
On 09.04.2014 13:09, Chand
Hi,
On 10 April 2014 11:18, Chander Kashyap wrote:
> Hi Tomasz,
>
> On 9 April 2014 20:15, Tomasz Figa wrote:
>> On 09.04.2014 15:49, Chander Kashyap wrote:
>>>
>>> Hi Tomasz,
>>>
>>> On 9 April 2014 17:19, Tomasz Figa wrote:
Hi Chander,
On 09.04.2014 13:09, Chander Kas
Hi Tomasz,
On 9 April 2014 20:15, Tomasz Figa wrote:
> On 09.04.2014 15:49, Chander Kashyap wrote:
>>
>> Hi Tomasz,
>>
>> On 9 April 2014 17:19, Tomasz Figa wrote:
>>>
>>> Hi Chander,
>>>
>>>
>>> On 09.04.2014 13:09, Chander Kashyap wrote:
Currently status/configuration power regi
On 09.04.2014 15:49, Chander Kashyap wrote:
Hi Tomasz,
On 9 April 2014 17:19, Tomasz Figa wrote:
Hi Chander,
On 09.04.2014 13:09, Chander Kashyap wrote:
Currently status/configuration power register values are hard-coded for
cpu1.
Make it generic so that it is useful for SoC's with more t
Hi Tomasz,
On 9 April 2014 17:19, Tomasz Figa wrote:
> Hi Chander,
>
>
> On 09.04.2014 13:09, Chander Kashyap wrote:
>>
>> Currently status/configuration power register values are hard-coded for
>> cpu1.
>>
>> Make it generic so that it is useful for SoC's with more than two cpus.
>>
>> Signed-of
Hi Chander,
On 09.04.2014 13:09, Chander Kashyap wrote:
Currently status/configuration power register values are hard-coded for cpu1.
Make it generic so that it is useful for SoC's with more than two cpus.
Signed-off-by: Chander Kashyap
---
changes in v2 : Used existing macros for clusterid a
Currently status/configuration power register values are hard-coded for cpu1.
Make it generic so that it is useful for SoC's with more than two cpus.
Signed-off-by: Chander Kashyap
---
changes in v2 : Used existing macros for clusterid and cpuid calculation
arch/arm/mach-exynos/hotplug.c |
Currently status/configuration power register values are hard-coded for cpu1.
Make it generic so that it is useful for SoC's with more than two cpus.
Signed-off-by: Chander Kashyap
---
arch/arm/mach-exynos/hotplug.c | 10 +++---
arch/arm/mach-exynos/platsmp.c | 13 -
arch/
13 matches
Mail list logo
