public inbox for linux-omap@vger.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, vikram.pandita@ti.com
Subject: Re: [PATCH 0/2] OMAP3 clock: fix 96MHz clocks, usbhost_120m_fclk enable
Date: Mon, 4 Aug 2008 11:13:44 +0300	[thread overview]
Message-ID: <20080804081343.GB8885@atomide.com> (raw)
In-Reply-To: <20080717021112.21489.95137.stgit@localhost.localdomain>

* Paul Walmsley <paul@pwsan.com> [080717 05:15]:
> This series fixes a few bugs in the OMAP3 clock tree.  The most noticeable
> difference is that the "Clock usbhost_48m_fck didn't enable in 100000 tries"
> no longer appears during boot.

Pushing these two today.

Tony

> 
> 
> ---
> 
>    text    data     bss     dec     hex filename
> 3391587  157104  107136 3655827  37c893 vmlinux.3430sdp.orig
> 3391683  157104  107136 3655923  37c8f3 vmlinux.3430sdp.new
> 
>  arch/arm/mach-omap2/clock.c           |   63 ++++++++++++++++++---------------
>  arch/arm/mach-omap2/clock34xx.h       |   60 ++++++++++++++++++++-----------
>  arch/arm/mach-omap2/cm-regbits-34xx.h |   10 ++++-
>  3 files changed, 80 insertions(+), 53 deletions(-)
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2008-08-04  8:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-17  2:13 [PATCH 0/2] OMAP3 clock: fix 96MHz clocks, usbhost_120m_fclk enable Paul Walmsley
2008-07-17  2:13 ` [PATCH 1/2] OMAP3 clock: fix 96MHz clocks Paul Walmsley
2008-07-17  2:14 ` [PATCH 2/2] OMAP3 clock: don't wait for USBHOST IDLEST bit on usbhost_120m_fclk enable Paul Walmsley
2008-08-04  8:13 ` 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=20080804081343.GB8885@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=vikram.pandita@ti.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