From: Timo Teras <timo.teras@solidboot.com>
To: David Brownell <david-b@pacbell.net>
Cc: Linux-OMAP <linux-omap-open-source@linux.omap.com>
Subject: Re: [patch 2.6.18-omap] omap2/gpmc updates
Date: Thu, 19 Oct 2006 10:15:03 +0300 [thread overview]
Message-ID: <20061019071503.GA25971@mail.solidboot.com> (raw)
In-Reply-To: <200610181342.14796.david-b@pacbell.net>
On Wed, Oct 18, 2006 at 01:42:14PM -0700, David Brownell wrote:
> Note that this API is glitchy; likely the best fix would be to add
> a member to "struct gpmc_timings" to hold GPMC_CONFIG1, since that
> holds one key aspect of the GPMC timings (the gpmc_fclk divisor,
> and sync vs. async == whether that divisor matters).
Something like that would be useful. Also currently you can only calculate
the timings in nanosecond precision. This is not enough in some cases
e.g. when calculating sync. timings and the tick length is not multiple of
nanosecond. We need picosecond precision or the possiblity to configure
ticks directly.
Cheers,
Timo
next prev parent reply other threads:[~2006-10-19 7:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 20:42 [patch 2.6.18-omap] omap2/gpmc updates David Brownell
2006-10-19 7:15 ` Timo Teras [this message]
2006-10-19 18:44 ` David Brownell
2006-10-19 13:35 ` Tony Lindgren
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=20061019071503.GA25971@mail.solidboot.com \
--to=timo.teras@solidboot.com \
--cc=david-b@pacbell.net \
--cc=linux-omap-open-source@linux.omap.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