[PATCH 15/23] Alternative mmc structure to support pxa168, pxa910, mmp2 family SD
prakity at marvell.com
Wed Dec 22 17:58:14 EST 2010
On Dec 22, 2010, at 6:10 AM, Arnd Bergmann wrote:
> On Wednesday 22 December 2010 08:09:58 Philip Rakity wrote:
>> The PXA168, PXA910, and MMP2 are not the same SOC. The family
>> of embedded processors have slightly different internal blocks
>> for SD, I2C, etc. Sometimes it is important to know which SOC
>> is being used due to differences in the silicon. Sometimes it
>> is important to know evaluation boards should be selected based
>> on the SOC on the board.
> This looks like you're moving in the wrong direction.
> If the chips are just slightly different, you'd certainly
> want to make sure that you can detect the difference at runtime,
> and be able to use the same kernel on all of the variants.
MMP2 used PJ4 core --- PXA168/PXA910 use PJ1 so rather different architecture.
PXA168/PXA910 have slightly different internal peripherals with different quirks.
Certainly possible to tell this apart at runtime but not all peripherals are the same
and startup files ARE different.
> Instead, you promote each of the SOCs to a top-level family
> in this patch, which makes it impossible to build a kernel
> for more than one of them at a time.
That was the intent to handle the case of development board selection.
it is meaningless to select MMP2 development board with say PXA168 SoC.
Open to other way to handle this problem. Suggestions welcome.
More information about the linux-arm-kernel