linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v2 3/3] ARM: shmobile: r8a7790: Wait for status on all MSTP clocks
Date: Thu, 21 Nov 2013 08:27:06 +0000	[thread overview]
Message-ID: <1477402.ex0BAyNzcT@avalon> (raw)
In-Reply-To: <1384357973-27365-4-git-send-email-laurent.pinchart+renesas@ideasonboard.com>

Hi Morimoto-san,

On Wednesday 20 November 2013 18:11:52 Kuninori Morimoto wrote:
> Hi Laurent
> 
> > From: Shinya Kuribayashi <shinya.kuribayashi.px@renesas.com>
> > 
> > When enabling a module clock by clearing its bit in the MSTP control
> > register, the CPG requires waiting for the status register to signal
> > that the clock has started. Failure to do so will result in returning
> > from the clk_enable() call with the clock potentially still disabled,
> > leading to various race conditions and difficult to debug errors.
> > 
> > Enable status wait for all MSTP clocks on the r8a7790.
> > 
> > Signed-off-by: Shinya Kuribayashi <shinya.kuribayashi.px@renesas.com>
> > Signed-off-by: Laurent Pinchart
> > <laurent.pinchart+renesas@ideasonboard.com>
> > ---
> > 
> >  arch/arm/mach-shmobile/clock-r8a7790.c | 90  +++++++++++++++-------------
> >  1 file changed, 49 insertions(+), 41 deletions(-)
> > 
> > diff --git a/arch/arm/mach-shmobile/clock-r8a7790.c
> > b/arch/arm/mach-shmobile/clock-r8a7790.c index 9fa39d1..6c65b70 100644
> > --- a/arch/arm/mach-shmobile/clock-r8a7790.c
> > +++ b/arch/arm/mach-shmobile/clock-r8a7790.c
> > @@ -43,16 +43,24 @@
> > 
> >   *	see "p1 / 2" on R8A7790_CLOCK_ROOT() below
> >   */
> > 
> > -#define CPG_BASE 0xe6150000
> > -#define CPG_LEN 0x1000
> > -
> > -#define SMSTPCR1 0xe6150134
> > -#define SMSTPCR2 0xe6150138
> > -#define SMSTPCR3 0xe615013c
> > -#define SMSTPCR5 0xe6150144
> > -#define SMSTPCR7 0xe615014c
> > -#define SMSTPCR8 0xe6150990
> > -#define SMSTPCR9 0xe6150994
> > +#define CPG_BASE	0xe6150000
> > +#define CPG_LEN		0x1000
> > +
> > +#define SMSTPCR1	0xe6150134
> > +#define SMSTPCR2	0xe6150138
> > +#define SMSTPCR3	0xe615013c
> > +#define SMSTPCR5	0xe6150144
> > +#define SMSTPCR7	0xe615014c
> > +#define SMSTPCR8	0xe6150990
> > +#define SMSTPCR9	0xe6150994
> > +
> > +#define MSTPSR1		IOMEM(0xe6150038)
> > +#define MSTPSR2		IOMEM(0xe6150040)
> > +#define MSTPSR3		IOMEM(0xe6150048)
> > +#define MSTPSR5		IOMEM(0xe615003c)
> > +#define MSTPSR7		IOMEM(0xe61501c4)
> > +#define MSTPSR8		IOMEM(0xe61509a0)
> > +#define MSTPSR9		IOMEM(0xe61509a4)
> 
> Similar comment here.
> cleanup (?) CPG_xxx / SMSTPCRx are out of this purpose ?

I'm just making the alignment consistent, I don't think it should be split to 
a separate patch.

-- 
Regards,

Laurent Pinchart


      parent reply	other threads:[~2013-11-21  8:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-13 15:52 [PATCH v2 3/3] ARM: shmobile: r8a7790: Wait for status on all MSTP clocks Laurent Pinchart
2013-11-21  2:11 ` Kuninori Morimoto
2013-11-21  8:27 ` Laurent Pinchart [this message]

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=1477402.ex0BAyNzcT@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --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).