public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Philip Balister <philip@balister.org>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: GPMC setup help
Date: Mon, 9 Nov 2009 14:26:59 -0800	[thread overview]
Message-ID: <20091109222658.GK23952@atomide.com> (raw)
In-Reply-To: <4AE75B05.7010701@balister.org>

Hi,

* Philip Balister <philip@balister.org> [091027 13:41]:
> I've been going round and round on this for a couple of days. I have
> a logic analyzer (cheap USB, that is why come edges are not quite
> synced) attached to the gpmc pins on a logicpd dev board. The read
> cycle timings are what I expect.
> 
> The write cycle seems to do one cycle OK, then thing go into the weeds.
> 
> Here are the values I write into the registers:
> 
> GPMC_CONFIG1 reg: 1200
> 
> GPMC_CONFIG2 reg: 40400
> 
> GPMC_CONFIG3 reg: 20201
> 
> GPMC_CONFIG4 reg: 4030403
> 
> GPMC_CONFIG5 reg: 1040505
> 
> GPMC_CONFIG6 reg: 4030000
> 
> and here is a screen shot of the logic analyzer:
> 
> http://balister.dyndns.org:8008/~balister/gpmc-write.png

This won't help with your current problem probably..

But once you get things working, please take a look the gpmc.c.
The GPMC values should be dynamically calculated depending on
the L3 speed. There are several examples of that in gpmc-onenand.c
and gpmc-smc91x.c.

You should be able to calculate the timings needed from the
external device data sheets. Also, Paul noted earlier that for
some devices you also need to add up the latencies for the level
shifter.

Then while at it, maybe check with your logic analyzer to make
sure the timings set using gpmc.c really are what we're trying
them to? I don't think anybody has ever verified that.

Regards,

Tony

      reply	other threads:[~2009-11-09 22:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-27 20:41 GPMC setup help Philip Balister
2009-11-09 22:26 ` Tony Lindgren [this message]

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=20091109222658.GK23952@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=philip@balister.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