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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux