Re: [PATCH 00/13] ARM: OMAP5: Add minimal OMAP5 SOC support
Tony, Thanks for you suggestions >> OMAP5 V2 series is ready with all comments addressed, but I have >> below dependencies to be merged to apply my series against your >> cleanup-soc branch > > OK > >> 1) git://git.pwsan.com/linux-2.6 hwmod_soc_conditional_cleanup_3.5 > > This one is not merged in yet and it seems that we're out of time > for v3.5 unless it drags on and we have -rc8 after -rc7. > OK >> 2) git://git.pwsan.com/linux-2.6 hwmod_data_cleanup_3.5 >> 3) https://github.com/hvaibhav/am335x-linux 32ksync-timer-cleanup > > These two are merged in arm-soc now. > OK >> 4) http://www.spinics.net/lists/arm-kernel/msg174461.html > > I think this series still has some pending comments? > Yes, right. In fact except for the last patch, others should not be needed when rebased against paul's PRCM cleanups which is yet to be posted and [1] which is already acked now. 1) http://www.spinics.net/lists/linux-omap/msg70192.html >> Can you please let me know how you want me to prepare the series >> with these dependencies. > > Until these dependencies get cleared out, it seems that the best > branch to base your patches is omap-cleanup-timer-for-v3.5 tag > and just carry the pending patches for a little bit longer. > Ok, will rebase against it then and then prepare the series with a couple of temporary patches that can be dropped when the above mentioned dependencies are sorted out. Thanks, Sricharan -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 00/13] ARM: OMAP5: Add minimal OMAP5 SOC support
Hi, * Sricharan R [120510 10:47]: > Hi Tony, > > > -Original Message- > > From: R Sricharan [mailto:r.sricha...@ti.com] > > Sent: Thursday, May 03, 2012 12:56 PM > > To: linux-omap@vger.kernel.org > > Cc: linux-arm-ker...@lists.infradead.org; santosh.shilim...@ti.com; > > t...@atomide.com; b-cous...@ti.com; r.sricha...@ti.com > > Subject: [PATCH 00/13] ARM: OMAP5: Add minimal OMAP5 SOC support > > > > 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. > > > OMAP5 V2 series is ready with all comments addressed, but I have > below dependencies to be merged to apply my series against your > cleanup-soc branch OK > 1) git://git.pwsan.com/linux-2.6 hwmod_soc_conditional_cleanup_3.5 This one is not merged in yet and it seems that we're out of time for v3.5 unless it drags on and we have -rc8 after -rc7. > 2) git://git.pwsan.com/linux-2.6 hwmod_data_cleanup_3.5 > 3) https://github.com/hvaibhav/am335x-linux 32ksync-timer-cleanup These two are merged in arm-soc now. > 4) http://www.spinics.net/lists/arm-kernel/msg174461.html I think this series still has some pending comments? > Can you please let me know how you want me to prepare the series > with these dependencies. Until these dependencies get cleared out, it seems that the best branch to base your patches is omap-cleanup-timer-for-v3.5 tag and just carry the pending patches for a little bit longer. Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH 00/13] ARM: OMAP5: Add minimal OMAP5 SOC support
Hi Tony, > -Original Message- > From: R Sricharan [mailto:r.sricha...@ti.com] > Sent: Thursday, May 03, 2012 12:56 PM > To: linux-omap@vger.kernel.org > Cc: linux-arm-ker...@lists.infradead.org; santosh.shilim...@ti.com; > t...@atomide.com; b-cous...@ti.com; r.sricha...@ti.com > Subject: [PATCH 00/13] ARM: OMAP5: Add minimal OMAP5 SOC support > > 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. > OMAP5 V2 series is ready with all comments addressed, but I have below dependencies to be merged to apply my series against your cleanup-soc branch 1) git://git.pwsan.com/linux-2.6 hwmod_soc_conditional_cleanup_3.5 2) git://git.pwsan.com/linux-2.6 hwmod_data_cleanup_3.5 3) https://github.com/hvaibhav/am335x-linux 32ksync-timer-cleanup 4) http://www.spinics.net/lists/arm-kernel/msg174461.html Can you please let me know how you want me to prepare the series with these dependencies. Thanks, Sricharan -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 00/13] ARM: OMAP5: Add minimal OMAP5 SOC support
* Santosh Shilimkar [120508 00:27]: > On Tuesday 08 May 2012 03:56 AM, Tony Lindgren wrote: > > * Santosh Shilimkar [120507 02:53]: > >> Tony, > >> > >> On Thursday 03 May 2012 12:56 PM, R Sricharan wrote: > >>> 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@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. > > >> 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. > > 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 -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 00/13] ARM: OMAP5: Add minimal OMAP5 SOC support
On Tuesday 08 May 2012 03:56 AM, Tony Lindgren wrote: > * Santosh Shilimkar [120507 02:53]: >> Tony, >> >> On Thursday 03 May 2012 12:56 PM, R Sricharan wrote: >>> 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@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. >> 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 ? > 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+ 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. Regards Santosh -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 00/13] ARM: OMAP5: Add minimal OMAP5 SOC support
* Santosh Shilimkar [120507 02:53]: > Tony, > > On Thursday 03 May 2012 12:56 PM, R Sricharan wrote: > > 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@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. > 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. 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? Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 00/13] ARM: OMAP5: Add minimal OMAP5 SOC support
Tony, On Thursday 03 May 2012 12:56 PM, R Sricharan wrote: > 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@vger.kernel.org/msg67166.html > Do you have a branch where above dependencies are merged ? 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. Regards Santosh -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
