From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 1/4] DaVinci DA8xx: tidy up clock ID definition
Date: Fri, 3 Aug 2012 09:05:40 -0700 [thread overview]
Message-ID: <20120803160540.GD16633@bill-the-cat> (raw)
In-Reply-To: <1343727037-17419-2-git-send-email-lwithers@guralp.com>
On Tue, Jul 31, 2012 at 09:30:34AM +0000, Laurence Withers wrote:
> Tidy up the clock IDs defined for the DA8xx SOCs. With this new structure in
> place, it is clear how to define new clock IDs, and how these map to the
> numbers presented in the technical reference manual.
>
> Signed-off-by: Laurence Withers <lwithers@guralp.com>
> Cc: Tom Rini <trini@ti.com>
> Cc: Prabhakar Lad <prabhakar.csengg@gmail.com>
I've applied this with a minor change for DAVINCI_MMC0_CLKID having been
added here in another series. Thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20120803/2eb2b0cf/attachment.pgp>
next prev parent reply other threads:[~2012-08-03 16:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 9:30 [U-Boot] [PATCH v2 0/4] DaVinci DA8xx: tidy up clock IDs Laurence Withers
2012-07-31 9:30 ` [U-Boot] [PATCH v2 1/4] DaVinci DA8xx: tidy up clock ID definition Laurence Withers
2012-08-03 16:05 ` Tom Rini [this message]
2012-07-31 9:30 ` [U-Boot] [PATCH v2 2/4] DaVinci DA850: UART2 clock ID comes from ASYNC3 Laurence Withers
2012-08-03 16:06 ` Tom Rini
2012-07-31 9:30 ` [U-Boot] [PATCH v2 3/4] DaVinci DA8xx: replace magic number for DDR speed Laurence Withers
2012-07-31 9:30 ` [U-Boot] [PATCH v2 4/4] DaVinci DA8xx: fix set_cpu_clk_info() Laurence Withers
2012-08-01 5:24 ` [U-Boot] [PATCH v2 0/4] DaVinci DA8xx: tidy up clock IDs Prabhakar Lad
2012-08-03 16:06 ` Tom Rini
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=20120803160540.GD16633@bill-the-cat \
--to=trini@ti.com \
--cc=u-boot@lists.denx.de \
/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