linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: afzal@ti.com (Afzal Mohammed)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] OMAP-GPMC generic timing migration
Date: Fri, 5 Oct 2012 21:30:55 +0530	[thread overview]
Message-ID: <cover.1349450723.git.afzal@ti.com> (raw)

Hi,

This series provides a generic gpmc timing calculation routine. There
were three peripherals (OneNAND, tusb6010, smc91x) using custom timing
calculations, they are migrated to use the generic timing calculation.

Such a generic routine would help create a driver out of gpmc platform
code, which would be peripheral agnostic and thus lead to DT finally.
Input to generic timing calculation routine would be gpmc peripheral
timings, output - translated timings that gpmc can understand. Later,
to DT'ify, gpmc peripheral timings could be passed through DT. Input
timings that has been used here are selected such that it represents
those that are present in peripheral timing datasheets.

This series has been created by pulling out last 4 patches in v7
of the series,
"OMAP-GPMC: generic time calc, prepare for driver"
This was done to have easy path for common zImage gpmc cleanup patches.

Proposed generic routine has been tested on OneNAND (async) on
OMAP3EVM rev C (as mainline does not have the OneNAND support for this,
local patch were used to test). For other cases of custom timing
calculation (tusb6010, smc91x non-muxed, OneNAND sync), generic timing
calculation routine was verified by simulating on OMAP3EVM.

This series is available
        @ git://gitorious.org/x0148406-public/linux-kernel.git gpmc-timing-v1
and is based on
        linux-next (next-20121005)
and is dependent on
	http://marc.info/?l=linux-omap&m=134945131602622&w=2
	http://marc.info/?l=linux-omap&m=134945239306131&w=2

This series as such is only the first version, but these patches has
already undergone one change before being made as this series. The
change was in using ps instead of ns to prevent rounding errors.
Also along with this series documentation has been improved.

Regards
Afzal


Afzal Mohammed (4):
  ARM: OMAP2+: gpmc: generic timing calculation
  ARM: OMAP2+: onenand: generic timing calculation
  ARM: OMAP2+: smc91x: generic timing calculation
  ARM: OMAP2+: tusb6010: generic timing calculation

 Documentation/bus-devices/ti-gpmc.txt | 122 +++++++++++++
 arch/arm/mach-omap2/gpmc-onenand.c    | 124 +++++--------
 arch/arm/mach-omap2/gpmc-smc91x.c     |  43 ++---
 arch/arm/mach-omap2/gpmc.c            | 325 ++++++++++++++++++++++++++++++++++
 arch/arm/mach-omap2/gpmc.h            | 102 ++++++++---
 arch/arm/mach-omap2/usb-tusb6010.c    | 182 +++++--------------
 6 files changed, 633 insertions(+), 265 deletions(-)
 create mode 100644 Documentation/bus-devices/ti-gpmc.txt

-- 
1.7.12

             reply	other threads:[~2012-10-05 16:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-05 16:00 Afzal Mohammed [this message]
2012-10-05 16:01 ` [PATCH 1/4] ARM: OMAP2+: gpmc: generic timing calculation Afzal Mohammed
2012-10-05 16:01 ` [PATCH 2/4] ARM: OMAP2+: onenand: " Afzal Mohammed
2012-10-05 16:01 ` [PATCH 3/4] ARM: OMAP2+: smc91x: " Afzal Mohammed
2012-10-05 16:01 ` [PATCH 4/4] ARM: OMAP2+: tusb6010: " Afzal Mohammed
2012-10-09  3:01 ` [PATCH 0/4] OMAP-GPMC generic timing migration Tony Lindgren
2012-10-09 12:59   ` Afzal Mohammed
2012-10-11 11:45 ` Daniel Mack
2012-10-11 12:47   ` Mohammed, Afzal
2012-10-11 14:47     ` Tony Lindgren
2012-10-15 12:41       ` Mohammed, Afzal
2012-10-15 16:01         ` Tony Lindgren
2012-10-16  6:56           ` Afzal Mohammed
2012-10-17  5:42             ` Afzal Mohammed
2012-10-17 15:13               ` Daniel Mack
2012-10-17 15:53                 ` Tony Lindgren
2012-10-18  5:26                 ` Afzal Mohammed
2012-10-19 15:34   ` Afzal Mohammed
2012-10-22 19:51     ` Daniel Mack

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.1349450723.git.afzal@ti.com \
    --to=afzal@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).