All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org, linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH 0/3] 24xx clock fixes: DSP, 54MHz APLL
Date: Wed, 5 Dec 2007 14:39:56 -0800	[thread overview]
Message-ID: <20071205223956.GY4105@atomide.com> (raw)
In-Reply-To: <20071203232426.775904267@pwsan.com>

* Paul Walmsley <paul@pwsan.com> [071203 15:30]:
> 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.

Pushing today.

Tony

      parent reply	other threads:[~2007-12-05 22:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-03 23:24 [PATCH 0/3] 24xx clock fixes: DSP, 54MHz APLL Paul Walmsley
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 ` Tony Lindgren [this message]

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=20071205223956.GY4105@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap-open-source@linux.omap.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.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 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.