From: khilman@ti.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v7 REPOST 00/24] gpio/omap: driver cleanup and fixes
Date: Tue, 27 Sep 2011 07:27:19 -0700 [thread overview]
Message-ID: <87vcse3vso.fsf@ti.com> (raw)
In-Reply-To: <1317082460-31706-1-git-send-email-tarun.kanti@ti.com> (Tarun Kanti DebBarma's message of "Tue, 27 Sep 2011 05:43:56 +0530")
Tarun Kanti DebBarma <tarun.kanti@ti.com> writes:
> This series is continuation of cleanup of OMAP GPIO driver and fixes.
> The cleanup include getting rid of cpu_is_* checks wherever possible,
> use of gpio_bank list instead of static array, use of unique platform
> specific value associated data member to OMAP platforms to avoid
> cpu_is_* checks. The series also include PM runtime support.*
>
> Baseline: git://gitorious.org/khilman/linux-omap-pm.git
> Branch: for_3.2/gpio-cleanup
> Commit: 8323374
Is this functionally different than the branch you posted yesterday?
I replied to that saying it does not fix the PER retention problems on
n900, and giving a suggestion of how to test it.
Kevin
prev parent reply other threads:[~2011-09-27 14:27 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 0:13 [PATCH v7 REPOST 00/24] gpio/omap: driver cleanup and fixes Tarun Kanti DebBarma
2011-09-27 0:13 ` [PATCH v7 REPOST 01/24] gpio/omap: remove dependency on gpio_bank_count Tarun Kanti DebBarma
2011-09-27 0:13 ` [PATCH v7 REPOST 02/24] gpio/omap: use flag to identify wakeup domain Tarun Kanti DebBarma
2011-09-27 0:13 ` [PATCH v7 REPOST 03/24] gpio/omap: make gpio_context part of gpio_bank structure Tarun Kanti DebBarma
2011-09-27 0:14 ` [PATCH v7 REPOST 04/24] gpio/omap: fix pwrdm_post_transition call sequence Tarun Kanti DebBarma
2011-09-27 0:14 ` [PATCH v7 REPOST 05/24] gpio/omap: handle save/restore context in GPIO driver Tarun Kanti DebBarma
2011-09-27 0:14 ` [PATCH v7 REPOST 06/24] gpio/omap: make non-wakeup GPIO part of pdata Tarun Kanti DebBarma
2011-09-27 0:14 ` [PATCH v7 REPOST 07/24] gpio/omap: avoid cpu checks during module ena/disable Tarun Kanti DebBarma
2011-09-27 0:14 ` [PATCH v7 REPOST 08/24] gpio/omap: further cleanup using wkup_en register Tarun Kanti DebBarma
2011-09-27 0:14 ` [PATCH v7 REPOST 09/24] gpio/omap: use level/edge detect reg offsets Tarun Kanti DebBarma
2011-09-27 0:14 ` [PATCH v7 REPOST 10/24] gpio/omap: remove hardcoded offsets in context save/restore Tarun Kanti DebBarma
2011-09-27 0:14 ` [PATCH v7 REPOST 11/24] gpio/omap: cleanup set_gpio_triggering function Tarun Kanti DebBarma
2011-09-27 0:14 ` [PATCH v7 REPOST 12/24] gpio/omap: cleanup omap_gpio_mod_init function Tarun Kanti DebBarma
2011-09-27 0:14 ` [PATCH v7 REPOST 13/24] gpio/omap: use pinctrl offset instead of macro Tarun Kanti DebBarma
2011-09-27 0:14 ` [PATCH v7 REPOST 14/24] gpio/omap: remove unnecessary bit-masking for read access Tarun Kanti DebBarma
2011-09-27 0:14 ` [PATCH v7 REPOST 15/24] gpio/omap: remove bank->method & METHOD_* macros Tarun Kanti DebBarma
2011-09-27 0:14 ` [PATCH v7 REPOST 16/24] gpio/omap: fix bankwidth for OMAP7xx MPUIO Tarun Kanti DebBarma
2011-09-27 0:14 ` [PATCH v7 REPOST 17/24] gpio/omap: use pm-runtime framework Tarun Kanti DebBarma
2011-09-27 0:14 ` [PATCH v7 REPOST 18/24] gpio/omap: optimize suspend and resume functions Tarun Kanti DebBarma
2011-09-27 0:14 ` [PATCH v7 REPOST 19/24] gpio/omap: cleanup prepare_for_idle and resume_after_idle Tarun Kanti DebBarma
2011-09-27 0:14 ` [PATCH v7 REPOST 20/24] gpio/omap: remove omap_gpio_save_context overhead Tarun Kanti DebBarma
2011-09-27 0:14 ` [PATCH v7 REPOST 21/24] gpio/omap: save and restore debounce registers Tarun Kanti DebBarma
2011-09-27 0:14 ` [PATCH v7 REPOST 22/24] gpio/omap: enable irq at the end of all configuration in restore Tarun Kanti DebBarma
2011-09-27 0:14 ` [PATCH v7 REPOST 23/24] gpio/omap: restore OE only after setting the output level Tarun Kanti DebBarma
2011-09-27 0:14 ` [PATCH v7 REPOST 24/24] gpio/omap: handle set_dataout reg capable IP on restore Tarun Kanti DebBarma
2011-09-27 14:27 ` 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=87vcse3vso.fsf@ti.com \
--to=khilman@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).