From: Paul Walmsley <paul@pwsan.com>
To: linux-omap@vger.kernel.org
Cc: linux-omap-open-source@linux.omap.com
Subject: [PATCH 3/4] 3430 clock: Add missing ICR clock
Date: Tue, 04 Dec 2007 02:26:08 -0700 [thread overview]
Message-ID: <20071204092737.064644136@pwsan.com> (raw)
In-Reply-To: 20071204092605.831497615@pwsan.com
[-- Attachment #1: 3430_add_icr_clock.patch --]
[-- Type: text/plain, Size: 1042 bytes --]
Add the 3430 clock for the ICR.
Signed-off-by: Paul Walmsley <paul@pwsan.com>
---
arch/arm/mach-omap2/clock34xx.h | 11 +++++++++++
1 file changed, 11 insertions(+)
Index: linux-omap/arch/arm/mach-omap2/clock34xx.h
===================================================================
--- linux-omap.orig/arch/arm/mach-omap2/clock34xx.h 2007-12-04 01:55:14.000000000 -0700
+++ linux-omap/arch/arm/mach-omap2/clock34xx.h 2007-12-04 01:55:58.000000000 -0700
@@ -1125,6 +1125,16 @@
.recalc = &followparent_recalc,
};
+/* Intersystem Communication Registers - chassis mode only */
+static struct clk icr_ick = {
+ .name = "icr_ick",
+ .parent = &core_l4_ick,
+ .enable_reg = OMAP_CM_REGADDR(CORE_MOD, CM_ICLKEN1),
+ .enable_bit = OMAP3430_EN_ICR_SHIFT,
+ .flags = CLOCK_IN_OMAP343X,
+ .recalc = &followparent_recalc,
+};
+
static struct clk aes2_ick = {
.name = "aes2_ick",
.parent = &core_l4_ick,
@@ -2265,6 +2275,7 @@
&security_l3_ick,
&pka_ick,
&core_l4_ick,
+ &icr_ick,
&aes2_ick,
&sha12_ick,
&des2_ick,
--
next prev parent reply other threads:[~2007-12-04 9:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-04 9:26 [PATCH 0/4] 3430 clock: minor cleanup patches Paul Walmsley
2007-12-04 9:26 ` [PATCH 1/4] 3430 clock: 3430 clock: enable SCM clock at boot Paul Walmsley
2007-12-04 9:26 ` [PATCH 2/4] 3430 clock: 3430 clock: combine div2_rates Paul Walmsley
2007-12-04 9:26 ` Paul Walmsley [this message]
2007-12-04 9:26 ` [PATCH 4/4] 3430 clock: Fix missing enable warnings from various clocks Paul Walmsley
2007-12-05 22:41 ` [PATCH 0/4] 3430 clock: minor cleanup patches 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=20071204092737.064644136@pwsan.com \
--to=paul@pwsan.com \
--cc=linux-omap-open-source@linux.omap.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