RE: [PATCH-V2 3/3] arm:omap:omap4: Hook-up am33xx support to existing prm code

2012-02-02 Thread Hiremath, Vaibhav
On Wed, Feb 01, 2012 at 23:03:56, Hilman, Kevin wrote: Hiremath, Vaibhav hvaib...@ti.com writes: On Tue, Jan 24, 2012 at 04:05:32, Hilman, Kevin wrote: Hiremath, Vaibhav hvaib...@ti.com writes: On Wed, Jan 11, 2012 at 21:48:25, Hiremath, Vaibhav wrote: On Tue, Jan 10, 2012 at

Re: [PATCH-V2 3/3] arm:omap:omap4: Hook-up am33xx support to existing prm code

2012-02-02 Thread Kevin Hilman
Hiremath, Vaibhav hvaib...@ti.com writes: On Wed, Feb 01, 2012 at 23:03:56, Hilman, Kevin wrote: Hiremath, Vaibhav hvaib...@ti.com writes: On Tue, Jan 24, 2012 at 04:05:32, Hilman, Kevin wrote: Hiremath, Vaibhav hvaib...@ti.com writes: On Wed, Jan 11, 2012 at 21:48:25, Hiremath,

RE: [PATCH-V2 3/3] arm:omap:omap4: Hook-up am33xx support to existing prm code

2012-02-02 Thread Hiremath, Vaibhav
On Wed, Feb 01, 2012 at 23:03:56, Hilman, Kevin wrote: Hiremath, Vaibhav hvaib...@ti.com writes: On Tue, Jan 24, 2012 at 04:05:32, Hilman, Kevin wrote: Hiremath, Vaibhav hvaib...@ti.com writes: On Wed, Jan 11, 2012 at 21:48:25, Hiremath, Vaibhav wrote: On Tue, Jan 10, 2012 at

Re: [PATCH-V2 3/3] arm:omap:omap4: Hook-up am33xx support to existing prm code

2012-02-01 Thread Kevin Hilman
Hiremath, Vaibhav hvaib...@ti.com writes: On Tue, Jan 24, 2012 at 04:05:32, Hilman, Kevin wrote: Hiremath, Vaibhav hvaib...@ti.com writes: On Wed, Jan 11, 2012 at 21:48:25, Hiremath, Vaibhav wrote: On Tue, Jan 10, 2012 at 23:39:22, Hilman, Kevin wrote: Vaibhav Hiremath hvaib...@ti.com

RE: [PATCH-V2 3/3] arm:omap:omap4: Hook-up am33xx support to existing prm code

2012-01-31 Thread Hiremath, Vaibhav
On Tue, Jan 24, 2012 at 04:05:32, Hilman, Kevin wrote: Hiremath, Vaibhav hvaib...@ti.com writes: On Wed, Jan 11, 2012 at 21:48:25, Hiremath, Vaibhav wrote: On Tue, Jan 10, 2012 at 23:39:22, Hilman, Kevin wrote: Vaibhav Hiremath hvaib...@ti.com writes: AM33XX PRM module (L4_WK

RE: [PATCH-V2 3/3] arm:omap:omap4: Hook-up am33xx support to existing prm code

2012-01-23 Thread Hiremath, Vaibhav
On Wed, Jan 11, 2012 at 21:48:25, Hiremath, Vaibhav wrote: On Tue, Jan 10, 2012 at 23:39:22, Hilman, Kevin wrote: Vaibhav Hiremath hvaib...@ti.com writes: AM33XX PRM module (L4_WK domain) will be treated as another seperate partition in _prm_bases[] table. Also, since

Re: [PATCH-V2 3/3] arm:omap:omap4: Hook-up am33xx support to existing prm code

2012-01-23 Thread Kevin Hilman
Hiremath, Vaibhav hvaib...@ti.com writes: On Wed, Jan 11, 2012 at 21:48:25, Hiremath, Vaibhav wrote: On Tue, Jan 10, 2012 at 23:39:22, Hilman, Kevin wrote: Vaibhav Hiremath hvaib...@ti.com writes: AM33XX PRM module (L4_WK domain) will be treated as another seperate partition in

RE: [PATCH-V2 3/3] arm:omap:omap4: Hook-up am33xx support to existing prm code

2012-01-11 Thread Hiremath, Vaibhav
On Tue, Jan 10, 2012 at 23:39:22, Hilman, Kevin wrote: Vaibhav Hiremath hvaib...@ti.com writes: AM33XX PRM module (L4_WK domain) will be treated as another seperate partition in _prm_bases[] table. Also, since cpu_is_omap34xx check is true for am33xx family of devices, we must check

Re: [PATCH-V2 3/3] arm:omap:omap4: Hook-up am33xx support to existing prm code

2012-01-10 Thread Kevin Hilman
Vaibhav Hiremath hvaib...@ti.com writes: AM33XX PRM module (L4_WK domain) will be treated as another seperate partition in _prm_bases[] table. Also, since cpu_is_omap34xx check is true for am33xx family of devices, we must check cpu_is_am33xx fisrt, in order to follow omap4 execution path.