From: Paul Walmsley <paul@pwsan.com>
To: linux-omap@vger.kernel.org
Subject: [PATCH 0/2] OMAP2/3: fix clock/clockdomain bugs
Date: Tue, 12 Aug 2008 15:31:41 -0600 [thread overview]
Message-ID: <20080812212919.24628.82229.stgit@localhost.localdomain> (raw)
This series fixes two bugs that cause N800 to panic on boot:
- a OMAP2xxx clock code bug, which caused an "Unhandled fault:
alignment exception (0x001) at 0xc02....." panic; and
- an OMAP2/3 clockdomain bug, which caused an "Unable to handle kernel
paging request at virtual address 5f75706d" panic.
These bugs were exposed by 0e5194e1a84c219bebbb78f305b7a8eabc4a3656 and
718fc6cd4db902aa2242a736cc3feb8744a4c71a.
With the following patches applied on git head, N800 boots fine, but
only if CONFIG_DEBUG_LL is enabled. If it is disabled, it hangs at
some point in early boot. Don't know why.
These patches also boot-tested cleanly on 2430SDP and 3430SDP, both
with and without CONFIG_DEBUG_LL.
text data bss dec hex filename
3217805 149808 85008 3452621 34aecd vmlinux.n800.orig
3217837 149808 85008 3452653 34aeed vmlinux.n800
arch/arm/mach-omap2/clock24xx.c | 2 ++
arch/arm/mach-omap2/clockdomain.c | 6 ++++++
2 files changed, 8 insertions(+), 0 deletions(-)
next reply other threads:[~2008-08-12 21:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-12 21:31 Paul Walmsley [this message]
2008-08-12 21:31 ` [PATCH 1/2] OMAP2 clock: associate clocks with clockdomains at startup Paul Walmsley
2008-08-12 21:31 ` [PATCH 2/2] OMAP2/3 clockdomains: autodeps should respect platform flags Paul Walmsley
2008-08-13 7:43 ` [PATCH 0/2] OMAP2/3: fix clock/clockdomain bugs Tony Lindgren
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=20080812212919.24628.82229.stgit@localhost.localdomain \
--to=paul@pwsan.com \
--cc=linux-omap@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