From: Paul Walmsley <paul@pwsan.com>
To: linux-omap-open-source@linux.omap.com, linux-omap@vger.kernel.org
Subject: [PATCH 0/3] 24xx clock fixes: DSP, 54MHz APLL
Date: Mon, 03 Dec 2007 16:24:26 -0700 [thread overview]
Message-ID: <20071203232426.775904267@pwsan.com> (raw)
Hello,
these patches clean up the structure of the DSP clocks on the OMAP24xx
platforms. They remove redundant clocks and rate structures, and fix
the DSP driver code to use the correct clock name on 2430. DSP
i-clock source selection is moved into a separate clock,
dsp_irate_ick, to facilitate some of this consolidation.
Also, in omap2_clk_fixed_enable(), it turns out that we were looking for
the wrong IDLEST bit to test if the 54MHz APLL was locked - fix this.
This series resolves the boot-time clock warnings that appear on
2430SDP:
clock: Could not find parent clock iva2_1_fck in clksel array of
clock iva2_1_ick
omapdsp: could not acquire dsp_ick handle
Clock apll54_ck didn't enable in 100000 tries
Boot-tested on N800 and 2430SDP. Comments welcome.
- Paul
diffstat:
arch/arm/mach-omap2/clock24xx.c | 2
arch/arm/mach-omap2/clock24xx.h | 180 ++++++++++++------------------------
drivers/dsp/dspgateway/dsp_common.c | 8 +
3 files changed, 72 insertions(+), 118 deletions(-)
size:
text data bss dec hex filename
2741640 141712 84116 2967468 2d47ac vmlinux.n800.orig
2741244 141712 84116 2967072 2d4620 vmlinux.n800.patched
next reply other threads:[~2007-12-03 23:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-03 23:24 Paul Walmsley [this message]
2007-12-03 23:24 ` [PATCH 1/3] 2430 clock: remove redundant iva2_1_fck Paul Walmsley
2007-12-03 23:24 ` [PATCH 2/3] 24xx clock: clarify clock structure; correct parent clock Paul Walmsley
2007-12-03 23:24 ` [PATCH 3/3] 24xx clock: Fix 54MHz APLL readiness test Paul Walmsley
2007-12-05 22:39 ` [PATCH 0/3] 24xx clock fixes: DSP, 54MHz APLL 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=20071203232426.775904267@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