From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v2 2/3] ARM: shmobile: r8a7779: Wait for status on selected MSTP clocks
Date: Mon, 25 Nov 2013 00:08:07 +0000 [thread overview]
Message-ID: <2011057.aML82f3mDe@avalon> (raw)
In-Reply-To: <1384357973-27365-3-git-send-email-laurent.pinchart+renesas@ideasonboard.com>
Hi Morimoto-san,
On Sunday 24 November 2013 16:05:42 Kuninori Morimoto wrote:
> Hi Laurent, Simon
>
> > > > From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > > >
> > > > When enabling some of the module clocks by clearing stop bits in the
> > > > MSTP control registers, the CPG requires waiting for the status
> > > > registers to signal that the clocks have 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 the r8a7779 MSTP clocks that report their
> > > > status.
> > > >
> > > > Signed-off-by: Laurent Pinchart
> > > > <laurent.pinchart+renesas@ideasonboard.com>
> > > > ---
> > > >
> > > > arch/arm/mach-shmobile/clock-r8a7779.c | 26 ++++++++++--------------
> > > > 1 file changed, 10 insertions(+), 16 deletions(-)
> > > >
> > > > diff --git a/arch/arm/mach-shmobile/clock-r8a7779.c
> > > > b/arch/arm/mach-shmobile/clock-r8a7779.c index b7ce0e7..1955738 100644
> > > > --- a/arch/arm/mach-shmobile/clock-r8a7779.c
> > > > +++ b/arch/arm/mach-shmobile/clock-r8a7779.c
> > > > @@ -52,12 +52,6 @@
> > > >
> > > > #define MSTPCR1 IOMEM(0xffc80034)
> > > > #define MSTPCR3 IOMEM(0xffc8003c)
> > > > #define MSTPSR1 IOMEM(0xffc80044)
> > > >
> > > > -#define MSTPSR4 IOMEM(0xffc80048)
> > > > -#define MSTPSR6 IOMEM(0xffc8004c)
> > > > -#define MSTPCR4 IOMEM(0xffc80050)
> > > > -#define MSTPCR5 IOMEM(0xffc80054)
> > > > -#define MSTPCR6 IOMEM(0xffc80058)
> > > > -#define MSTPCR7 IOMEM(0xffc80040)
> > >
> > > Why do you remove these MSTPCRx in this patch ?
> > > It is out-of this purpose
> >
> > I've removed them as they're unused. This could be split to a separate
> > patch if preferred, I've just thought it would be overkill.
>
> Yes, they are not used, but it doesn't have relationship to this patch.
I've considered the change to be related, at this patch fixes the MSTP clock
definitions. Of course if you disagree I'm fine with removing this change.
> (and, do we really need to remove these ?)
They're not used, so I thought it would be good to remove them.
> This is not super big deal,
> but I was ordered many times not to do such things at other ML.
>
> Let's follow the opinion of Simon.
Sounds good to me :-)
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-11-25 0:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 15:52 [PATCH v2 2/3] ARM: shmobile: r8a7779: Wait for status on selected MSTP clocks Laurent Pinchart
2013-11-21 2:07 ` Kuninori Morimoto
2013-11-21 8:26 ` Laurent Pinchart
2013-11-25 0:05 ` Kuninori Morimoto
2013-11-25 0:08 ` Laurent Pinchart [this message]
2013-11-25 0:23 ` Kuninori Morimoto
2013-11-25 3:36 ` Simon Horman
2013-11-25 14:19 ` Laurent Pinchart
2013-11-26 0:26 ` 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=2011057.aML82f3mDe@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