From: Paul Walmsley <paul@pwsan.com>
To: linux-omap-open-source@linux.omap.com
Subject: [PATCH 1/2] 3430 clock: revise SmartReflex clocks
Date: Mon, 12 Nov 2007 03:57:27 -0700 [thread overview]
Message-ID: <20071112110147.779860304@pwsan.com> (raw)
In-Reply-To: 20071112105726.514186925@pwsan.com
[-- Attachment #1: add_sr_clocks.patch --]
[-- Type: text/plain, Size: 1620 bytes --]
The two SmartReflex voltage controllers on OMAP3430 have one
functional clock each. These clocks appear to be independent of each
other. Encode them appropriately, replacing the previous 'sr_alwon_fck'
clock.
Signed-off-by: Paul Walmsley <paul@pwsan.com>
---
arch/arm/mach-omap2/clock34xx.h | 23 ++++++++++++++++++-----
1 file changed, 18 insertions(+), 5 deletions(-)
Index: linux-omap/arch/arm/mach-omap2/clock34xx.h
===================================================================
--- linux-omap.orig/arch/arm/mach-omap2/clock34xx.h 2007-11-08 13:05:40.000000000 -0700
+++ linux-omap/arch/arm/mach-omap2/clock34xx.h 2007-11-08 13:05:47.000000000 -0700
@@ -2003,11 +2003,23 @@
/* SR clocks */
-/* REVISIT: dependent on en_sr1 && en_sr2 - use custom enable/disable? */
-static struct clk sr_alwon_fck = {
- .name = "sr_alwon_fck",
+/* SmartReflex fclk (VDD1) */
+static struct clk sr1_fck = {
+ .name = "sr1_fck",
.parent = &sys_ck,
- .flags = CLOCK_IN_OMAP343X,
+ .enable_reg = OMAP_CM_REGADDR(WKUP_MOD, CM_FCLKEN),
+ .enable_bit = OMAP3430_EN_SR1_SHIFT,
+ .flags = CLOCK_IN_OMAP343X | RATE_PROPAGATES,
+ .recalc = &followparent_recalc,
+};
+
+/* SmartReflex fclk (VDD2) */
+static struct clk sr2_fck = {
+ .name = "sr2_fck",
+ .parent = &sys_ck,
+ .enable_reg = OMAP_CM_REGADDR(WKUP_MOD, CM_FCLKEN),
+ .enable_bit = OMAP3430_EN_SR2_SHIFT,
+ .flags = CLOCK_IN_OMAP343X | RATE_PROPAGATES,
.recalc = &followparent_recalc,
};
@@ -2204,7 +2216,8 @@
&mcbsp2_fck,
&mcbsp3_fck,
&mcbsp4_fck,
- &sr_alwon_fck,
+ &sr1_fck,
+ &sr2_fck,
&sr_l4_ick,
&secure_32k_fck,
&gpt12_fck,
--
next prev parent reply other threads:[~2007-11-12 10:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-12 10:57 [PATCH 0/2] 3430 clock: REVISED: Add SmartReflex, emulation, trace clocks Paul Walmsley
2007-11-12 10:57 ` Paul Walmsley [this message]
2007-11-12 10:57 ` [PATCH 2/2] 3430 clock: add emulation clocks Paul Walmsley
2007-11-15 22:11 ` [PATCH 0/2] 3430 clock: REVISED: Add SmartReflex, emulation, trace clocks Tony Lindgren
-- strict thread matches above, loose matches on Subject: below --
2007-11-05 8:24 [PATCH 0/2] 3430 clock: " Paul Walmsley
2007-11-05 8:24 ` [PATCH 1/2] 3430 clock: revise SmartReflex clocks 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=20071112110147.779860304@pwsan.com \
--to=paul@pwsan.com \
--cc=linux-omap-open-source@linux.omap.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