All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@ti.com>
To: Jon Hunter <jon-hunter@ti.com>
Cc: linux-omap <linux-omap@vger.kernel.org>,
	Tony Lindgren <tony@atomide.com>,
	Benoit Cousson <b-cousson@ti.com>
Subject: Re: [PATCH 2/9] ARM: OMAP2+: Remove unused max number of timers definition
Date: Thu, 17 May 2012 13:07:14 -0700	[thread overview]
Message-ID: <87obpmwozx.fsf@ti.com> (raw)
In-Reply-To: <1337124927-19992-1-git-send-email-jon-hunter@ti.com> (Jon Hunter's message of "Tue, 15 May 2012 18:35:27 -0500")

Jon Hunter <jon-hunter@ti.com> writes:

> From: Jon Hunter <jon-hunter@ti.com>
>
> The OMAP2+ timer code has a definition for the maximum number of timers that
> OMAP2+ devices have. This defintion is not used anywhere in the code and
> appears to be left over. Furthermore the definition is not accurate for OMAP4
> devices that only have 11 timers available because the 12th timer is reserved
> as a secure timer. Therefore, remove this definition.

changelog nit: the 12th timer is secure on OMAP3 HS devices also.

Kevin

> Signed-off-by: Jon Hunter <jon-hunter@ti.com>
> ---
>  arch/arm/mach-omap2/timer.c |    3 ---
>  1 files changed, 0 insertions(+), 3 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/timer.c b/arch/arm/mach-omap2/timer.c
> index 840929b..c030dfe 100644
> --- a/arch/arm/mach-omap2/timer.c
> +++ b/arch/arm/mach-omap2/timer.c
> @@ -69,9 +69,6 @@
>  #define OMAP3_SECURE_TIMER	1
>  #endif
>  
> -/* MAX_GPTIMER_ID: number of GPTIMERs on the chip */
> -#define MAX_GPTIMER_ID		12
> -
>  static u32 sys_timer_reserved;
>  
>  /* Clockevent code */

      reply	other threads:[~2012-05-17 20:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-15 23:35 [PATCH 2/9] ARM: OMAP2+: Remove unused max number of timers definition Jon Hunter
2012-05-17 20:07 ` 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=87obpmwozx.fsf@ti.com \
    --to=khilman@ti.com \
    --cc=b-cousson@ti.com \
    --cc=jon-hunter@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.