From mboxrd@z Thu Jan 1 00:00:00 1970 From: Suman Anna Subject: Re: [PATCHv5 06/15] hwspinlock/omap: enable module before reading SYSSTATUS register Date: Wed, 2 Jul 2014 14:38:04 -0500 Message-ID: <53B45F9C.2040209@ti.com> References: <1398904476-26200-1-git-send-email-s-anna@ti.com> <1398904476-26200-7-git-send-email-s-anna@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Ohad Ben-Cohen Cc: Mark Rutland , Kumar Gala , Tony Lindgren , Josh Cartwright , Bjorn Andersson , "linux-kernel@vger.kernel.org" , "linux-omap@vger.kernel.org" , "devicetree@vger.kernel.org" , linux-arm List-Id: devicetree@vger.kernel.org Hi Ohad, On 07/01/2014 07:51 AM, Ohad Ben-Cohen wrote: > Hi Suman, > > On Thu, May 1, 2014 at 3:34 AM, Suman Anna wrote: >> The number of hwspinlocks are determined based on the value read >> from the IP block's SYSSTATUS register. However, the module may >> not be enabled and clocked, and the read may result in a bus error. >> >> This particular issue is seen rather easily on AM33XX, since the >> module wakeup is software controlled, and it is disabled out of >> reset. Make sure the module is enabled and clocked before reading >> the SYSSTATUS register. > > This seems like a valid fix that is independent of this patch series. > > Feel free to submit it separately if you want, so we can get it merged. > OK, I will submit this patch and Patch 7 separately. regards Suman