RE: [PATCH] ARM: OMAP2+: hwmod: Hook-up am33xx support in omap_hwmod framework

2012-07-16 Thread Hiremath, Vaibhav
On Thu, Jul 12, 2012 at 02:03:06, Paul Walmsley wrote: On Wed, 11 Jul 2012, Hiremath, Vaibhav wrote: Agreed, but would it make sense to include in v3.6 merge window? Barring force majeure, I'm pretty much done with patches for the v3.6 merge window. Am working on this patch and the

RE: [PATCH] ARM: OMAP2+: hwmod: Hook-up am33xx support in omap_hwmod framework

2012-07-11 Thread Paul Walmsley
On Wed, 11 Jul 2012, Hiremath, Vaibhav wrote: Agreed, but would it make sense to include in v3.6 merge window? Barring force majeure, I'm pretty much done with patches for the v3.6 merge window. Am working on this patch and the AM33xx hwmod data for v3.7. - Paul -- To unsubscribe from this

RE: [PATCH] ARM: OMAP2+: hwmod: Hook-up am33xx support in omap_hwmod framework

2012-07-10 Thread Hiremath, Vaibhav
On Wed, Jul 04, 2012 at 14:59:45, Paul Walmsley wrote: On Wed, 4 Jul 2012, Hiremath, Vaibhav wrote: Yes it does, and was expecting it to go along with Kevin's series. The AM33xx patch isn't a cleanup -- it adds new functionality -- so it doesn't belong as part of a cleanup series.

RE: [PATCH] ARM: OMAP2+: hwmod: Hook-up am33xx support in omap_hwmod framework

2012-07-04 Thread Paul Walmsley
On Tue, 3 Jul 2012, Hiremath, Vaibhav wrote: On Thu, Jun 28, 2012 at 21:14:16, Hiremath, Vaibhav wrote: AM33XX PRCM architecture is different that any OMAP family of devices, so it is required to have separate implementation to handle AM33XX module enable/disable, reset assert/deassert

RE: [PATCH] ARM: OMAP2+: hwmod: Hook-up am33xx support in omap_hwmod framework

2012-07-04 Thread Hiremath, Vaibhav
On Wed, Jul 04, 2012 at 14:43:15, Paul Walmsley wrote: On Tue, 3 Jul 2012, Hiremath, Vaibhav wrote: On Thu, Jun 28, 2012 at 21:14:16, Hiremath, Vaibhav wrote: AM33XX PRCM architecture is different that any OMAP family of devices, so it is required to have separate implementation to

RE: [PATCH] ARM: OMAP2+: hwmod: Hook-up am33xx support in omap_hwmod framework

2012-07-04 Thread Hiremath, Vaibhav
On Wed, Jul 04, 2012 at 14:43:15, Paul Walmsley wrote: On Tue, 3 Jul 2012, Hiremath, Vaibhav wrote: On Thu, Jun 28, 2012 at 21:14:16, Hiremath, Vaibhav wrote: AM33XX PRCM architecture is different that any OMAP family of devices, so it is required to have separate implementation to

RE: [PATCH] ARM: OMAP2+: hwmod: Hook-up am33xx support in omap_hwmod framework

2012-07-04 Thread Paul Walmsley
On Wed, 4 Jul 2012, Hiremath, Vaibhav wrote: Yes it does, and was expecting it to go along with Kevin's series. The AM33xx patch isn't a cleanup -- it adds new functionality -- so it doesn't belong as part of a cleanup series. - Paul -- To unsubscribe from this list: send the line

RE: [PATCH] ARM: OMAP2+: hwmod: Hook-up am33xx support in omap_hwmod framework

2012-07-04 Thread Paul Walmsley
On Wed, 4 Jul 2012, Hiremath, Vaibhav wrote: ARM: OMAP2+: hwmod: Add new sysc_type3 into omap_hwmod required for am33xx ARM: OMAP3/4: omap_hwmod: Add rstst_off field to struct omap_hwmod_omap4_prcm Can this also be merged into your pull request? Those have been sent as part of

RE: [PATCH] ARM: OMAP2+: hwmod: Hook-up am33xx support in omap_hwmod framework

2012-07-03 Thread Hiremath, Vaibhav
On Thu, Jun 28, 2012 at 21:14:16, Hiremath, Vaibhav wrote: AM33XX PRCM architecture is different that any OMAP family of devices, so it is required to have separate implementation to handle AM33XX module enable/disable, reset assert/deassert functionality. This patch adds wrapper api's in