From: John Stultz <john.stultz@linaro.org>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: John Stultz <john.stultz@linaro.org>,
Colin Cross <ccross@android.com>,
Thomas Gleixner <tglx@linutronix.de>,
Greg KH <gregkh@linuxfoundation.org>,
Android Kernel Team <kernel-team@android.com>
Subject: [PATCH 0/4] Android Alarm Driver Cleanups (for staging-next/3.5)
Date: Fri, 20 Apr 2012 12:31:43 -0700 [thread overview]
Message-ID: <1334950307-403-1-git-send-email-john.stultz@linaro.org> (raw)
This patch-set moves the Android alarm driver in staging to use
the upstreamed CLOCK_BOOTTIME and alarmtimer interfaces, allowing
us to greatly shrink the alarm driver.
The Google Android team has been using these patches in its AOSP tree
for a little while without any reported issues.
The only gotcha is that I needed to make one alarmtimer interface
non-static in order to support the android alarm driver. This sort
of is a grey area for the staging tree, but I'm the author of the
upstreamed alarmtimer code, and Thomas (cc'ed) had no objection
to this patch going in via the staging tree, instead of -tip so
this should be ok (and much simpler then dealing with
cross-maintainer dependencies).
Greg: Would you mind applying this set to staging-next for 3.5?
thanks
-john
CC: Colin Cross <ccross@android.com>
CC: Thomas Gleixner <tglx@linutronix.de>
CC: Greg KH <gregkh@linuxfoundation.org>
CC: Android Kernel Team <kernel-team@android.com>
John Stultz (4):
android-alarm: Convert ALARM_ELAPSED_REALTIME to use CLOCK_BOOTTIME
alarmtimer: Provide accessor to alarmtimer rtc device
android-alarm: Rework alarm-dev.c to use upstreamed alarmtimers
android-alarm: Remove unused android alarm in-kernel interfaces
drivers/staging/android/Kconfig | 21 +-
drivers/staging/android/Makefile | 1 -
drivers/staging/android/alarm-dev.c | 111 +++++-
drivers/staging/android/alarm.c | 601 -------------------------------
drivers/staging/android/android_alarm.h | 59 ---
include/linux/alarmtimer.h | 3 +
kernel/time/alarmtimer.c | 4 +-
7 files changed, 106 insertions(+), 694 deletions(-)
delete mode 100644 drivers/staging/android/alarm.c
--
1.7.3.2.146.gca209
next reply other threads:[~2012-04-20 19:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-20 19:31 John Stultz [this message]
2012-04-20 19:31 ` [PATCH 1/4] android-alarm: Convert ALARM_ELAPSED_REALTIME to use CLOCK_BOOTTIME John Stultz
2012-04-20 19:31 ` [PATCH 2/4] alarmtimer: Provide accessor to alarmtimer rtc device John Stultz
2012-04-20 19:31 ` [PATCH 3/4] android-alarm: Rework alarm-dev.c to use upstreamed alarmtimers John Stultz
2012-04-20 22:02 ` Greg KH
2012-04-20 19:31 ` [PATCH 4/4] android-alarm: Remove unused android alarm in-kernel interfaces John Stultz
2012-04-20 22:08 ` [PATCH 0/4] Android Alarm Driver Cleanups (for staging-next/3.5) Greg KH
2012-04-20 22:57 ` John Stultz
2012-04-20 23:43 ` Greg KH
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=1334950307-403-1-git-send-email-john.stultz@linaro.org \
--to=john.stultz@linaro.org \
--cc=ccross@android.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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