From: Joel Fernandes <joelf@ti.com>
To: Tony Lindgren <tony@atomide.com>, Rob Herring <robh@kernel.org>,
Tero Kristo <t-kristo@ti.com>, Nishanth Menon <nm@ti.com>,
Suman Anna <s-anna@ti.com>, Felipe Balbi <balbi@ti.com>
Cc: Linux OMAP List <linux-omap@vger.kernel.org>,
Linux ARM Kernel List <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [RFC 0/5] Clocksource driver for OMAP SoCs
Date: Thu, 13 Mar 2014 15:35:14 -0500 [thread overview]
Message-ID: <1394742919-32163-1-git-send-email-joelf@ti.com> (raw)
Here's an RFC series for clocksource migration of OMAP timers.
This attempt is going to step-by-step attempt to migrate platforms
such that everything is kept working smoothly during migration. Currently
the series introduces a clocksource driver and migrates AM335x platform
to discuss the general idea.
The plan is to move dmtimer to clocksource (infact make a copy for now
so that platforms not migrated still work). Then we add a per-SoC clocksource
registration and select a timer as each of them are initialized by clocksource
(suggested in [1]).
We also add support for a generic timer init function which is called for
every SoC for which support in clocksource driver is available. And, we
call a generic OMAP power up function which is introduced in the mach-omap
layer in this series.
Lastly, we add clock nodes for the system timers, and setup a default-parent
so that the parent clocks are setup correctly. Due to this, the series depends
on Tero's series [2].
Please note- this effort is for system timer support. This is the first basic
step. Converting dmtimer to use any other generic framework is a completely
different topic and should not be discussed in this thread. It is something
that can be done only _after_ the work done in this series is completed, thanks.
[1] https://lkml.org/lkml/2013/11/23/88
[2] http://www.spinics.net/lists/linux-omap/msg103069.html
Joel Fernandes (5):
ARM: dts: am33xx: Add clock nodes for timer1 and timer2
ARM: dts: am33xx: Set parent clock for timer through DT
ARM: OMAP2+: timer: Add clocksource initialization and powerup
support
clocksource: omap-timer: Introduce clocksource driver for OMAP SoCs
ARM: AM33xx: Move to using omap_generic_timer_init for init_time
arch/arm/boot/dts/am33xx.dtsi | 4 +
arch/arm/mach-omap2/board-generic.c | 2 +-
arch/arm/mach-omap2/common.h | 1 +
arch/arm/mach-omap2/timer.c | 28 +
drivers/clocksource/Makefile | 1 +
drivers/clocksource/omap-timer.c | 1157 +++++++++++++++++++++++++++++++++++
drivers/clocksource/omap-timer.h | 422 +++++++++++++
7 files changed, 1614 insertions(+), 1 deletion(-)
create mode 100644 drivers/clocksource/omap-timer.c
create mode 100644 drivers/clocksource/omap-timer.h
--
1.7.9.5
next reply other threads:[~2014-03-13 20:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 20:35 Joel Fernandes [this message]
2014-03-13 20:35 ` [RFC 1/5] ARM: dts: am33xx: Add clock nodes for timer1 and timer2 Joel Fernandes
2014-03-13 20:35 ` [RFC 2/5] ARM: dts: am33xx: Set parent clock for timer through DT Joel Fernandes
2014-03-14 8:08 ` Tero Kristo
2014-03-13 20:35 ` [RFC 3/5] ARM: OMAP2+: timer: Add clocksource initialization and powerup support Joel Fernandes
2014-03-13 21:52 ` Rob Herring
2014-03-13 23:36 ` Joel Fernandes
2014-03-14 8:03 ` Tero Kristo
2014-03-14 21:09 ` Kevin Hilman
2014-03-14 21:16 ` Rob Herring
2014-03-13 20:35 ` [RFC 4/5] clocksource: omap-timer: Introduce clocksource driver for OMAP SoCs Joel Fernandes
2014-03-13 20:48 ` Tony Lindgren
2014-03-13 23:49 ` Joel Fernandes
2014-03-14 15:52 ` Tony Lindgren
2014-03-14 19:32 ` Joel Fernandes
2014-03-14 19:33 ` Joel Fernandes
2014-03-15 0:13 ` Suman Anna
2014-03-15 1:11 ` Joel Fernandes
2014-03-13 20:35 ` [RFC 5/5] ARM: AM33xx: Move to using omap_generic_timer_init for init_time Joel Fernandes
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=1394742919-32163-1-git-send-email-joelf@ti.com \
--to=joelf@ti.com \
--cc=balbi@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=s-anna@ti.com \
--cc=t-kristo@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
all inboxes | Powered by JetHome®