From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh: sh7785 early scif fix
Date: Fri, 08 May 2009 02:39:12 +0000 [thread overview]
Message-ID: <20090508023911.GB26125@linux-sh.org> (raw)
In-Reply-To: <20090507101744.31631.58621.sendpatchset@rx1.opensource.se>
On Thu, May 07, 2009 at 07:17:44PM +0900, Magnus Damm wrote:
> This patch moves the SH4 case of EARLY_SCIF_CONSOLE_PORT
> so the SH7785 default value gets used. Without this patch
> the value for SH7785 is set to 0xffe80000.
On Thu, May 07, 2009 at 07:31:39PM +0900, Magnus Damm wrote:
> Make sure that clk->ops->init() only gets called once in
> the case of CLK_ALWAYS_ENABLED. Without this patch the
> init() callback may be called multiple times.
On Thu, May 07, 2009 at 07:44:55PM +0900, Magnus Damm wrote:
> Update the r7785 highlander defconfig to fix
> PCLK value and that mode4 is set high.
On Thu, May 07, 2009 at 07:55:37PM +0900, Magnus Damm wrote:
> This patch adds TMU platform data for sh7785. Both clockevent
> and clocksource support is enabled.
I've applied these, thanks.
prev parent reply other threads:[~2009-05-08 2:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-07 10:17 [PATCH] sh: sh7785 early scif fix Magnus Damm
2009-05-08 2:39 ` 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=20090508023911.GB26125@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