From: Keerthy <a0393675@ti.com>
To: "Mohammed, Afzal" <afzal@ti.com>, "Anna, Suman" <s-anna@ti.com>,
"J, KEERTHY" <j-keerthy@ti.com>,
"tony@atomide.com" <tony@atomide.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Kristo, Tero" <t-kristo@ti.com>,
"Gerlach, Dave" <d-gerlach@ti.com>,
"paul@pwsan.com" <paul@pwsan.com>,
"linux@armlinux.org.uk" <linux@armlinux.org.uk>
Subject: Re: [PATCH] ARM: AM43XX: hwmod: Fix RSTST register offset for pruss
Date: Wed, 22 Jun 2016 14:40:16 +0530 [thread overview]
Message-ID: <576A55F8.4070906@ti.com> (raw)
In-Reply-To: <57690F83.80709@ti.com>
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 while it worked on AM33xx,
>>> AM437x failed because of this difference.
>>
>> Okay, seems on am335x, PER doesn't have RSTST register itself.
>
> Seems like code has some reference!
>
> arch/arm/mach-omap2/prm33xx.h
> #define AM33XX_RM_PER_RSTST_OFFSET 0x0004
>
> But TRM: http://www.ti.com/lit/ug/spruh73m/spruh73m.pdf
> claims that offset is reserved.
>
> Should i remove the above lines altogether?
>
Can you pull this patch as well?
>>
>> Regards
>> afzal
>>
next prev parent reply other threads:[~2016-06-22 9:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 3:52 [PATCH] ARM: AM43XX: hwmod: Fix RSTST register offset for pruss Keerthy
2016-06-20 7:05 ` Mohammed, Afzal
2016-06-20 8:23 ` Keerthy
2016-06-20 16:19 ` Suman Anna
2016-06-21 7:52 ` Mohammed, Afzal
2016-06-21 9:57 ` Keerthy
2016-06-22 9:10 ` Keerthy [this message]
2016-06-22 9:59 ` Tony Lindgren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=576A55F8.4070906@ti.com \
--to=a0393675@ti.com \
--cc=afzal@ti.com \
--cc=d-gerlach@ti.com \
--cc=j-keerthy@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=paul@pwsan.com \
--cc=s-anna@ti.com \
--cc=t-kristo@ti.com \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).