From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: omap clocksource timer selection: dmtimer OR 32K-Sync timer
Date: Fri, 13 Jan 2012 08:50:03 -0800 [thread overview]
Message-ID: <20120113165003.GJ15299@atomide.com> (raw)
In-Reply-To: <CAMQu2gxkBV87YQE7SPmLXh0RZBR+SNHzHE5H-PVjuef+1UZp8Q@mail.gmail.com>
* Shilimkar, Santosh <santosh.shilimkar@ti.com> [120113 06:08]:
> On Fri, Jan 13, 2012 at 2:42 PM, Hiremath, Vaibhav <hvaibhav@ti.com> wrote:
> > On Fri, Jan 13, 2012 at 18:19:24, Shilimkar, Santosh wrote:
> >> > ? ...
> >> > ? };
> >> >
> >> > ? We need to have similar entries in all devices where 32K timer is present.
> >> >
> >> > 2) OR simply add another cpu_is_am33xx() and then fall back to dmtimer?
> >> > ? Just to prove this, everything works here, I modified the code for this
> >> > ? and tested it on both AM335x EVM and AM37xEVM and it works fine for me.
> >> >
> >> >
> >> > Any comments?? OR Better approach? OR anything which I am missing here?
Why don't you just add a new entry to mach-omap2/timer.c using the OMAP_SYS_TIMER
macro?
See for example the omap3_secure timer set up. That should allow
specifying the clock source already.
Regards,
Tony
next prev parent reply other threads:[~2012-01-13 16:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 12:21 omap clocksource timer selection: dmtimer OR 32K-Sync timer Hiremath, Vaibhav
2012-01-13 12:49 ` Shilimkar, Santosh
2012-01-13 13:42 ` Hiremath, Vaibhav
2012-01-13 14:41 ` Shilimkar, Santosh
2012-01-13 14:57 ` Hiremath, Vaibhav
2012-01-13 16:50 ` Tony Lindgren [this message]
2012-01-16 9:16 ` Hiremath, Vaibhav
2012-01-13 15:19 ` Cousson, Benoit
2012-01-13 15:52 ` Hiremath, Vaibhav
2012-01-13 16:09 ` Cousson, Benoit
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=20120113165003.GJ15299@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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