From: Paul Walmsley <paul@pwsan.com>
To: linux-omap@vger.kernel.org
Cc: gadiyar@ti.com, k.kooi@student.utwente.nl,
dirk.behme@googlemail.com, igor.stoppa@nokia.com,
r-woodruff2@ti.com, jouni.hogander@nokia.comD
Subject: [PATCH 0/4] OMAP2/3 clock: fix some bugs in omap2_clk_wait_ready()
Date: 26 Jun 2008 07:11:40 -0000 [thread overview]
Message-ID: <20080626070305.16555.96759.stgit@localhost.localdomain> (raw)
This patch series fixes some bugs in omap2_clk_wait_ready(). This function
waits for an OMAP module to become ready after both its functional and
interface clocks are enabled. Not all OMAP modules support this process.
In particular, this series:
- does some minor code cleanup,
- waits for DSS to become available on OMAP3430ES2+,
- waits for SSI to become available on OMAP3430ES2+,
- and adds a test for the OMAP2 portion of the code to verify that the
clocks it tests for are in the CORE powerdomain.
These patches are possible due to the efforts of several people; credits
are listed in the individual patch descriptions.
Boot-tested on 3430SDP ES2 and 2430SDP.
- Paul
---
size:
text data bss dec hex filename
3391246 156920 107144 3655310 37c68e vmlinux.3430sdp.orig
3391374 156920 107144 3655438 37c70e vmlinux.3430sdp.fixed
arch/arm/mach-omap2/clock.c | 79 ++++++++++++++++++++++++++-------
arch/arm/mach-omap2/cm-regbits-34xx.h | 7 ++-
2 files changed, 67 insertions(+), 19 deletions(-)
next reply other threads:[~2008-06-26 7:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-26 7:11 Paul Walmsley [this message]
2008-06-26 7:09 ` [PATCH 1/4] OMAP2/3 clock: clean up omap2_clk_wait_ready() Paul Walmsley
2008-06-26 7:09 ` [PATCH 2/4] OMAP3 clock: fix omap2_clk_wait_ready() for OMAP3430ES2+ DSS Paul Walmsley
2008-06-26 7:09 ` [PATCH 3/4] OMAP3 clock: OMAP3430ES2+ has SSI target idlest bit Paul Walmsley
2008-06-26 7:09 ` [PATCH 4/4] OMAP2 clock: check register address in omap2_clk_wait_ready() Paul Walmsley
2008-06-26 10:33 ` [PATCH 0/4] OMAP2/3 clock: fix some bugs " Pandita, Vikram
2008-06-26 17:13 ` Paul Walmsley
2008-06-26 19:11 ` Felipe Balbi
2008-06-27 5:29 ` Paul Walmsley
2008-07-17 1:33 ` Paul Walmsley
2008-06-26 13:44 ` Tony Lindgren
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=20080626070305.16555.96759.stgit@localhost.localdomain \
--to=paul@pwsan.com \
--cc=dirk.behme@googlemail.com \
--cc=gadiyar@ti.com \
--cc=igor.stoppa@nokia.com \
--cc=jouni.hogander@nokia.comD \
--cc=k.kooi@student.utwente.nl \
--cc=linux-omap@vger.kernel.org \
--cc=r-woodruff2@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