All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sanjeev Premi <premi@ti.com>
To: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Cc: Sanjeev Premi <premi@ti.com>, Paul Walmsley <paul@pwsan.com>
Subject: [PATCH] omap3: beagle: Use GPTIMERi 1 for clockevents
Date: Fri, 24 Jun 2011 21:53:45 +0530	[thread overview]
Message-ID: <1308932625-17632-1-git-send-email-premi@ti.com> (raw)

The current selection of the GPTIMER on was result of
a hardware issue in early versions of the Beagleboards
(Ax and B1 thru B4). [1] [2]

Its been long since the hardware issue has been fixed.
This patch uses GPTIMER 1 for all newer board revisions
incl. Beagleboard XM.

 [1] http://thread.gmane.org/gmane.comp.hardware.beagleboard.general/91
 [2] Errata #7 at http://elinux.org/BeagleBoard#Errata

Signed-off-by: Sanjeev Premi <premi@ti.com>
Cc: Paul Walmsley <paul@pwsan.com>
---

  * The patch has been boot tested with Beagleboard-XM.
    Verified that GPTIMER1 is indeed being used.

  * Browsing through the code, it appears that similar
    change could be applied for these boards:
     - devkit8000
     - omap3stalker
     - omap3touchbook
    However, I don't have access to any of these;
    or information on their revisions.
    I can update this patch based on confirmations.

 arch/arm/mach-omap2/board-omap3beagle.c |    5 ++++-
 1 files changed, 4 insertions(+), 1 deletions(-)

diff --git a/arch/arm/mach-omap2/board-omap3beagle.c b/arch/arm/mach-omap2/board-omap3beagle.c
index 4b113b2..edc1596 100644
--- a/arch/arm/mach-omap2/board-omap3beagle.c
+++ b/arch/arm/mach-omap2/board-omap3beagle.c
@@ -509,7 +509,10 @@ static void __init omap3_beagle_init_irq(void)
 {
 	omap_init_irq();
 #ifdef CONFIG_OMAP_32K_TIMER
-	omap2_gp_clockevent_set_gptimer(12);
+	if (omap3_beagle_version == OMAP3BEAGLE_BOARD_AXBX)
+		omap2_gp_clockevent_set_gptimer(12);
+	else
+		omap2_gp_clockevent_set_gptimer(1);
 #endif
 }
 
-- 
1.7.2.2


WARNING: multiple messages have this Message-ID (diff)
From: premi@ti.com (Sanjeev Premi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] omap3: beagle: Use GPTIMERi 1 for clockevents
Date: Fri, 24 Jun 2011 21:53:45 +0530	[thread overview]
Message-ID: <1308932625-17632-1-git-send-email-premi@ti.com> (raw)

The current selection of the GPTIMER on was result of
a hardware issue in early versions of the Beagleboards
(Ax and B1 thru B4). [1] [2]

Its been long since the hardware issue has been fixed.
This patch uses GPTIMER 1 for all newer board revisions
incl. Beagleboard XM.

 [1] http://thread.gmane.org/gmane.comp.hardware.beagleboard.general/91
 [2] Errata #7 at http://elinux.org/BeagleBoard#Errata

Signed-off-by: Sanjeev Premi <premi@ti.com>
Cc: Paul Walmsley <paul@pwsan.com>
---

  * The patch has been boot tested with Beagleboard-XM.
    Verified that GPTIMER1 is indeed being used.

  * Browsing through the code, it appears that similar
    change could be applied for these boards:
     - devkit8000
     - omap3stalker
     - omap3touchbook
    However, I don't have access to any of these;
    or information on their revisions.
    I can update this patch based on confirmations.

 arch/arm/mach-omap2/board-omap3beagle.c |    5 ++++-
 1 files changed, 4 insertions(+), 1 deletions(-)

diff --git a/arch/arm/mach-omap2/board-omap3beagle.c b/arch/arm/mach-omap2/board-omap3beagle.c
index 4b113b2..edc1596 100644
--- a/arch/arm/mach-omap2/board-omap3beagle.c
+++ b/arch/arm/mach-omap2/board-omap3beagle.c
@@ -509,7 +509,10 @@ static void __init omap3_beagle_init_irq(void)
 {
 	omap_init_irq();
 #ifdef CONFIG_OMAP_32K_TIMER
-	omap2_gp_clockevent_set_gptimer(12);
+	if (omap3_beagle_version == OMAP3BEAGLE_BOARD_AXBX)
+		omap2_gp_clockevent_set_gptimer(12);
+	else
+		omap2_gp_clockevent_set_gptimer(1);
 #endif
 }
 
-- 
1.7.2.2

             reply	other threads:[~2011-06-24 16:25 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-24 16:23 Sanjeev Premi [this message]
2011-06-24 16:23 ` [PATCH] omap3: beagle: Use GPTIMERi 1 for clockevents Sanjeev Premi
2011-06-24 16:32 ` Premi, Sanjeev
2011-06-24 16:32   ` Premi, Sanjeev
2011-06-25  8:16 ` Koen Kooi
2011-06-25  8:16   ` Koen Kooi
2011-06-25 18:51   ` Premi, Sanjeev
2011-06-25 18:51     ` Premi, Sanjeev
2011-06-25 20:10     ` Koen Kooi
2011-06-25 20:10       ` Koen Kooi
2011-06-27  4:45       ` Premi, Sanjeev
2011-06-27  4:45         ` Premi, Sanjeev
2011-06-27 12:32       ` Jonathan Cameron
2011-06-27 12:32         ` Jonathan Cameron
2011-06-25 22:47     ` Paul Walmsley
2011-06-25 22:47       ` Paul Walmsley
2011-06-27  4:47       ` Premi, Sanjeev
2011-06-27  4:47         ` Premi, Sanjeev
2011-06-27 10:14       ` Tony Lindgren
2011-06-27 10:14         ` Tony Lindgren
2011-06-27 15:29         ` Paul Walmsley
2011-06-27 15:29           ` Paul Walmsley
2011-06-27 15:40           ` Premi, Sanjeev
2011-06-27 15:40             ` Premi, Sanjeev
2011-06-27 16:55             ` Paul Walmsley
2011-06-27 16:55               ` Paul Walmsley
2011-06-27 18:03               ` Tony Lindgren
2011-06-27 18:03                 ` Tony Lindgren
2011-06-25 22:49 ` Paul Walmsley
2011-06-25 22:49   ` Paul Walmsley

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=1308932625-17632-1-git-send-email-premi@ti.com \
    --to=premi@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.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.