From: Paul Walmsley <paul@pwsan.com>
To: linux-omap@vger.kernel.org
Subject: [PATCH v2 0/3] OMAP2/3 clock: fix module IDLEST code for unusual devs
Date: Thu, 25 Jun 2009 17:38:21 -0600 [thread overview]
Message-ID: <20090625233647.19686.87614.stgit@localhost.localdomain> (raw)
Hello,
After Linux enables an OMAP device's clocks, it must wait for the
device to leave the 'idle' state, or register accesses may result in
an interconnect error and subsequent system crash. Code to do this is
currently in the OMAP clock code, but is overgeneralized, and will not
work correctly for several exception cases - one on 2430, and four on
OMAP3.
This series fixes these bugs by modularizing omap2_clk_wait_ready(),
allowing custom CM_IDLEST register and bit shift data to be supplied
on a per-clock basis, if necessary. (This was originally fixed in the
linux-omap kernel during 2.6.29 in a slightly different manner.)
In the medium term, the module wait code will be moved to omap_hwmod or a
similar OMAP device layer.
Tested on BeagleBoard rev C2 (OMAP3530 ES3); compile-tested with the
N800 defconfig.
This second version fills in the clock.c documentation and removes one
of the custom find_idlest functions (since DSS and USBHOST use the same
target IDLEST shift).
- Paul
---
size:
text data bss dec hex filename
3405015 191408 103632 3700055 387557 vmlinux.beagle.orig
3405475 192144 103632 3701251 387a03 vmlinux.beagle
Paul Walmsley (3):
OMAP3 clock: correct module IDLEST bits: SSI; DSS; USBHOST; HSOTGUSB
OMAP2 clock: 2430 I2CHS uses non-standard CM_IDLEST register
OMAP2/3 clock: split, rename omap2_wait_clock_ready()
arch/arm/mach-omap2/clock.c | 156 ++++++++++++++++---------------
arch/arm/mach-omap2/clock.h | 6 +
arch/arm/mach-omap2/clock24xx.c | 37 +++++++
arch/arm/mach-omap2/clock24xx.h | 4 -
arch/arm/mach-omap2/clock34xx.c | 118 ++++++++++++++++++++++-
arch/arm/mach-omap2/clock34xx.h | 85 +++++++++++++++--
arch/arm/mach-omap2/prcm.c | 43 +++++++++
arch/arm/plat-omap/include/mach/clock.h | 2
arch/arm/plat-omap/include/mach/prcm.h | 1
9 files changed, 353 insertions(+), 99 deletions(-)
next reply other threads:[~2009-06-25 23:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-25 23:38 Paul Walmsley [this message]
2009-06-25 23:38 ` [PATCH v2 1/3] OMAP2/3 clock: split, rename omap2_wait_clock_ready() Paul Walmsley
2009-06-25 23:38 ` [PATCH v2 2/3] OMAP2 clock: 2430 I2CHS uses non-standard CM_IDLEST register Paul Walmsley
2009-06-25 23:38 ` [PATCH v2 3/3] OMAP3 clock: correct module IDLEST bits: SSI; DSS; USBHOST; HSOTGUSB 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=20090625233647.19686.87614.stgit@localhost.localdomain \
--to=paul@pwsan.com \
--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