From: Tony Lindgren <tony@atomide.com>
To: "DebBarma, Tarun Kanti" <tarun.kanti@ti.com>
Cc: "Hilman, Kevin" <khilman@ti.com>,
"Shilimkar, Santosh" <santosh.shilimkar@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Gopinath, Thara" <thara@ti.com>
Subject: Re: [PATCH v12 4/9] OMAP2+: dmtimer: convert to platform devices
Date: Tue, 29 Mar 2011 10:13:45 -0700 [thread overview]
Message-ID: <20110329171345.GH4016@atomide.com> (raw)
In-Reply-To: <20110325155549.GZ2811@atomide.com>
* Tony Lindgren <tony@atomide.com> [110325 08:54]:
> * DebBarma, Tarun Kanti <tarun.kanti@ti.com> [110324 23:53]:
> > Hi Tony,
> > [...]
> > > Well the dmtimer code can then become just a regular platform_device
> > > based driver, except for clockevent and clocksource on omap2 & 3.
> > Should I re-post the patch series with removal of duplicate initialization
> > Which Kevin pointed out + other relevant comments?
> > Or, wait for your patch series!
>
> Just wait few days please, I should have something available that mostly
> deals with timer-gp.c, so it should not cause too many issues with your
> patches.
FYI, posted some patches in the "omap init_early changes for irq and
timer init" thread, also available in devel-timer branch. Few notes
regarding updating your dmtimer series:
- Add the dmtimer arch_initcall into arch/arm/mach-omap2/timer.c so
we don't end up with yet another timer*.c file there
- Make use of omap_dm_timer_init_one in the dmtimer arch_initcall so
sys_timer initialized struct omap_dm_timer can be picked up
- You can pick the reserved clockevent and clocksource timers based
on the sys_timer_reserved mask and then create proper dev entries
for those too later on during the init
- Now arch/arm/plat-omap/dmtimer.c can become just a driver module
living under drivers somewhere
Other than that, your patches should be pretty easy to rebase.
Regards,
Tony
next prev parent reply other threads:[~2011-03-29 17:13 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 23:45 [PATCH v12 0/9] dmtimer adaptation to platform_driver Tarun Kanti DebBarma
2011-03-08 23:45 ` [PATCH v12 1/9] OMAP2+: dmtimer: add device names to flck nodes Tarun Kanti DebBarma
2011-03-08 23:45 ` [PATCH v12 2/9] OMAP4: hwmod data: add dmtimer version information Tarun Kanti DebBarma
2011-03-08 23:45 ` [PATCH v12 3/9] OMAP1: dmtimer: conversion to platform devices Tarun Kanti DebBarma
2011-03-08 23:45 ` [PATCH v12 4/9] OMAP2+: dmtimer: convert " Tarun Kanti DebBarma
2011-03-09 21:42 ` Tony Lindgren
2011-03-10 15:29 ` DebBarma, Tarun Kanti
2011-03-10 22:52 ` Kevin Hilman
2011-03-11 4:36 ` DebBarma, Tarun Kanti
2011-03-10 23:14 ` Kevin Hilman
2011-03-11 4:20 ` DebBarma, Tarun Kanti
2011-03-11 19:13 ` Tony Lindgren
2011-03-12 0:03 ` Kevin Hilman
2011-03-14 17:12 ` Tony Lindgren
2011-03-17 22:00 ` Kevin Hilman
2011-03-19 0:27 ` Tony Lindgren
2011-03-19 4:34 ` Santosh Shilimkar
2011-03-21 17:07 ` Tony Lindgren
2011-03-21 18:33 ` Kevin Hilman
2011-03-21 19:11 ` Tony Lindgren
2011-03-25 6:55 ` DebBarma, Tarun Kanti
2011-03-25 15:55 ` Tony Lindgren
2011-03-29 17:13 ` Tony Lindgren [this message]
2011-03-29 17:52 ` Tony Lindgren
2011-03-10 23:21 ` Kevin Hilman
2011-03-11 4:13 ` DebBarma, Tarun Kanti
2011-03-08 23:45 ` [PATCH v12 5/9] OMAP: dmtimer: platform driver Tarun Kanti DebBarma
2011-03-08 23:45 ` [PATCH v12 6/9] dmtimer: switch-over to platform device driver Tarun Kanti DebBarma
2011-03-09 22:02 ` Tony Lindgren
2011-03-10 15:27 ` DebBarma, Tarun Kanti
2011-03-10 17:56 ` Tony Lindgren
2011-03-11 5:35 ` DebBarma, Tarun Kanti
2011-03-11 12:45 ` G, Manjunath Kondaiah
2011-03-11 19:15 ` Tony Lindgren
2011-03-12 4:20 ` G, Manjunath Kondaiah
2011-03-11 19:14 ` Tony Lindgren
2011-03-14 6:48 ` DebBarma, Tarun Kanti
2011-03-08 23:45 ` [PATCH v12 7/9] OMAP: dmtimer: pm_runtime support Tarun Kanti DebBarma
2011-03-08 23:45 ` [PATCH v12 8/9] OMAP: dmtimer: add timeout to low-level routines Tarun Kanti DebBarma
2011-03-08 23:45 ` [PATCH v12 9/9] OMAP: dmtimer: use mutex instead of spinlock Tarun Kanti DebBarma
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=20110329171345.GH4016@atomide.com \
--to=tony@atomide.com \
--cc=khilman@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=santosh.shilimkar@ti.com \
--cc=tarun.kanti@ti.com \
--cc=thara@ti.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).