public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@ti.com>
To: "DebBarma, Tarun Kanti" <tarun.kanti@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"Shilimkar, Santosh" <santosh.shilimkar@ti.com>,
	"Varadarajan, Charulatha" <charu@ti.com>
Subject: Re: [PATCH 0/2] OMAP: GPIO: cleanup: first pass at ifdef removal
Date: Thu, 21 Apr 2011 08:12:52 -0700	[thread overview]
Message-ID: <8739lb4ozv.fsf@ti.com> (raw)
In-Reply-To: <5A47E75E594F054BAF48C5E4FC4B92AB037AD272CB@dbde02.ent.ti.com> (Tarun Kanti DebBarma's message of "Thu, 21 Apr 2011 14:02:26 +0530")

Hi Tarun,

"DebBarma, Tarun Kanti" <tarun.kanti@ti.com> writes:

> [...]
>> 
>> 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.
> Tested following on OMAP2420, OMAP2430, OMAP4430:
> -> request/free of gpio lines
> -> configure input/output mode
> -> interrupt configuration
> -> read/write

Thanks for testing!

Kevin

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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-21  0:13 [PATCH 0/2] OMAP: GPIO: cleanup: first pass at ifdef removal Kevin Hilman
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 [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=8739lb4ozv.fsf@ti.com \
    --to=khilman@ti.com \
    --cc=charu@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=santosh.shilimkar@ti.com \
    --cc=tarun.kanti@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