public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Nikula <jarkko.nikula@bitmer.com>
To: Tony Lindgren <tony@atomide.com>
Cc: CF Adad <cfadad@rocketmail.com>,
	"Shilimkar, Santosh" <santosh.shilimkar@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Please help! AM35xx mm/slab.c BUG
Date: Wed, 06 Jun 2012 13:37:15 +0300	[thread overview]
Message-ID: <4FCF32DB.7000208@bitmer.com> (raw)
In-Reply-To: <20120606084123.GU12766@atomide.com>

my 2 cents.

On 06/06/2012 11:41 AM, Tony Lindgren wrote:
> * CF Adad <cfadad@rocketmail.com> [120606 00:55]:
>>
>> Do you folks know of a good reference for properly calculating these GPMC settings?
> 
> In theory you just need to know the timings of connected components,
> then check which ones depend on cycles and which ones depend on time.
> 
I afraid paper-and-pencil gpmc exercise is often required but after that
it is more easy to see from charts if e.g. original settings were not
optimal or too near to edge. Helps to understand and point possible
problems on oscilloscope measurements too.

> Also take into account latencies added by level shifters if you have those.
> Paul Walmsley noticed a few years ago that those affected the smsc911x
> timings if not accounted for.
> 
I've noticed the same. Even one-directional level shifters easily add a
few ns and double amount in read operation since then there are two
level shifters in a path: one in clk/cs/oe/etc cpu-to-chip signal and
one on chip-to-cpu side.

Pay also attention if there are extra latencies in chip. Chip memory
reads/writes may be slower than chip register access (probably similar
than smsc fifo issue what Tony mentioned earlier in this thread).

-- 
Jarkko

  reply	other threads:[~2012-06-06 10:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-05  6:37 Please help! AM35xx mm/slab.c BUG CF Adad
2012-06-05  7:08 ` Tony Lindgren
2012-06-05 16:29   ` CF Adad
2012-06-06  6:14     ` CF Adad
2012-06-06  6:36       ` Shilimkar, Santosh
2012-06-06  7:08         ` CF Adad
2012-06-06  7:10         ` Tony Lindgren
2012-06-06  7:51           ` CF Adad
2012-06-06  8:41             ` Tony Lindgren
2012-06-06 10:37               ` Jarkko Nikula [this message]
2012-06-06 15:53                 ` CF Adad
2012-06-07  9:32             ` Mohammed, Afzal
2012-06-07 19:50               ` CF Adad
2012-06-12 11:14                 ` Mohammed, Afzal
2012-06-12 15:27                   ` CF Adad
2012-06-14 17:28                   ` CF Adad
2012-06-14 19:10                     ` jean-philippe francois
2012-06-15  4:23                       ` CF Adad
2012-06-19  1:29                   ` CF Adad
2012-06-19  6:29                     ` Mohammed, Afzal

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=4FCF32DB.7000208@bitmer.com \
    --to=jarkko.nikula@bitmer.com \
    --cc=cfadad@rocketmail.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=santosh.shilimkar@ti.com \
    --cc=tony@atomide.com \
    /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