On Fri, Mar 14, 2014 at 05:10:34PM +, Rob Herring wrote:
> On Fri, Mar 14, 2014 at 5:23 AM, Mark Rutland wrote:
> > On Fri, Mar 14, 2014 at 06:53:53AM +, Pranavkumar Sawargaonkar wrote:
> >> Hi Christoffer,
> >>
> >> On 14 March 2014 09:19, Christoffer Dall
> >> wrote:
> >> > On Thu, Feb
On Fri, Mar 14, 2014 at 5:23 AM, Mark Rutland wrote:
> On Fri, Mar 14, 2014 at 06:53:53AM +, Pranavkumar Sawargaonkar wrote:
>> Hi Christoffer,
>>
>> On 14 March 2014 09:19, Christoffer Dall wrote:
>> > On Thu, Feb 27, 2014 at 12:21:07PM +0530, Pranavkumar Sawargaonkar wrote:
>> >> If we have
On Fri, Mar 14, 2014 at 06:53:53AM +, Pranavkumar Sawargaonkar wrote:
> Hi Christoffer,
>
> On 14 March 2014 09:19, Christoffer Dall wrote:
> > On Thu, Feb 27, 2014 at 12:21:07PM +0530, Pranavkumar Sawargaonkar wrote:
> >> If we have in-kernel emulation of PSCI v0.2 for KVM ARM/ARM64 then
> >
Hi Christoffer,
On 14 March 2014 09:19, Christoffer Dall wrote:
> On Thu, Feb 27, 2014 at 12:21:07PM +0530, Pranavkumar Sawargaonkar wrote:
>> If we have in-kernel emulation of PSCI v0.2 for KVM ARM/ARM64 then
>> we enable PSCI v0.2 for each VCPU at the time of VCPU init hence we
>> need to provi
On 27 February 2014 12:21, Pranavkumar Sawargaonkar
wrote:
> If we have in-kernel emulation of PSCI v0.2 for KVM ARM/ARM64 then
> we enable PSCI v0.2 for each VCPU at the time of VCPU init hence we
> need to provide PSCI v0.2 function IDs via generated DTB.
>
> This patch updates generated DTB to
