From: Paul Walmsley <paul@pwsan.com>
To: linux-arm-kernel@lists.arm.linux.org.uk, linux-kernel@vger.kernel.org
Cc: linux-omap@vger.kernel.org
Subject: [PATCH F 00/12] OMAP clock, F of F: more clock cleanup
Date: Wed, 28 Jan 2009 12:34:56 -0700 [thread overview]
Message-ID: <20090128193326.2396.9437.stgit@localhost.localdomain> (raw)
This series is the sixth of six to bring the mainline kernel OMAP
clock code up-to-date with the linux-omap tree. This series fixes
several bugs and cleans up some of the clock code.
Some patches have been "compressed" together, as requested by rmk.
Original commit IDs are in the patch descriptions.
Compile-tested on OSK5912 (OMAP1), H4 and 2430SDP (OMAP2), and
BeagleBoard (OMAP3). Boot-tested on 2430SDP and BeagleBoard.
Applies on top of series E, posted earlier.
- Paul
---
Paul Walmsley (12):
OMAP2/3 McBSP: add temporary clockdomain fix for McBSP virtual clocks
OMAP2/3 clock: don't tinker with hardirqs when they are supposed to be disabled
OMAP2/3 clock: omap2_clk_enable(): fix logic
OMAP2/3 clock: omap2_clk_enable(): fix usecount decrement bug
OMAP2/3 clock: omap2_clk_enable(): fix bugs in clockdomain handling
OMAP2/3 clock: omap2_clk_enable(): refactor usecount check
OMAP2/3 clock: every clock must have a clkdm
OMAP clock: add OMAP chip family-specific clk_register() option
OMAP clock: drop clk_get_usecount()
OMAP2/3 clock: convert remaining MPU barriers into OCP barriers
OMAP2xxx clock: consolidate DELAYED_APP clock commits; fix barrier
OMAP2/3 clock: don't use a barrier after clk_disable()
arch/arm/mach-omap2/clock.c | 102 +++++++++++++++++++------------
arch/arm/mach-omap2/clock.h | 1
arch/arm/mach-omap2/clock24xx.c | 15 +----
arch/arm/mach-omap2/clock34xx.c | 7 +-
arch/arm/mach-omap2/clockdomains.h | 2 -
arch/arm/mach-omap2/mcbsp.c | 5 ++
arch/arm/plat-omap/clock.c | 27 +++-----
arch/arm/plat-omap/include/mach/clock.h | 2 -
8 files changed, 85 insertions(+), 76 deletions(-)
text data bss dec hex filename
3241435 165504 100880 3507819 35866b vmlinux.beagle.orig
3241418 165504 100880 3507802 35865a vmlinux.beagle
next reply other threads:[~2009-01-28 20:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-28 19:34 Paul Walmsley [this message]
2009-01-28 19:35 ` [PATCH F 01/12] OMAP2/3 clock: don't use a barrier after clk_disable() Paul Walmsley
2009-01-28 19:35 ` [PATCH F 02/12] OMAP2xxx clock: consolidate DELAYED_APP clock commits; fix barrier Paul Walmsley
2009-01-28 19:35 ` [PATCH F 03/12] OMAP2/3 clock: convert remaining MPU barriers into OCP barriers Paul Walmsley
2009-01-28 19:35 ` [PATCH F 04/12] OMAP clock: drop clk_get_usecount() Paul Walmsley
2009-01-28 19:35 ` [PATCH F 05/12] OMAP clock: add OMAP chip family-specific clk_register() option Paul Walmsley
2009-01-28 19:35 ` [PATCH F 06/12] OMAP2/3 clock: every clock must have a clkdm Paul Walmsley
2009-01-31 14:08 ` Russell King - ARM Linux
2009-02-03 9:27 ` Paul Walmsley
2009-02-03 14:20 ` Woodruff, Richard
2009-02-05 9:03 ` Paul Walmsley
2009-01-28 19:35 ` [PATCH F 07/12] OMAP2/3 clock: omap2_clk_enable(): refactor usecount check Paul Walmsley
2009-01-28 19:35 ` [PATCH F 08/12] OMAP2/3 clock: omap2_clk_enable(): fix bugs in clockdomain handling Paul Walmsley
2009-01-28 19:35 ` [PATCH F 09/12] OMAP2/3 clock: omap2_clk_enable(): fix usecount decrement bug Paul Walmsley
2009-01-28 19:35 ` [PATCH F 10/12] OMAP2/3 clock: omap2_clk_enable(): fix logic Paul Walmsley
2009-01-31 10:58 ` Russell King - ARM Linux
2009-02-02 8:01 ` Paul Walmsley
2009-01-28 19:35 ` [PATCH F 11/12] OMAP2/3 clock: don't tinker with hardirqs when they are supposed to be disabled Paul Walmsley
2009-01-28 19:35 ` [PATCH F 12/12] OMAP2/3 McBSP: add temporary clockdomain fix for McBSP virtual clocks Paul Walmsley
2009-01-31 11:42 ` Russell King - ARM Linux
2009-02-02 8:09 ` Paul Walmsley
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=20090128193326.2396.9437.stgit@localhost.localdomain \
--to=paul@pwsan.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.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