Thread (57 messages) flat view 57 messages, 6 authors, 2012-09-17
STALE5097d

Revision v1 of 8 in this series.

Revisions (8)
  1. v1 [diff vs current]
  2. v1 [diff vs current]
  3. v1 [diff vs current]
  4. v1 current
  5. v1 [diff vs current]
  6. v1 [diff vs current]
  7. v1 [diff vs current]
  8. v1 [diff vs current]

[PATCH 00/29] Move OMAP2+ over to use COMMON clock

From: paul@pwsan.com (Paul Walmsley)
Date: 2012-09-11 23:10:51
Also in: linux-omap

On Tue, 11 Sep 2012, Vaibhav Hiremath wrote:
quoted hunk ↗ jump to hunk
I tried this branch on BeagleBone platform and needs one small typo
correction in hwmod data patch (submitted earlier, which you are going
to queue it)

diff --git a/arch/arm/mach-omap2/omap_hwmod_33xx_data.c
b/arch/arm/mach-omap2/omap_hwmod_33xx_data.c
index de7a3ab..767a77d 100644
--- a/arch/arm/mach-omap2/omap_hwmod_33xx_data.c
+++ b/arch/arm/mach-omap2/omap_hwmod_33xx_data.c
@@ -1441,7 +1441,7 @@ static struct omap_hwmod am33xx_mmc2_hwmod = {
        .clkdm_name     = "l3s_clkdm",
        .mpu_irqs       = am33xx_mmc2_irqs,
        .sdma_reqs      = am33xx_mmc2_edma_reqs,
-       .main_clk       = "mmc2_fck",
+       .main_clk       = "mmc_clk",
        .prcm           = {
                .omap4  = {
                      .clkctrl_offs = AM33XX_CM_PER_MMC2_CLKCTRL_OFFSET,

With above change I boot tested it on BeagleBone platform and also
verified the clock rates getting printed in debugfs.
So does this mean we need to put together a patch to remove the existing 
mmc2_fck first from the OMAP clock data file?  Looks like that would be 
the right thing to do, based on the AM33x PRCM data.


- Paul
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help