From: Kevin Hilman <khilman@deeprootsystems.com>
To: Felipe Balbi <felipe.balbi@nokia.com>
Cc: Tony Lindgren <tony@atomide.com>,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>
Subject: Re: [RFC/PATCH 2/3] arm: omap1: remove dead code from timer32k.c
Date: Tue, 06 Apr 2010 14:30:56 -0700 [thread overview]
Message-ID: <87sk78mfov.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1270033995-12516-3-git-send-email-felipe.balbi@nokia.com> (Felipe Balbi's message of "Wed\, 31 Mar 2010 14\:13\:14 +0300")
Felipe Balbi <felipe.balbi@nokia.com> writes:
> Trivial patch, no functional changes
>
> Signed-off-by: Felipe Balbi <felipe.balbi@nokia.com>
Acked-by: Kevin Hilman <khilman@deeprootsystems.com>
> ---
> arch/arm/mach-omap1/timer32k.c | 15 ---------------
> 1 files changed, 0 insertions(+), 15 deletions(-)
>
> diff --git a/arch/arm/mach-omap1/timer32k.c b/arch/arm/mach-omap1/timer32k.c
> index 9ad1185..20cfbcc 100644
> --- a/arch/arm/mach-omap1/timer32k.c
> +++ b/arch/arm/mach-omap1/timer32k.c
> @@ -68,12 +68,6 @@ struct sys_timer omap_timer;
> * ---------------------------------------------------------------------------
> */
>
> -#if defined(CONFIG_ARCH_OMAP16XX)
> -#define TIMER_32K_SYNCHRONIZED 0xfffbc410
> -#else
> -#error OMAP 32KHz timer does not currently work on 15XX!
> -#endif
> -
> /* 16xx specific defines */
> #define OMAP1_32K_TIMER_BASE 0xfffb9000
> #define OMAP1_32K_TIMER_CR 0x08
> @@ -150,15 +144,6 @@ static struct clock_event_device clockevent_32k_timer = {
> .set_mode = omap_32k_timer_set_mode,
> };
>
> -/*
> - * The 32KHz synchronized timer is an additional timer on 16xx.
> - * It is always running.
> - */
> -static inline unsigned long omap_32k_sync_timer_read(void)
> -{
> - return omap_readl(TIMER_32K_SYNCHRONIZED);
> -}
> -
> static irqreturn_t omap_32k_timer_interrupt(int irq, void *dev_id)
> {
> struct clock_event_device *evt = &clockevent_32k_timer;
> --
> 1.7.0.rc0.33.g7c3932
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-04-06 21:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 11:13 [RFC/PATCH 0/3] 32k timer patches Felipe Balbi
2010-03-31 11:13 ` [RFC/PATCH 1/3] omap: fix clocksource_32k to start from zero Felipe Balbi
2010-03-31 11:13 ` [RFC/PATCH 2/3] arm: omap1: remove dead code from timer32k.c Felipe Balbi
2010-04-06 21:30 ` Kevin Hilman [this message]
2010-03-31 11:13 ` [RFC/PATCH 3/3] arm: omap1/2/3/4: convert clocksource to a platform_driver Felipe Balbi
2010-04-06 21:37 ` Kevin Hilman
2010-04-07 7:21 ` Felipe Balbi
2010-04-07 9:57 ` [PATCH 1/3] omap: fix clocksource_32k to start from zero felipe.balbi
2010-04-07 10:02 ` Felipe Balbi
2010-04-22 23:49 ` [APPLIED] " Tony Lindgren
2010-04-07 9:57 ` [PATCH 2/3] arm: omap1: remove dead code from timer32k.c felipe.balbi
2010-04-22 23:49 ` [APPLIED] " Tony Lindgren
2010-04-07 9:57 ` [PATCH 3/3] arm: omap1/2/3/4: convert 32k-sync driver to a platform_driver felipe.balbi
2010-04-07 16:08 ` Kevin Hilman
2010-04-07 17:34 ` Felipe Balbi
2010-06-11 15:24 ` Shilimkar, Santosh
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=87sk78mfov.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=felipe.balbi@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).