public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Kevin Hilman <khilman@mvista.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH] ARM: OMAP: fix clock table walking for OMAP2 variants
Date: Thu, 21 Jun 2007 05:00:25 -0700	[thread overview]
Message-ID: <20070621120024.GH20283@atomide.com> (raw)
In-Reply-To: <20070614005558.976939568@mvista.com>

* Kevin Hilman <khilman@mvista.com> [070613 18:00]:
> The various places where the clock rate_table is walked are not all
> checking whether the clock actually exists on the OMAP2 variant.
> 
> Among other things, this results in broken rounding for the OMAP2430
> since the rounding code can potentially find matching speeds that are
> marked as RATE_IN_242X.
> 
> It also results in confusing CPUfreq about what the current speed is.

Thanks, pushing today.

Tony

      reply	other threads:[~2007-06-21 12:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-14  0:55 [PATCH] ARM: OMAP: fix clock table walking for OMAP2 variants Kevin Hilman
2007-06-21 12:00 ` 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=20070621120024.GH20283@atomide.com \
    --to=tony@atomide.com \
    --cc=khilman@mvista.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