From: Kevin Hilman <khilman@deeprootsystems.com>
To: Tarun Kanti DebBarma <tarun.kanti@ti.com>
Cc: linux-omap@vger.kernel.org, Thara Gopinath <thara@ti.com>,
Partha Basak <p-basak2@ti.com>, Rajendra Nayak <rnayak@ti.com>,
Paul Walmsley <paul@pwsan.com>, Tony Lindgren <tony@atomide.com>
Subject: Re: [PATCHv2 6/13] dmtimer: hwmod: OMAP2PLUS: device registration
Date: Mon, 23 Aug 2010 17:11:00 -0700 [thread overview]
Message-ID: <87tymkq38r.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1281800238-15135-1-git-send-email-tarun.kanti@ti.com> (Tarun Kanti DebBarma's message of "Sat, 14 Aug 2010 21:07:18 +0530")
Tarun Kanti DebBarma <tarun.kanti@ti.com> writes:
> +/**
> +* omap2_dm_timer_early_init - top level early timer initialization
> +* called in the last part of omap2_init_common_hw
> +*
> +* uses dedicated hwmod api to parse through hwmod database for
> +* given class name and then build and register the timer device.
> +* at the end driver is registered and early probe initiated.
> +**/
> +void __init omap2_dm_timer_early_init(void)
> +{
> + omap_hwmod_for_each_by_class("timer_1ms",
> + omap_dm_timer_early_init, NULL);
> + omap2_dm_timer_setup();
> + early_platform_driver_register_all("earlytimer");
> + early_platform_driver_probe("earlytimer", early_timer_count + 1, 0);
> +}
It's not clear (or documented) why on the 1ms timers should be the only
earlydevices.
For example, GPT12 is used as the system timer on Beagle due to a board
bug in early revs of the board. That will no longer function with this
approach.
Kevin
next prev parent reply other threads:[~2010-08-24 0:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-14 15:37 [PATCHv2 6/13] dmtimer: hwmod: OMAP2PLUS: device registration Tarun Kanti DebBarma
2010-08-24 0:06 ` Kevin Hilman
2010-09-01 10:11 ` DebBarma, Tarun Kanti
2010-09-01 15:29 ` Kevin Hilman
2010-09-02 12:32 ` DebBarma, Tarun Kanti
2010-08-24 0:11 ` Kevin Hilman [this message]
2010-09-01 9:20 ` DebBarma, Tarun Kanti
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=87tymkq38r.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=p-basak2@ti.com \
--cc=paul@pwsan.com \
--cc=rnayak@ti.com \
--cc=tarun.kanti@ti.com \
--cc=thara@ti.com \
--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).