From: Tony Lindgren <tony@atomide.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 16:35:13 +0300 [thread overview]
Message-ID: <20061019133511.GD9983@atomide.com> (raw)
In-Reply-To: <200610181342.14796.david-b@pacbell.net>
* David Brownell <david-b@pacbell.net> [061018 23:44]:
> GPMC updates:
> - bugfixes: wrong/missing flags, omitted write, wrong test
> - don't map memory segments starting at zero
> - improve debug messaging
> - export gpmc_get_fclk_period() since it's needed to calc timings
> - expect gpmc_cs_set_timings() caller to have initialized sync vs async
>
> 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).
Pushing this today.
Tony
prev parent reply other threads:[~2006-10-19 13:35 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
2006-10-19 18:44 ` David Brownell
2006-10-19 13:35 ` 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=20061019133511.GD9983@atomide.com \
--to=tony@atomide.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