Re: [PATCH RFC 0/6] ARM: OMAP2+: AM43x/AM335x prcm reset driver

2013-09-12 Thread Afzal Mohammed
Hi Philipp, On Monday 09 September 2013 02:36 PM, Philipp Zabel wrote: > So if I understand correctly, the only problem is that on OMAP the clock > needs to be enabled to deassert the reset, but as long as the clock > domain is in hardware supervised mode, it won't be enabled? Yes, enabling

Re: [PATCH RFC 0/6] ARM: OMAP2+: AM43x/AM335x prcm reset driver

2013-09-12 Thread Afzal Mohammed
Hi Philipp, On Monday 09 September 2013 02:36 PM, Philipp Zabel wrote: So if I understand correctly, the only problem is that on OMAP the clock needs to be enabled to deassert the reset, but as long as the clock domain is in hardware supervised mode, it won't be enabled? Yes, enabling clock

Re: [PATCH RFC 0/6] ARM: OMAP2+: AM43x/AM335x prcm reset driver

2013-09-09 Thread Philipp Zabel
Am Donnerstag, den 05.09.2013, 21:26 +0530 schrieb Afzal Mohammed: > Hi Philipp, > > On Thursday 05 September 2013 03:37 PM, Philipp Zabel wrote: > > Am Montag, den 02.09.2013, 19:41 +0530 schrieb Afzal Mohammed: > > >> Two new reset API's are provided to check whether reset is ready and > >> to

Re: [PATCH RFC 0/6] ARM: OMAP2+: AM43x/AM335x prcm reset driver

2013-09-09 Thread Philipp Zabel
Am Donnerstag, den 05.09.2013, 21:26 +0530 schrieb Afzal Mohammed: Hi Philipp, On Thursday 05 September 2013 03:37 PM, Philipp Zabel wrote: Am Montag, den 02.09.2013, 19:41 +0530 schrieb Afzal Mohammed: Two new reset API's are provided to check whether reset is ready and to clear

Re: [PATCH RFC 0/6] ARM: OMAP2+: AM43x/AM335x prcm reset driver

2013-09-05 Thread Afzal Mohammed
Hi Philipp, On Thursday 05 September 2013 03:37 PM, Philipp Zabel wrote: > Am Montag, den 02.09.2013, 19:41 +0530 schrieb Afzal Mohammed: >> Two new reset API's are provided to check whether reset is ready and >> to clear reset. This would be required in case IP needs to mix reset >> handling

Re: [PATCH RFC 0/6] ARM: OMAP2+: AM43x/AM335x prcm reset driver

2013-09-05 Thread Philipp Zabel
Hi Afzal, Am Montag, den 02.09.2013, 19:41 +0530 schrieb Afzal Mohammed: > Hi, > > This is an attempt to achieve reset on AM43x/AM335x based SoC's with > reset driver making use of the reset framework. > > prcm node is added in device tree, which would hold reset bindings. > Initially node was

Re: [PATCH RFC 0/6] ARM: OMAP2+: AM43x/AM335x prcm reset driver

2013-09-05 Thread Philipp Zabel
Hi Afzal, Am Montag, den 02.09.2013, 19:41 +0530 schrieb Afzal Mohammed: Hi, This is an attempt to achieve reset on AM43x/AM335x based SoC's with reset driver making use of the reset framework. prcm node is added in device tree, which would hold reset bindings. Initially node was made as

Re: [PATCH RFC 0/6] ARM: OMAP2+: AM43x/AM335x prcm reset driver

2013-09-05 Thread Afzal Mohammed
Hi Philipp, On Thursday 05 September 2013 03:37 PM, Philipp Zabel wrote: Am Montag, den 02.09.2013, 19:41 +0530 schrieb Afzal Mohammed: Two new reset API's are provided to check whether reset is ready and to clear reset. This would be required in case IP needs to mix reset handling procedure

[PATCH RFC 0/6] ARM: OMAP2+: AM43x/AM335x prcm reset driver

2013-09-02 Thread Afzal Mohammed
Hi, This is an attempt to achieve reset on AM43x/AM335x based SoC's with reset driver making use of the reset framework. prcm node is added in device tree, which would hold reset bindings. Initially node was made as a one that represents reset functionality of SoC. but ended up with node for

[PATCH RFC 0/6] ARM: OMAP2+: AM43x/AM335x prcm reset driver

2013-09-02 Thread Afzal Mohammed
Hi, This is an attempt to achieve reset on AM43x/AM335x based SoC's with reset driver making use of the reset framework. prcm node is added in device tree, which would hold reset bindings. Initially node was made as a one that represents reset functionality of SoC. but ended up with node for