From mboxrd@z Thu Jan 1 00:00:00 1970 From: Simon Horman Date: Fri, 01 Nov 2013 00:23:16 +0000 Subject: Re: [PATCH 1/2] ARM: shmobile: wait for MSTP clock status to toggle, when enabling it Message-Id: <20131101002315.GG6818@verge.net.au> List-Id: References: <1383066834-25956-2-git-send-email-laurent.pinchart+renesas@ideasonboard.com> In-Reply-To: <1383066834-25956-2-git-send-email-laurent.pinchart+renesas@ideasonboard.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-sh@vger.kernel.org On Fri, Nov 01, 2013 at 09:18:14AM +0900, Simon Horman wrote: > On Thu, Oct 31, 2013 at 01:34:04PM +0100, Laurent Pinchart wrote: > > Hi Simon, > > > > On Thursday 31 October 2013 14:34:48 Simon Horman wrote: > > > On Tue, Oct 29, 2013 at 06:13:53PM +0100, Laurent Pinchart wrote: > > > > From: Guennadi Liakhovetski > > > > > > > > On r-/sh-mobile SoCs MSTP clocks are used by the runtime PM to dynamically > > > > enable and disable peripheral clocks. To make sure the clock has really > > > > started we have to read back its status register until it confirms > > > > success. > > > > > > > > Signed-off-by: Guennadi Liakhovetski > > > > Signed-off-by: Laurent Pinchart > > > > > > > > > > Is there an impact of this patch on shmobile, that is ARM SoCs or boards > > > based on them? > > > > There's no impact on existing SoCs or boards, as this patch adds support for a > > feature that is turned on by default. SoCs need to explicitly enable it when > > declaring the MSTP clocks to get any behaviour change. > > Ok. Is there a plan to make use of this on the shmobile (ARM) side? Sorry for not being more thorough. I now see that you have pointed out that is is used by patch 2 in this series, which is for shmobile. I will see if I can have a word to Paul about the best way to move this forwards.