[U-Boot] [PATCH v2 00/22] U-Boot MMC SPL for OMAP4

[Aneesh V <aneesh@ti.com>]

Dear Wolfgang,

On Sunday 15 May 2011 08:51 PM, Aneesh V wrote:
> This series adds mmc SPL support for OMAP4. This is essentially
> an up-streaming effort for TI's x-loader for OMAP4 using the SPL
> framework
>
> This work partly draws upon previous work done for x-loader by:
> 	Santosh Shilimkar<santosh.shilimkar@ti.com>
> 	Rajendra Nayak<rnayak@ti.com>
> and many others
>
> This series is depedent on the following series:
> http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/95550
>
> Features supported:
> * Clock init - DPLL locking, clock domains/modules enabling
> * SDRAM/DMM initialization
> * Mux initialization
> * MMC raw read support
> * MMC FAT read support
>
> Improvments over x-loader:
> * Code completely revamped
> * DPLL programming that works for all SYS_CLK frequencies
> * Automatic SDRAM identification and initialization
> * Board dependent parts(especially mux) deferred to u-boot. So, same
>    SPL will work for Panda and SDP and most likely on any other board
>    that comes along
> * Determination of u-boot size to avoid reading extra content while
>    loading U-Boot
> * Modular apporach to enable future addition of support for all OMAP3/4
>    platforms
>
> V2:
> * Some fixes in SDRAM init, clock init
> * Use of pre-calculated M&  N values for DPLL locking instead
>    run-time calculation
> * Change in make files to allow reuse of common rules
>    between boards
> * Console initialization moved further earlier in the boot
>    allowing traces from even clock initialization code
> * Reuse utility macros from a previous series
>
> Aneesh V (21):
>    omap4: add OMAP4430 revision check
>    armv7: start.S: provide a hook for saving boot params
>    omap4: save parameters passed by ROM code to SPL
>    arm: new labels in the linker script file
>    Add generic spl infrastructure
>    armv7: start.S: add SPL support
>    omap: add spl support
>    omap4: add spl support for OMAP4 SDP
>    omap4: utility function to identify the context of hw init
>    omap4: separate mux settings into essential and non essential parts
>    omap4: correct mux data for sdp4430
>    omap4: add clock support
>    omap4: add serial console support to SPL
>    omap4: add sdram init support
>    omap4: calculate EMIF register values
>    omap4: automatic sdram detection
>    armv7: embed u-boot size within u-boot for use from SPL
>    omap: add MMC support to SPL
>    omap: spl: add FAT support over MMC
>    omap4: add spl support for OMAP4 Panda
>    omap: spl: add more debug traces
>
> John Rigby (1):
>    mkimage: Add OMAP boot image support
>

This work has mainly two parts:
1. Add the missing hardware support for OMAP4 such as clock init, sdram
init etc (OMAP4 u-boot worked without these because it was always
prececeded by x-loader)
2. Addd SPL support.

Now that SPL framework design is taking time, I was wondering whether I
should split the series into two based on the two main tasks above.

That is, I can send out the hw initialization part immediately without
waiting for the SPL design to be finalized and send out the SPL support
once we concluded the SPL design discussions.

The patches themselves will not change much. Just that they will be
separated into two different series. The reviews done so far will not
be wasted.

Are you Ok with this approach?

best regards,
Aneesh