* Keerthy [160622 02:13]:
> Can you pull this patch as well?
OK thanks applying into omap-for-v4.8/soc.
Tony
Tony,
On Tuesday 21 June 2016 03:27 PM, Keerthy wrote:
On Tuesday 21 June 2016 01:22 PM, Mohammed, Afzal wrote:
Hi Suman,
Anna, Suman wrote on Monday, June 20, 2016 9:49 PM:
It does happen when the pruss module is exercised. We found this when we
tried to do a standby test on suspend, and
On Tuesday 21 June 2016 01:22 PM, Mohammed, Afzal wrote:
Hi Suman,
Anna, Suman wrote on Monday, June 20, 2016 9:49 PM:
It does happen when the pruss module is exercised. We found this when we
tried to do a standby test on suspend, and while it worked on AM33xx,
AM437x failed because of this
Hi Suman,
Anna, Suman wrote on Monday, June 20, 2016 9:49 PM:
> It does happen when the pruss module is exercised. We found this when we
> tried to do a standby test on suspend, and while it worked on AM33xx,
> AM437x failed because of this difference.
Okay, seems on am335x, PER doesn't have RST
Hi Afzal,
On 06/20/2016 03:23 AM, Keerthy wrote:
>
>
> On Monday 20 June 2016 12:35 PM, Mohammed, Afzal wrote:
>> Hi,
>>
>> J, KEERTHY wrote on Monday, June 20, 2016 9:22 AM:
>>
>>> pruss hwmod RSTST register wrongly points to PWRSTCTRL register in
>>> case of
>>> am43xx. Fix the RSTST register
On Monday 20 June 2016 12:35 PM, Mohammed, Afzal wrote:
Hi,
J, KEERTHY wrote on Monday, June 20, 2016 9:22 AM:
pruss hwmod RSTST register wrongly points to PWRSTCTRL register in case of
am43xx. Fix the RSTST register offset value.
This can lead to setting of wrong power state values for P
Hi,
J, KEERTHY wrote on Monday, June 20, 2016 9:22 AM:
> pruss hwmod RSTST register wrongly points to PWRSTCTRL register in case of
> am43xx. Fix the RSTST register offset value.
> This can lead to setting of wrong power state values for PER domain.
Just curious, does it happen or noticed by go
7 matches
Mail list logo
