From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 2/2] ARM: mach-shmobile: mackerel: fixup memory
Date: Thu, 17 Feb 2011 00:41:59 +0000 [thread overview]
Message-ID: <20110217004158.GA27179@verge.net.au> (raw)
In-Reply-To: <w3phbc5yjly.wl%kuninori.morimoto.gx@renesas.com>
On Tue, Feb 15, 2011 at 02:03:53PM +0900, Kuninori Morimoto wrote:
> Current makerel had issue which couldn't boot sometimes.
> This patch fixup it.
>
> Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Hi Morimoto-san,
I have verified that this boots on my Mackerel.
I have also looked over the register changes
and they seem reasonable to me.
Reviewed-by: Simon Horman <horms@verge.net.au>
> ---
> .../mach-shmobile/include/mach/head-mackerel.txt | 10 +++++-----
> 1 files changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/arch/arm/mach-shmobile/include/mach/head-mackerel.txt b/arch/arm/mach-shmobile/include/mach/head-mackerel.txt
> index efd3687..3029aba 100644
> --- a/arch/arm/mach-shmobile/include/mach/head-mackerel.txt
> +++ b/arch/arm/mach-shmobile/include/mach/head-mackerel.txt
> @@ -6,13 +6,10 @@ LIST "RWT Setting"
> EW 0xE6020004, 0xA500
> EW 0xE6030004, 0xA500
>
> -DD 0x01001000, 0x01001000
> -
> LIST "GPIO Setting"
> EB 0xE6051013, 0xA2
>
> LIST "CPG"
> -ED 0xE6150080, 0x00000180
> ED 0xE61500C0, 0x00000002
>
> WAIT 1, 0xFE40009C
> @@ -37,6 +34,9 @@ ED 0xE615002C, 0x93000040
>
> WAIT 1, 0xFE40009C
>
> +LIST "SUB/USBClk"
> +ED 0xE6150080, 0x00000180
> +
> LIST "BSC"
> ED 0xFEC10000, 0x00E0001B
>
> @@ -53,7 +53,7 @@ ED 0xFE400048, 0x20C18505
> ED 0xFE40004C, 0x00110209
> ED 0xFE400010, 0x00000087
>
> -WAIT 10, 0xFE40009C
> +WAIT 30, 0xFE40009C
>
> ED 0xFE400084, 0x0000003F
> EB 0xFE500000, 0x00
> @@ -84,7 +84,7 @@ ED 0xE6150004, 0x80331050
>
> WAIT 1, 0xFE40009C
>
> -ED 0xE6150354, 0x00000002
> +ED 0xFE400354, 0x01AD8002
I don't see 0xE6150354 in the processor manual. Was it a typo?
> LIST "SCIF0 - Serial port for earlyprintk"
> EB 0xE6053098, 0x11
> --
> 1.7.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-sh" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2011-02-17 0:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 5:03 [PATCH 2/2] ARM: mach-shmobile: mackerel: fixup memory initialize for Kuninori Morimoto
2011-02-17 0:41 ` Simon Horman [this message]
2011-02-17 1:11 ` [PATCH 2/2] ARM: mach-shmobile: mackerel: fixup memory initialize Kuninori Morimoto
2011-05-25 2:49 ` [PATCH 2/2] ARM: mach-shmobile: mackerel: add renesas_usbhs support Kuninori Morimoto
2011-05-25 2:57 ` [PATCH 2/2] ARM: mach-shmobile: mackerel: add renesas_usbhs support for USB1 Paul Mundt
2011-05-25 4:24 ` [PATCH 2/2] ARM: mach-shmobile: mackerel: add renesas_usbhs Kuninori Morimoto
2011-05-25 5:40 ` [PATCH 2/2] ARM: mach-shmobile: mackerel: add renesas_usbhs support for USB1 Paul Mundt
2012-03-01 4:25 ` [PATCH 2/2] ARM: mach-shmobile: mackerel: Add FSI DMAEngine support Kuninori Morimoto
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=20110217004158.GA27179@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;
as well as URLs for NNTP newsgroup(s).