From: Tony Lindgren <tony@atomide.com>
To: "Premi, Sanjeev" <premi@ti.com>
Cc: Thomas Weber <weber@corscience.de>,
Gregoire Gentil <gregoire@gentil.com>,
"Bhandiwad, Hrishikesh" <hrishikesh.b@ti.com>,
Jason Lam <lzg@ema-tech.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCHv2] omap3: beagle: Use GPTIMER1 for clockevents
Date: Mon, 27 Jun 2011 05:31:40 -0700 [thread overview]
Message-ID: <20110627123140.GP23145@atomide.com> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB593024D7933C0@dbde02.ent.ti.com>
* Premi, Sanjeev <premi@ti.com> [110627 05:08]:
> > From: Tony Lindgren [mailto:tony@atomide.com]
> >
> > I don't think omap3_beagle_init_rev is even called when
> > the timer is set?
>
> [sp] I verified the patch based on the print indicating that
> GPTIMER1 being used as clockevent source.
> http://marc.info/?l=linux-omap&m=130893319726456&w=2
I suspect the test always fails though, so it probably never
gets set to gptimer12 on any board :)
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2] omap3: beagle: Use GPTIMER1 for clockevents
Date: Mon, 27 Jun 2011 05:31:40 -0700 [thread overview]
Message-ID: <20110627123140.GP23145@atomide.com> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB593024D7933C0@dbde02.ent.ti.com>
* Premi, Sanjeev <premi@ti.com> [110627 05:08]:
> > From: Tony Lindgren [mailto:tony at atomide.com]
> >
> > I don't think omap3_beagle_init_rev is even called when
> > the timer is set?
>
> [sp] I verified the patch based on the print indicating that
> GPTIMER1 being used as clockevent source.
> http://marc.info/?l=linux-omap&m=130893319726456&w=2
I suspect the test always fails though, so it probably never
gets set to gptimer12 on any board :)
Tony
next prev parent reply other threads:[~2011-06-27 12:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 10:36 [PATCHv2] omap3: beagle: Use GPTIMER1 for clockevents Sanjeev Premi
2011-06-27 10:36 ` Sanjeev Premi
2011-06-27 11:15 ` Tony Lindgren
2011-06-27 11:15 ` Tony Lindgren
2011-06-27 12:12 ` Premi, Sanjeev
2011-06-27 12:12 ` Premi, Sanjeev
2011-06-27 12:31 ` Tony Lindgren [this message]
2011-06-27 12:31 ` Tony Lindgren
2011-06-27 13:28 ` Premi, Sanjeev
2011-06-27 13:28 ` Premi, Sanjeev
2011-06-27 18:00 ` Tony Lindgren
2011-06-27 18:00 ` Tony Lindgren
2011-06-27 19:04 ` Kevin Hilman
2011-06-27 19:04 ` Kevin Hilman
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=20110627123140.GP23145@atomide.com \
--to=tony@atomide.com \
--cc=gregoire@gentil.com \
--cc=hrishikesh.b@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=lzg@ema-tech.com \
--cc=premi@ti.com \
--cc=weber@corscience.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 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.