linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: valentin.longchamp@epfl.ch (Valentin Longchamp)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mx31moboard: fix typo
Date: Wed, 09 Dec 2009 13:44:50 +0100	[thread overview]
Message-ID: <4B1F9BC2.6010205@epfl.ch> (raw)
In-Reply-To: <20091204174623.GW14091@buzzloop.caiaq.de>

Daniel Mack wrote:
> 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).

Well, there are not a lot of information about the IIM in the reference 
manual (only Tables 13-1 for the different fuses and 13-2 for the 
silicon revisions). I wanted to check for the registers to find maybe a 
problem, but found nothing more

> 
> 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.
> 

The clock is running (well, at least the parent ipg_clk and the gating 
is configured for the clock running, thanks to clk_enable(&iim_clk);

About the bootloader, on our boards we have redboot, adapted from the 
release Freescale did for the ADS. So it may be a bootloader issue. What 
could be missing in my bootloader that makes this read fail ?

I would say that maybe someting the EMI or SPBA configuration is missing 
so that I can access the addresses in this range. Any ideas ?

Val

-- 
Valentin Longchamp, PhD Student, EPFL-STI-LSRO1
valentin.longchamp at epfl.ch, Phone: +41216937827
http://people.epfl.ch/valentin.longchamp
MEA3485, Station 9, CH-1015 Lausanne

  reply	other threads:[~2009-12-09 12:44 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
2009-12-09 12:44         ` Valentin Longchamp [this message]
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=4B1F9BC2.6010205@epfl.ch \
    --to=valentin.longchamp@epfl.ch \
    --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).