From mboxrd@z Thu Jan 1 00:00:00 1970 From: Suman Anna Subject: Re: [PATCH] ARM: AM43XX: hwmod: Fix RSTST register offset for pruss Date: Mon, 20 Jun 2016 11:19:07 -0500 Message-ID: <5768177B.9070306@ti.com> References: <1466394745-983-1-git-send-email-j-keerthy@ti.com> <5E94841CD408F1498111ED1D1196B1B237B18D3A@DBDE04.ent.ti.com> <5767A81E.1040809@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <5767A81E.1040809@ti.com> Sender: linux-kernel-owner@vger.kernel.org To: Keerthy , "Mohammed, Afzal" , "J, KEERTHY" , "tony@atomide.com" Cc: "linux-omap@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "Kristo, Tero" , "Gerlach, Dave" , "paul@pwsan.com" , "linux@armlinux.org.uk" List-Id: linux-omap@vger.kernel.org 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 offset value. >> >>> This can lead to setting of wrong power state values for PER domain. >> >> Just curious, does it happen or noticed by going thr' the code ? 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. regards Suman > > No i was trying omap4_prminst_deassert_hardreset on AM43XX on my local > tree and i saw issues and then saw that RSTST register offsets were > wrongly populated. Hence fixing the same. > >> >> Regards >> afzal >>