From: Mike Rapoport <mike@compulab.co.il>
To: linux-omap@vger.kernel.org
Cc: tony@atomide.com, vimal.newwork@gmail.com, s-ghorai@ti.com,
Mike Rapoport <mike@compulab.co.il>
Subject: [PATCH v2 0/3] omap: gpmc-nand: add ability to keep timings defined by the bootloader
Date: Thu, 29 Apr 2010 11:48:09 +0300 [thread overview]
Message-ID: <cover.1272530653.git.mike@compulab.co.il> (raw)
These patches add ability to keep GPMC timings configured by the
bootloader. The platforms have to either define NAND GPMC timinings
explicitly via gpmc_t field of omap_nand_platform_data or set
keep_timings flag to allow detection of current timing configuration
and its subsequent use in omap2_nand_gpmc_retime.
v2 changes:
- remove debug leftovers
- make timing rounding depend on .keep_timing flag and introduce
omap2_nand_gpmc_round_timings to facilitate this change
Mike Rapoport (3):
omap: gpmc: add gpmc_cs_get_timings
omap: gpmc-nand: introduce omap2_nand_gpmc_round_timings helper
omap: gpmc-nand: add ability to keep timings defined by the
bootloader
arch/arm/mach-omap2/gpmc-nand.c | 73 +++++++++++++++++++------------
arch/arm/mach-omap2/gpmc.c | 76 ++++++++++++++++++++++++++++++++
arch/arm/plat-omap/include/plat/gpmc.h | 1 +
arch/arm/plat-omap/include/plat/nand.h | 1 +
4 files changed, 123 insertions(+), 28 deletions(-)
next reply other threads:[~2010-04-30 21:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-29 8:48 Mike Rapoport [this message]
2010-04-29 8:48 ` [PATCH v2 1/3] omap: gpmc: add gpmc_cs_get_timings Mike Rapoport
2010-04-29 8:48 ` [PATCH v2 2/3] omap: gpmc-nand: introduce omap2_nand_gpmc_round_timings helper Mike Rapoport
2010-04-29 8:48 ` [PATCH v2 3/3] omap: gpmc-nand: add ability to keep timings defined by the bootloader Mike Rapoport
2010-05-03 18:24 ` Tony Lindgren
2010-05-03 20:32 ` Mike Rapoport
2010-05-03 21:16 ` Tony Lindgren
2010-05-04 13:22 ` Mike Rapoport
2010-05-04 21:46 ` 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=cover.1272530653.git.mike@compulab.co.il \
--to=mike@compulab.co.il \
--cc=linux-omap@vger.kernel.org \
--cc=s-ghorai@ti.com \
--cc=tony@atomide.com \
--cc=vimal.newwork@gmail.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;
as well as URLs for NNTP newsgroup(s).