Hi Sudeep,
On Fri, Nov 24, 2017 at 02:39:47PM +, Sudeep Holla wrote:
[...]
> > Come back to recommended state id, I reviewed Juno board defintion and
> > I found it's not align with PSCI spec defintion, in ARM-TF Juno code
> > defines state as below [1]:
> >
>
> Yes Juno is almost 4 years
On 24/11/17 06:56, Leo Yan wrote:
> Hi Sudeep,
>
> On Thu, Nov 23, 2017 at 02:03:51PM +, Sudeep Holla wrote:
>> Hi Daniel,
>>
>> Thanks a lot for pointing me to this and having some useful discussion
>> in private. That helped to dig a bit further on this.
>>
>> On 23/11/17 05:40, Leo Yan wr
Hi Sudeep,
On Thu, Nov 23, 2017 at 02:03:51PM +, Sudeep Holla wrote:
> Hi Daniel,
>
> Thanks a lot for pointing me to this and having some useful discussion
> in private. That helped to dig a bit further on this.
>
> On 23/11/17 05:40, Leo Yan wrote:
> > Thanks a lot for Vincent Guittot care
Hi Daniel,
Thanks a lot for pointing me to this and having some useful discussion
in private. That helped to dig a bit further on this.
On 23/11/17 05:40, Leo Yan wrote:
> Thanks a lot for Vincent Guittot careful work to find bug for 'CPU_NAP'
> idle state. From ftrace log we can observe CA73 CPU
Thanks a lot for Vincent Guittot careful work to find bug for 'CPU_NAP'
idle state. From ftrace log we can observe CA73 CPUs can be easily waken
up from 'CPU_NAP' state but the 'waken up' CPUs doesn't handle anything
and sleep again; so there have tons of trace events for CA73 CPUs
entering and exi
5 matches
Mail list logo
