From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 2/2] ARM: shmobile: r8a7740 dtsi: Correct IIC0 parent clock
Date: Wed, 12 Nov 2014 02:25:50 +0000 [thread overview]
Message-ID: <20141112022549.GG11597@verge.net.au> (raw)
In-Reply-To: <1415181874-21549-2-git-send-email-geert+renesas@glider.be>
On Wed, Nov 12, 2014 at 09:57:02AM +0900, Simon Horman wrote:
> On Mon, Nov 10, 2014 at 09:57:46AM +0900, Simon Horman wrote:
> > On Wed, Nov 05, 2014 at 11:04:34AM +0100, Geert Uytterhoeven wrote:
> > > According to the datasheet, the operating clock for IIC0 is the HPP
> > > (RT Peri) clock, not the SUB (Peri) clock. Both clocks run at the same
> > > speed (50 Mhz).
> > >
> > > This is consistent with IIC0 being located in the A4R PM domain, and
> > > IIC1 in the A3SP PM domain.
> >
> > Thanks, I have queued this up.
>
> Hi Geert,
>
> As this appears to be a bug fix I would like to accompany this patch with
> some text describing when the problem was introduced and what its effects
> are. In short a rough guide to if it should be applied to -stable. To that
> end I prepared the following which I would appreciate your feedback on.
>
> * ARM: shmobile: r8a7740 dtsi: Correct IIC0 parent clock
>
> This problem was introduced when clock support was added DT for the
> r8a7740 by d9ffd583bf345e2ea ("ARM: shmobile: r8a7740: add SoC clocks to
> DTS") in v3.17.
s/v3.17/v3.18-rc1/
> I am not aware of any run-time effect of this problem.
next prev parent reply other threads:[~2014-11-12 2:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 10:04 [PATCH 2/2] ARM: shmobile: r8a7740 dtsi: Correct IIC0 parent clock Geert Uytterhoeven
2014-11-10 0:57 ` Simon Horman
2014-11-12 0:57 ` Simon Horman
2014-11-12 2:25 ` Simon Horman [this message]
2014-11-12 9:09 ` Geert Uytterhoeven
2014-11-12 11:04 ` Geert Uytterhoeven
-- strict thread matches above, loose matches on Subject: below --
2014-11-13 1:20 [GIT PULL] Renesas ARM Based SoC DT Fixes for v3.18 Simon Horman
2014-11-13 1:20 ` [PATCH 2/2] ARM: shmobile: r8a7740 dtsi: Correct IIC0 parent clock 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=20141112022549.GG11597@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