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.com
Subject: [PATCH 3/4] OMAP3 clock: OMAP3430ES2+ has SSI target idlest bit
Date: Thu, 26 Jun 2008 01:09:15 -0600 [thread overview]
Message-ID: <20080626070913.16555.90593.stgit@localhost.localdomain> (raw)
In-Reply-To: <20080626070305.16555.96759.stgit@localhost.localdomain>
On OMAP3430ES2+, SSI has both an initiator standby CM_IDLEST bit, and a
target idle CM_IDLEST bit. This is a departure from previous silicon,
which only had an initiator standby bit.
This means that omap2_clk_wait_ready() needs to wait for the SSI
module to indicate readiness after both SSI interface and functional
clocks are enabled.
Thanks to Igor Stoppa <igor.stoppa@nokia.com>, Richard Woodruff
<r-woodruff2@ti.com>, and Jouni Högander <jouni.hogander@nokia.com> for
help with this portion of the patch.
Signed-off-by: Paul Walmsley <paul@pwsan.com>
---
arch/arm/mach-omap2/clock.c | 59 ++++++++++++++++++++-------------
arch/arm/mach-omap2/cm-regbits-34xx.h | 3 +-
2 files changed, 38 insertions(+), 24 deletions(-)
diff --git a/arch/arm/mach-omap2/clock.c b/arch/arm/mach-omap2/clock.c
index 343477b..59b042f 100644
--- a/arch/arm/mach-omap2/clock.c
+++ b/arch/arm/mach-omap2/clock.c
@@ -246,28 +246,31 @@ static void omap2_clk_wait_ready(struct clk *clk)
}
/* REVISIT: What are the appropriate exclusions for 34XX? */
- if (cpu_is_omap34xx() &&
- prcm_mod == OMAP34XX_CM_REGADDR(OMAP3430_DSS_MOD, 0)) {
+ if (cpu_is_omap34xx()) {
- /* 3430ES1 DSS has no target idlest bits */
- if (is_sil_rev_equal_to(OMAP3430_REV_ES1_0))
+ /* SSI */
+ if (is_sil_rev_equal_to(OMAP3430_REV_ES1_0) &&
+ prcm_mod == OMAP34XX_CM_REGADDR(CORE_MOD, 0) &&
+ (reg & 0x0f) == 0 &&
+ clk->enable_bit == OMAP3430_EN_SSI_SHIFT)
return;
- /*
- * For 3430ES2+ DSS, only wait once (dss1_alwon_fclk,
- * dss_l3_iclk, dss_l4_iclk) are enabled
- */
- if (clk->enable_bit != OMAP3430_EN_DSS1_SHIFT)
- return;
+ /* DSS */
+ if (prcm_mod == OMAP34XX_CM_REGADDR(OMAP3430_DSS_MOD, 0)) {
- }
+ /* 3430ES1 DSS has no target idlest bits */
+ if (is_sil_rev_equal_to(OMAP3430_REV_ES1_0))
+ return;
- /* REVISIT: SSI has a target idlest bit on OMAP3 */
- /* REVISIT: This could accidentally exclude other clocks also */
- if (cpu_is_omap34xx() &&
- prcm_mod == OMAP34XX_CM_REGADDR(CORE_MOD, 0) &&
- clk->enable_bit == OMAP3430_EN_SSI_SHIFT)
- return;
+ /*
+ * For 3430ES2+ DSS, only wait once (dss1_alwon_fclk,
+ * dss_l3_iclk, dss_l4_iclk) are enabled
+ */
+ if (clk->enable_bit != OMAP3430_EN_DSS1_SHIFT)
+ return;
+ }
+
+ }
/* Check if both functional and interface clocks
* are running. */
@@ -276,13 +279,23 @@ static void omap2_clk_wait_ready(struct clk *clk)
return;
/*
- * OMAP3430ES2 DSS target idlest bit is at a different shift than
- * the corresponding {I,F}CLKEN bits
+ * OMAP3430ES2+ has target idlest bits at unusual offsets for
+ * modules with both initiator and target agents
*/
- if (cpu_is_omap34xx() &&
- prcm_mod == OMAP34XX_CM_REGADDR(OMAP3430_DSS_MOD, 0) &&
- clk->enable_bit == OMAP3430_EN_DSS1_SHIFT)
- bit = OMAP3430ES2_ST_DSS_IDLE;
+ if (cpu_is_omap34xx()) {
+
+ /* SSI */
+ if (prcm_mod == OMAP34XX_CM_REGADDR(CORE_MOD, 0) &&
+ (reg & 0x0f) == 0 &&
+ clk->enable_bit == OMAP3430_EN_SSI_SHIFT)
+ bit = OMAP3430ES2_ST_SSI_IDLE;
+
+ /* DSS */
+ if (prcm_mod == OMAP34XX_CM_REGADDR(OMAP3430_DSS_MOD, 0) &&
+ clk->enable_bit == OMAP3430_EN_DSS1_SHIFT)
+ bit = OMAP3430ES2_ST_DSS_IDLE;
+
+ }
st_reg = ((other_reg & ~0xf0) | 0x20); /* CM_IDLEST* */
diff --git a/arch/arm/mach-omap2/cm-regbits-34xx.h b/arch/arm/mach-omap2/cm-regbits-34xx.h
index 946c552..971b9ad 100644
--- a/arch/arm/mach-omap2/cm-regbits-34xx.h
+++ b/arch/arm/mach-omap2/cm-regbits-34xx.h
@@ -190,11 +190,12 @@
#define OMAP3430_ST_MSPRO (1 << 23)
#define OMAP3430_ST_HDQ (1 << 22)
#define OMAP3430ES1_ST_FAC (1 << 8)
+#define OMAP3430ES2_ST_SSI_IDLE (1 << 8)
#define OMAP3430ES1_ST_MAILBOXES (1 << 7)
#define OMAP3430_ST_OMAPCTRL (1 << 6)
#define OMAP3430_ST_SDMA (1 << 2)
#define OMAP3430_ST_SDRC (1 << 1)
-#define OMAP3430_ST_SSI (1 << 0)
+#define OMAP3430_ST_SSI_STDBY (1 << 0)
/* CM_IDLEST2_CORE */
#define OMAP3430_ST_PKA (1 << 4)
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent 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 [PATCH 0/4] OMAP2/3 clock: fix some bugs in omap2_clk_wait_ready() Paul Walmsley
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 ` Paul Walmsley [this message]
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=20080626070913.16555.90593.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.com \
--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