From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 1/2] ARM: shmobile: wait for MSTP clock status to toggle, when enabling it
Date: Fri, 01 Nov 2013 00:18:14 +0000 [thread overview]
Message-ID: <20131101001813.GF6818@verge.net.au> (raw)
In-Reply-To: <1383066834-25956-2-git-send-email-laurent.pinchart+renesas@ideasonboard.com>
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 <g.liakhovetski@gmx.de>
> > >
> > > 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 <g.liakhovetski+renesas@gmail.com>
> > > Signed-off-by: Laurent Pinchart
> > > <laurent.pinchart+renesas@ideasonboard.com>
> >
> > 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?
next prev parent reply other threads:[~2013-11-01 0:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-29 17:13 [PATCH 1/2] ARM: shmobile: wait for MSTP clock status to toggle, when enabling it Laurent Pinchart
2013-10-31 5:34 ` Simon Horman
2013-10-31 12:34 ` Laurent Pinchart
2013-11-01 0:18 ` Simon Horman [this message]
2013-11-01 0:23 ` Simon Horman
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=20131101001813.GF6818@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-sh@vger.kernel.org \
/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).