All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Juha Kuikka <juha.kuikka@gmail.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: Problems with 2430 NAND prefetch engine
Date: Fri, 11 Apr 2008 12:22:27 -0700	[thread overview]
Message-ID: <20080411192227.GH7717@atomide.com> (raw)
In-Reply-To: <a46a26fd0804081733i469936d4m3315f3bb3270ff5@mail.gmail.com>

* Juha Kuikka <juha.kuikka@gmail.com> [080408 17:33]:
> Hi,
> 
> I am trying to use the NAND prefetch engine to speed up NAND access.
> 
> In GPMC CS0 is the NAND chip. GPMC_CONFIG7_0 is set to 0x0000084c by
> u-boot. Hence the address for this CS should be 0x0C000000.
> Documentation indicates that the FIFO should be accessible in any
> associated chip-select region after the engine has been enabled.
> 
> In linux I use ioremap() to map 0x0C000000 and use the returned
> pointer to access the prefetch engine FIFO.
> 
> Prefetch engine is configured and started.
> I get FIFOEVENT interrupt from it and try to read the fifo by using
> this ioremap's pointer but kernel crashes with:
> 
> Unhandled fault: external abort on non-linefetch (0x008) at 0xc4854000
> 0xc4854000 corresponds to the pointer ioremap() returned.
>
> Apparently I miss something either in HW or kernel but I cannot think
> of anything.
> Conventional access to the NAND chip through COMMAND/ADDRESS/DATA
> registers works ok.
> Any ideas would be appreciated.

Are you sure you have all the needed clocks on at this point? At least
gpmc_fck should be checked. Of course if access to gpmc works in
general, this is not the problem.

Tony

  reply	other threads:[~2008-04-11 19:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-09  0:33 Problems with 2430 NAND prefetch engine Juha Kuikka
2008-04-11 19:22 ` Tony Lindgren [this message]
2008-04-11 21:10   ` Juha Kuikka
2008-04-13 12:22     ` Choraria, Rohit
2008-04-13 19:18       ` Juha Kuikka

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=20080411192227.GH7717@atomide.com \
    --to=tony@atomide.com \
    --cc=juha.kuikka@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.