From: Paul Walmsley <paul@pwsan.com>
To: linux-omap-open-source@linux.omap.com
Subject: [PATCH 1/3] omap2: standardize clock.h enable_reg/enable_bit order
Date: Wed, 02 May 2007 12:33:21 -0600 [thread overview]
Message-ID: <20070502183844.336483674@pwsan.com> (raw)
In-Reply-To: 20070502183320.656693735@pwsan.com
[-- Attachment #1: fix-clock.h-enable-reg-enable-bit-order.patch --]
[-- Type: text/plain, Size: 1726 bytes --]
A few of the clock definitions in mach-omap2/clock.h list the
.enable_bit member before .enable_reg. This fixes those to conform
with the order used in the rest of the file.
Signed-off-by: Paul Walmsley <paul@pwsan.com>
---
arch/arm/mach-omap2/clock.h | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
Index: linux-omap-2.6/arch/arm/mach-omap2/clock.h
===================================================================
--- linux-omap-2.6.orig/arch/arm/mach-omap2/clock.h
+++ linux-omap-2.6/arch/arm/mach-omap2/clock.h
@@ -1318,8 +1318,8 @@ static struct clk mcbsp1_ick = {
.name = "mcbsp1_ick",
.parent = &l4_ck,
.flags = CLOCK_IN_OMAP242X | CLOCK_IN_OMAP243X,
- .enable_bit = 15,
.enable_reg = (void __iomem *)&CM_ICLKEN1_CORE, /* bit16 */
+ .enable_bit = 15,
.recalc = &omap2_followparent_recalc,
};
@@ -1327,8 +1327,8 @@ static struct clk mcbsp1_fck = {
.name = "mcbsp1_fck",
.parent = &func_96m_ck,
.flags = CLOCK_IN_OMAP242X | CLOCK_IN_OMAP243X,
- .enable_bit = 15,
.enable_reg = (void __iomem *)&CM_FCLKEN1_CORE,
+ .enable_bit = 15,
.recalc = &omap2_followparent_recalc,
};
@@ -1336,8 +1336,8 @@ static struct clk mcbsp2_ick = {
.name = "mcbsp2_ick",
.parent = &l4_ck,
.flags = CLOCK_IN_OMAP242X | CLOCK_IN_OMAP243X,
- .enable_bit = 16,
.enable_reg = (void __iomem *)&CM_ICLKEN1_CORE,
+ .enable_bit = 16,
.recalc = &omap2_followparent_recalc,
};
@@ -1345,8 +1345,8 @@ static struct clk mcbsp2_fck = {
.name = "mcbsp2_fck",
.parent = &func_96m_ck,
.flags = CLOCK_IN_OMAP242X | CLOCK_IN_OMAP243X,
- .enable_bit = 16,
.enable_reg = (void __iomem *)&CM_FCLKEN1_CORE,
+ .enable_bit = 16,
.recalc = &omap2_followparent_recalc,
};
--
next prev parent reply other threads:[~2007-05-02 18:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-02 18:33 [PATCH 0/3] omap2: trivial cleanup patches Paul Walmsley
2007-05-02 18:33 ` Paul Walmsley [this message]
2007-05-02 18:33 ` [PATCH 2/3] omap2: fix clock.h rate_offset whitespace Paul Walmsley
2007-05-02 18:33 ` [PATCH 3/3] omap2: merge CONTROL_STATUS defines Paul Walmsley
2007-05-03 17:08 ` [PATCH 0/3] omap2: trivial 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=20070502183844.336483674@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