From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 0/6] ARM: mach-shmobile: FSI clock fixup
Date: Wed, 24 Nov 2010 06:00:24 +0000 [thread overview]
Message-ID: <20101124060024.GD11705@linux-sh.org> (raw)
In-Reply-To: <w3pd3q14w2t.wl%kuninori.morimoto.gx@renesas.com>
On Fri, Nov 19, 2010 at 04:22:02PM +0900, Kuninori Morimoto wrote:
>
> Dear Paul, Magnus, Mark, Liam, Guennadi
>
> These patches are FSI clock fixup
>
> Kuninori Morimoto (6):
> ARM: mach-shmobile: clock-sh7372: remove fsidiv bogus disable
> ARM: mach-shmobile: ap4evb: FSI clock use proper process for HDMI
> ARM: mach-shmobile: ap4evb: FSI clock use proper process for ak4642
> ARM: mach-shmobile: clock-sh7372: modify error code
> ARM: mach-shmobile: clock-sh7372: remove unnecessary fsi clocks
> ARM: mach-shmobile: clock-sh7372: remove pllc2 clock bogus
>
> These patches modify bogus control of FSI clock.
> To modify it, FSI driver was changed.
> I tested these patches on AP4 and Ecovec.
>
> >> Mark, Liam
>
> Can you please check #2 #3 patches ?
> It change FSI driver.
>
> >> Magnus, Paul, Guennadi
>
> The last patch change pllc2 bogus, but I'm not sure about it.
> Of course I tested it though.
> I put it as RFC.
>
This is fixing the same bogosity that the FSI clock was doing, so it's a
good step. The FSI changes we do want for .37 anyways, as we don't want
to have that going out with clocks in a half-usable state, it makes sense
to roll the pllc2 change in at the same time.
If Liam or Mark wish to provide Acks for the FSI driver bits I'll add
those in, otherwise I'll plan to send this series (with v2 of patch #2)
to Linus this week.
prev parent reply other threads:[~2010-11-24 6:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 7:22 [PATCH 0/6] ARM: mach-shmobile: FSI clock fixup Kuninori Morimoto
2010-11-24 6:00 ` Paul Mundt [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=20101124060024.GD11705@linux-sh.org \
--to=lethal@linux-sh.org \
--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).