From: daniel@caiaq.de (Daniel Mack)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mx31moboard: fix typo
Date: Fri, 4 Dec 2009 18:46:23 +0100 [thread overview]
Message-ID: <20091204174623.GW14091@buzzloop.caiaq.de> (raw)
In-Reply-To: <4B19473D.7010801@epfl.ch>
On Fri, Dec 04, 2009 at 06:30:37PM +0100, Valentin Longchamp wrote:
> Guennadi Liakhovetski wrote:
> >...to second that, yesterday's next also locks up hard on boot on
> >pcm037. .config available on request.
> >
>
> Same problem here. As a matter of fact, it comes from the mxc-master
> branch. I have bisected out the culprit:
>
> http://git.pengutronix.de/?p=imx/linux-2.6.git;a=commit;h=52939c03e53b151848da9e83fd839bddfda29e78
>
> It seems conform with the lock syndrom: very early at boot right
> after Uncompessing Linux and before any other message.
>
> The proc stalls on this read:
> srev = __raw_readl(IO_ADDRESS(IIM_BASE_ADDR) + MXC_IIMSREV);
>
> Maybe Guennadi and I have silicon revisions that do not work well
> with this patch (because I assume it worked well for Daniel).
Grmpf. Yes, it does work right on my LiteKit board, and the reference
manual reads like the register is there for a very long time (as it has
possible values for very old silicon revisions).
Could you double check whether the clock is running? The only thing I can
think of is differences in the bootloaders. I still have the proprietary
'losh' running here, which I have no sources for.
Daniel
next prev parent reply other threads:[~2009-12-04 17:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-03 19:30 [PATCH] mx31moboard: fix typo Robert Schwebel
2009-12-03 19:33 ` Robert Schwebel
2009-12-04 8:39 ` Valentin Longchamp
2009-12-04 11:14 ` Valentin Longchamp
2009-12-04 12:20 ` Sascha Hauer
2009-12-04 15:50 ` [PATCH 1/1] mx31moboard: fix usbh device names Valentin Longchamp
2009-12-04 9:14 ` [PATCH] mx31moboard: fix typo Guennadi Liakhovetski
2009-12-04 17:30 ` Valentin Longchamp
2009-12-04 17:46 ` Daniel Mack [this message]
2009-12-09 12:44 ` Valentin Longchamp
2009-12-09 13:57 ` Daniel Mack
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=20091204174623.GW14091@buzzloop.caiaq.de \
--to=daniel@caiaq.de \
--cc=linux-arm-kernel@lists.infradead.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).