From: Mike Rapoport <mike@compulab.co.il>
To: tony@atomide.com
Cc: s-ghorai@ti.com, linux-omap@vger.kernel.org,
Mike Rapoport <mike@compulab.co.il>
Subject: [PATCH 0/2] omap: gpmc-nand: add ability to keep timings defined by the bootloader
Date: Wed, 28 Apr 2010 19:06:03 +0300 [thread overview]
Message-ID: <cover.1272470212.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.
The following changes since commit 104a77440f05430f29f9d3f4ecb88c1536819585:
Tony Lindgren (1):
Linux-omap rebuilt: Merged in i2c-omap-for-ben branch and cleaned up cbus branch
Mike Rapoport (2):
omap: gpmc: add gpmc_cs_get_timings
omap: gpmc-nand: add ability to keep timings defined by the
bootloader
arch/arm/mach-omap2/gpmc-nand.c | 19 +++++++-
arch/arm/mach-omap2/gpmc.c | 79 ++++++++++++++++++++++++++++++++
arch/arm/plat-omap/include/plat/gpmc.h | 1 +
arch/arm/plat-omap/include/plat/nand.h | 1 +
4 files changed, 99 insertions(+), 1 deletions(-)
next reply other threads:[~2010-04-28 16:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-28 16:06 Mike Rapoport [this message]
2010-04-28 16:06 ` [PATCH 1/2] omap: gpmc: add gpmc_cs_get_timings Mike Rapoport
2010-04-28 16:06 ` [PATCH 2/2] omap: gpmc-nand: add ability to keep timings defined by the bootloader Mike Rapoport
2010-04-29 4:27 ` Vimal Singh
2010-04-29 6:53 ` Mike Rapoport
2010-04-29 7:11 ` Vimal Singh
2010-04-29 7:27 ` Mike Rapoport
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.1272470212.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 \
/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