Re: [U-Boot] [PATCH V2 1/4] configs: split ti_armv7_common into a omap generic header

2015-07-17 Thread Murali Karicheri
On 07/16/2015 03:08 PM, Nishanth Menon wrote: TI armv7 based SoCs are based on two architectures - one based on OMAP generation architecture and others based on Keystone architecture. Many of the options are architecture specific, however a lot are common with v7 architecture. So, step 1 will

Re: [U-Boot] [PATCH V2 1/4] configs: split ti_armv7_common into a omap generic header

2015-07-17 Thread Nishanth Menon
On 07/17/2015 10:38 AM, Murali Karicheri wrote: On 07/16/2015 03:08 PM, Nishanth Menon wrote: [...] /* MMC/SD IP block */ #define CONFIG_MMC #define CONFIG_GENERIC_MMC Why do we need MMC options in common? Only keystone device that uses MMC is Galileo. This should stay in

Re: [U-Boot] [PATCH V2 1/4] configs: split ti_armv7_common into a omap generic header

2015-07-17 Thread Murali Karicheri
On 07/17/2015 12:27 PM, Nishanth Menon wrote: On 07/17/2015 10:38 AM, Murali Karicheri wrote: On 07/16/2015 03:08 PM, Nishanth Menon wrote: [...] /* MMC/SD IP block */ #define CONFIG_MMC #define CONFIG_GENERIC_MMC Why do we need MMC options in common? Only keystone device that

[U-Boot] [PATCH V2 1/4] configs: split ti_armv7_common into a omap generic header

2015-07-16 Thread Nishanth Menon
TI armv7 based SoCs are based on two architectures - one based on OMAP generation architecture and others based on Keystone architecture. Many of the options are architecture specific, however a lot are common with v7 architecture. So, step 1 will be to move out OMAP specific stuff from