From: ben-linux@fluff.org (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 5/9] S3C64XX: Set rate of crystal mux
Date: Tue, 3 Nov 2009 17:37:01 +0000 [thread overview]
Message-ID: <20091103173701.GJ23772@trinity.fluff.org> (raw)
In-Reply-To: <1257259332-7867-5-git-send-email-broonie@opensource.wolfsonmicro.com>
On Tue, Nov 03, 2009 at 02:42:08PM +0000, Mark Brown wrote:
> The current code assumes that the external clock mux will be set to
> the crystal. Set this up explicitly within the clock API.
should be merged now.
--
Ben
Q: What's a light-year?
A: One-third less calories than a regular year.
next prev parent reply other threads:[~2009-11-03 17:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-03 14:42 [PATCH 1/9] SMDK6410: Configure GPIO pull up for WM835x IRQ line Mark Brown
2009-11-03 14:42 ` [PATCH 2/9] S3C64XX: Fix S3C64XX_CLKDIV0_ARM_MASK value Mark Brown
2009-11-03 14:42 ` [PATCH 3/9] SMDK6410: Hook up regulator supplies for WM8580 Mark Brown
2009-11-03 14:42 ` [PATCH 4/9] S3C64XX: Provide logging when CPU frequencies are eliminated due to clocks Mark Brown
2009-11-03 14:42 ` [PATCH 5/9] S3C64XX: Set rate of crystal mux Mark Brown
2009-11-03 14:42 ` [PATCH 6/9] S3C64XX: Provide control of APLL Mark Brown
2009-11-03 14:42 ` [PATCH 7/9] SMDK6410: Allocate more GPIO space for WM1190-EV1 Mark Brown
2009-11-03 14:42 ` [PATCH 8/9] S3C64XX: Separate out regulator and frequency latencies Mark Brown
2009-11-03 14:42 ` [PATCH 9/9] S3C64XX: Redo voltage ranges for cpufreq Mark Brown
2009-11-03 17:37 ` Ben Dooks [this message]
2009-11-03 17:36 ` [PATCH 2/9] S3C64XX: Fix S3C64XX_CLKDIV0_ARM_MASK value Ben Dooks
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=20091103173701.GJ23772@trinity.fluff.org \
--to=ben-linux@fluff.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).