Re: [PATCH] ARM: OMAP2+: omap_device: add fail hook for runtime_pm when bad data is detected

2013-12-10 Thread Tony Lindgren
* Kevin Hilman khil...@linaro.org [131209 08:07]: Tony Lindgren t...@atomide.com writes: * Nishanth Menon n...@ti.com [131203 17:40]: Due to the cross dependencies between hwmod for automanaged device information for OMAP and dts node definitions, we can run into scenarios where the dts

Re: [PATCH] ARM: OMAP2+: omap_device: add fail hook for runtime_pm when bad data is detected

2013-12-10 Thread Kevin Hilman
Tony Lindgren t...@atomide.com writes: * Kevin Hilman khil...@linaro.org [131209 08:07]: Tony Lindgren t...@atomide.com writes: * Nishanth Menon n...@ti.com [131203 17:40]: Due to the cross dependencies between hwmod for automanaged device information for OMAP and dts node definitions,

Re: [PATCH] ARM: OMAP2+: omap_device: add fail hook for runtime_pm when bad data is detected

2013-12-09 Thread Kevin Hilman
Tony Lindgren t...@atomide.com writes: * Nishanth Menon n...@ti.com [131203 17:40]: Due to the cross dependencies between hwmod for automanaged device information for OMAP and dts node definitions, we can run into scenarios where the dts node is defined, however it's hwmod entry is yet to be

Re: [PATCH] ARM: OMAP2+: omap_device: add fail hook for runtime_pm when bad data is detected

2013-12-05 Thread Joel Fernandes
On 12/04/2013 07:07 PM, Nishanth Menon wrote: On 18:14-20131204, Joel Fernandes wrote: On 12/04/2013 05:03 PM, Nishanth Menon wrote: On 12/04/2013 02:08 AM, Joel Fernandes wrote: On 12/04/2013 07:09 AM, Nishanth Menon wrote: Due to the cross dependencies between hwmod for automanaged device

Re: [PATCH] ARM: OMAP2+: omap_device: add fail hook for runtime_pm when bad data is detected

2013-12-05 Thread Tony Lindgren
* Nishanth Menon n...@ti.com [131203 17:40]: Due to the cross dependencies between hwmod for automanaged device information for OMAP and dts node definitions, we can run into scenarios where the dts node is defined, however it's hwmod entry is yet to be added. In these cases: a) omap_device

Re: [PATCH] ARM: OMAP2+: omap_device: add fail hook for runtime_pm when bad data is detected

2013-12-04 Thread Joel Fernandes
On 12/04/2013 07:09 AM, Nishanth Menon wrote: Due to the cross dependencies between hwmod for automanaged device information for OMAP and dts node definitions, we can run into scenarios where the dts node is defined, however it's hwmod entry is yet to be added. In these cases: a) omap_device

Re: [PATCH] ARM: OMAP2+: omap_device: add fail hook for runtime_pm when bad data is detected

2013-12-04 Thread Nishanth Menon
On 12/04/2013 02:08 AM, Joel Fernandes wrote: On 12/04/2013 07:09 AM, Nishanth Menon wrote: Due to the cross dependencies between hwmod for automanaged device information for OMAP and dts node definitions, we can run into scenarios where the dts node is defined, however it's hwmod entry is yet

Re: [PATCH] ARM: OMAP2+: omap_device: add fail hook for runtime_pm when bad data is detected

2013-12-04 Thread Joel Fernandes
On 12/04/2013 05:03 PM, Nishanth Menon wrote: On 12/04/2013 02:08 AM, Joel Fernandes wrote: On 12/04/2013 07:09 AM, Nishanth Menon wrote: Due to the cross dependencies between hwmod for automanaged device information for OMAP and dts node definitions, we can run into scenarios where the dts

Re: [PATCH] ARM: OMAP2+: omap_device: add fail hook for runtime_pm when bad data is detected

2013-12-04 Thread Nishanth Menon
On 18:14-20131204, Joel Fernandes wrote: On 12/04/2013 05:03 PM, Nishanth Menon wrote: On 12/04/2013 02:08 AM, Joel Fernandes wrote: On 12/04/2013 07:09 AM, Nishanth Menon wrote: Due to the cross dependencies between hwmod for automanaged device information for OMAP and dts node

[PATCH] ARM: OMAP2+: omap_device: add fail hook for runtime_pm when bad data is detected

2013-12-03 Thread Nishanth Menon
Due to the cross dependencies between hwmod for automanaged device information for OMAP and dts node definitions, we can run into scenarios where the dts node is defined, however it's hwmod entry is yet to be added. In these cases: a) omap_device does not register a pm_domain (since it cannot find