From: "Cousson, Benoit" <b-cousson@ti.com>
To: Felipe Balbi <balbi@ti.com>
Cc: Tony Lindgren <tony@atomide.com>,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 0/5] 32k sync timer meets hwmod
Date: Wed, 20 Oct 2010 23:29:42 +0200 [thread overview]
Message-ID: <4CBF5F46.4030609@ti.com> (raw)
In-Reply-To: <1287480136-2046-1-git-send-email-balbi@ti.com>
Hi Felipe,
Just one minor comment about the subjects.
On 10/19/2010 11:22 AM, Felipe Balbi wrote:
> Hi all,
>
> Converted 32k-sync timer to platform_driver
> and now using pm_runtime and hwmod.
>
> Tested on 3430 by me and 4430 by Tarun
>
> If someone could test on 2430 and 2420, I would
> be really glad.
>
> Felipe Balbi (5):
> arm: omap1/2/3/4: convert 32k-sync driver to a platform_driver
> arm: omap: counter-32k: convert to pm_runtime API
> clocksource: move omap 32k timer to drivers/clocksource
> arm: omap: introduce 32k timer hwmod for omap2/3/4
> arm: omap: 32k: move to omap_device_build
32k-sync, counter-32k, 32k timer, and then 32k... That's a lot of
different names for that IP :)
You should maybe stick to counter-32k and add a comment saying that the
synctimer32k name was so bad, that we renamed it counter-32k.
Thanks,
Benoit
>
> arch/arm/mach-omap1/devices.c | 24 +++
> arch/arm/mach-omap2/clock2420_data.c | 2 +-
> arch/arm/mach-omap2/clock2430_data.c | 2 +-
> arch/arm/mach-omap2/clock3xxx_data.c | 2 +-
> arch/arm/mach-omap2/devices.c | 36 +++++
> arch/arm/mach-omap2/omap_hwmod_2420_data.c | 52 ++++++
> arch/arm/mach-omap2/omap_hwmod_2430_data.c | 52 ++++++
> arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 51 ++++++
> arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 61 ++++++++
> arch/arm/plat-omap/Makefile | 2 +-
> arch/arm/plat-omap/counter_32k.c | 183 ----------------------
> drivers/clocksource/Makefile | 1 +
> drivers/clocksource/omap-32k.c | 231 ++++++++++++++++++++++++++++
> 13 files changed, 512 insertions(+), 187 deletions(-)
> delete mode 100644 arch/arm/plat-omap/counter_32k.c
> create mode 100644 drivers/clocksource/omap-32k.c
>
next prev parent reply other threads:[~2010-10-20 21:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 9:22 [PATCH 0/5] 32k sync timer meets hwmod Felipe Balbi
2010-10-19 9:22 ` [PATCH 1/5] arm: omap1/2/3/4: convert 32k-sync driver to a platform_driver Felipe Balbi
2010-10-19 9:22 ` [PATCH 2/5] arm: omap: counter-32k: convert to pm_runtime API Felipe Balbi
2010-10-21 17:46 ` Kevin Hilman
2010-10-21 19:06 ` Felipe Balbi
2010-10-21 20:17 ` Kevin Hilman
2010-10-22 6:31 ` Felipe Balbi
2010-10-19 9:22 ` [PATCH 3/5] clocksource: move omap 32k timer to drivers/clocksource Felipe Balbi
2010-10-19 9:22 ` [PATCH 4/5] arm: omap: introduce 32k timer hwmod for omap2/3/4 Felipe Balbi
2010-10-20 21:32 ` Cousson, Benoit
2010-10-21 5:30 ` Felipe Balbi
2010-10-21 17:57 ` Kevin Hilman
2010-10-21 19:08 ` Felipe Balbi
2010-10-21 20:20 ` Kevin Hilman
2010-10-21 20:29 ` Kevin Hilman
2010-10-19 9:22 ` [PATCH 5/5] arm: omap: 32k: move to omap_device_build Felipe Balbi
2010-10-19 9:23 ` [PATCH 0/5] 32k sync timer meets hwmod Felipe Balbi
2010-10-20 21:29 ` Cousson, Benoit [this message]
2010-10-21 5:04 ` DebBarma, Tarun Kanti
2010-10-21 18:00 ` Kevin Hilman
2010-10-21 19:09 ` Felipe Balbi
2010-10-22 19:01 ` green
2010-10-25 7:45 ` Felipe Balbi
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=4CBF5F46.4030609@ti.com \
--to=b-cousson@ti.com \
--cc=balbi@ti.com \
--cc=linux-omap@vger.kernel.org \
--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 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.