public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@ti.com>
To: linux-omap@vger.kernel.org
Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>, charu@ti.com
Subject: [PATCH 0/2] OMAP: GPIO: cleanup: first pass at ifdef removal
Date: Wed, 20 Apr 2011 17:13:49 -0700	[thread overview]
Message-ID: <1303344831-7889-1-git-send-email-khilman@ti.com> (raw)

This series is a first pass at the #ifdef removal cleanup.  

To demonstrate the type of changes needed for the cleanup, the
direction and data input/output functions are handled first.  Register
offset fields are added to platform_data so #ifdefs can be removed.

Similar needs to be done for the remaining #ifdefs.

Currently boot tested on 3430/n900 only.

Series applies to v2.6.39-rc4.

Kevin Hilman (2):
  OMAP: GPIO: move register offset defines into gpio.h
  OMAP: GPIO: consolidate direction, input, output, remove #ifdefs

 arch/arm/mach-omap1/gpio15xx.c         |    7 +
 arch/arm/mach-omap1/gpio16xx.c         |   15 ++
 arch/arm/mach-omap1/gpio7xx.c          |   15 ++
 arch/arm/mach-omap2/gpio.c             |   10 +
 arch/arm/plat-omap/gpio.c              |  328 +++----------------------------
 arch/arm/plat-omap/include/plat/gpio.h |  111 +++++++++++
 6 files changed, 190 insertions(+), 296 deletions(-)

-- 
1.7.4


             reply	other threads:[~2011-04-21  0:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-21  0:13 Kevin Hilman [this message]
2011-04-21  0:13 ` [PATCH 1/2] OMAP: GPIO: move register offset defines into gpio.h Kevin Hilman
2011-04-21  0:13 ` [PATCH 2/2] OMAP: GPIO: consolidate direction, input, output, remove #ifdefs Kevin Hilman
2011-04-21  8:32 ` [PATCH 0/2] OMAP: GPIO: cleanup: first pass at ifdef removal DebBarma, Tarun Kanti
2011-04-21 15:12   ` Kevin Hilman

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=1303344831-7889-1-git-send-email-khilman@ti.com \
    --to=khilman@ti.com \
    --cc=charu@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=santosh.shilimkar@ti.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