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

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 [diff vs current]
  5. v1 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-15 05:32:59
Also in: linux-omap

On Tue, 11 Sep 2012, Paul Walmsley wrote:
The kernel built with omap2plus_defconfig was then booted on several 
OMAP2+ boards.  Here's what was found:
[ ... ]
- The 2420 N800 seems to have some kind of MMC-related problem
  that prevents it from booting.  Still looking into this:

  http://www.pwsan.com/omap/testlogs/common_clk_testing_devel_3.7/20120911000742/boot/2420n800/2420n800_log.txt
This has been resolved.  The APLL clocks have been missing rate 
recalculation functions for a long time.  This wasn't a problem in the 
past because these were considered fixed rate clocks (at the locked 
frequency).  But in the CCF conversion, the fixed rate was dropped.  This 
caused the MMC functional clock to be set incorrectly to the sys_clk rate.  
This in turn caused the MMC driver's timing calculation code to return the 
wrong value, preventing meaningful MMC/SD access.

The problem was resolved by creating recalc_rate function pointers for the 
APLLs that return sys_ck if the APLL is bypassed, or the APLL rate if it's 
locked, for both 2420 and 2430.


- 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