[PATCH 00/13] ARM: OMAP5: Add minimal OMAP5 SOC support

* Santosh Shilimkar [off-list ref] [120508 00:27]:

On Tuesday 08 May 2012 03:56 AM, Tony Lindgren wrote:

quoted

* Santosh Shilimkar [off-list ref] [120507 02:53]:

quoted

Tony,

On Thursday 03 May 2012 12:56 PM, R Sricharan wrote:

quoted

The series adds minimal OMAP5 support.
OMAP5430 has a dual core Cortex-A15 based MPU subsystem with 2MB
L2 cache. The SOC has many compatible blocks with OMAP4 SOCS and
hence large part of the peripherals are re-used.

OMAP5432 is another variant of OMAP5430, with a
memory controller supporting DDR3 and SATA.

Series is generated against the 3.4-rc5. This has been rebased on
top of the OMAP2+ cleanup series [1]

To get the boot working with omap2plus_defconfig,
OMAP5 hwmod/clock/prm/cm database needs to be added.
The data and the integrated tree are available in the
below git repository

OMAP5_DATA:
git://gitorious.org/omap-sw-develoment/linux-omap-dev.git
 omap5_data

OMAP5_INTEGRATED:
git://gitorious.org/omap-sw-develoment/linux-omap-dev.git
 omap5_dt_integrated

The series is boot tested on OMAP5430 ES1.0.
OMAP2/3/4 build and boot is tested as well to avoid any breakage
because of the series.

Patch "TEMP: ARM: OMAP5: Add cpu_is_omap54xx() checks" is temporary and
can be dropped once rebased against [2]

Patch "TEMP: ARM: OMAP5: Update the base address of the 32k-counter" is
temporary and can be dropped once rebased against [3]


[1] http://www.spinics.net/lists/linux-omap/msg69233.html
[2] http://www.spinics.net/lists/linux-omap/msg69013.html
[3] http://www.mail-archive.com/linux-omap at vger.kernel.org/msg67166.html

Do you have a branch where above dependencies are merged ?

Seems like those should go into the cleanup branch, and then
that can be used as a base.

Yep. That will be a good base.

quoted

quoted

How do you suggest to go about updating this series so
that above dependencies plus DT support(3.3 based branch
in arm-soc tree and needs to be updated against 3.4) is
base tree for the patchset.

Probably the DT patch should be separate, we can make dt branch
depend on the cleanup branch.

Sounds good. Btw, who is re-basing the omap-dt branch against 3.4 ?

That's already queued up, I can merge in some trivial v3.4 based patches
Benoit has and it gets updated automatically.
 

quoted

Then the data files should be first posted for reviews (and potentially
updated for what we have queued in hwmod-cleanup).  Does this series
compile on it's own without the data now?

This series does compile on it's own without data patches. Data
patches needs to re-based against Paul's clean-up and also we
need to sort out ES1/ES2 diff so they can wait till then.
Probably 3.6+

OK good.
 

This series was intentionally made in such a way that it can
be merged without data patches. Just for getting boot working
on OMAP5 data patches needs to be merged.

Great, excellent.

Regards,

Tony