From: Rajendra Nayak <rnayak@ti.com>
To: linux-omap@vger.kernel.org
Cc: Rajendra Nayak <rnayak@ti.com>
Subject: [PATCH 1/5] OMAP4 clock: Support clk_set_parent
Date: Tue, 11 May 2010 12:57:06 +0530 [thread overview]
Message-ID: <1273562830-9758-2-git-send-email-rnayak@ti.com> (raw)
In-Reply-To: <1273562830-9758-1-git-send-email-rnayak@ti.com>
Remove the hack put in place while clock framework
was still not in place for OMAP4.
Signed-off-by: Rajendra Nayak <rnayak@ti.com>
---
arch/arm/plat-omap/clock.c | 3 ---
1 files changed, 0 insertions(+), 3 deletions(-)
diff --git a/arch/arm/plat-omap/clock.c b/arch/arm/plat-omap/clock.c
index 5261a09..701e4ea 100644
--- a/arch/arm/plat-omap/clock.c
+++ b/arch/arm/plat-omap/clock.c
@@ -140,9 +140,6 @@ int clk_set_parent(struct clk *clk, struct clk *parent)
unsigned long flags;
int ret = -EINVAL;
- if (cpu_is_omap44xx())
- /* OMAP4 clk framework not supported yet */
- return 0;
if (clk == NULL || IS_ERR(clk) || parent == NULL || IS_ERR(parent))
return ret;
--
1.7.0.rc1.33.g07cf0f
next prev parent reply other threads:[~2010-05-11 7:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-11 7:27 [PATCH 0/5] OMAP4: power framework fixes Rajendra Nayak
2010-05-11 7:27 ` Rajendra Nayak [this message]
2010-05-11 7:27 ` [PATCH 2/5] OMAP: timers: Fix clock source names for OMAP4 Rajendra Nayak
2010-05-11 7:27 ` [PATCH 3/5] OMAP4 powerdomain: Fix pwrsts flags for ALWAYS ON domains Rajendra Nayak
2010-05-11 7:27 ` [PATCH 4/5] OMAP4 clockdomain: Fix omap2_clkdm_clk_enable/disable api for 44xx Rajendra Nayak
2010-05-11 7:27 ` [PATCH 5/5] OMAP4 powerdomain: Support LOWPOWERSTATECHANGE for powerdomains Rajendra Nayak
2010-05-11 15:00 ` [PATCH 2/5] OMAP: timers: Fix clock source names for OMAP4 Kevin Hilman
2010-05-19 2:20 ` [PATCH 0/5] OMAP4: power framework fixes 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=1273562830-9758-2-git-send-email-rnayak@ti.com \
--to=rnayak@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.