Hi All,
On Mon, Jun 18, 2012 at 10:53 AM, Lokesh Vutla lokeshvu...@ti.com wrote:
OMAP watchdong driver is adapted to runtime PM like a general device
driver but it is not appropriate. It is causing couple of functional
issues.
1. On OMAP4 SYSCLK can't be gated, because of issue with
On Sat, Jul 7, 2012 at 5:57 PM, Wim Van Sebroeck w...@iguana.be wrote:
Hi All,
On Mon, Jun 18, 2012 at 10:53 AM, Lokesh Vutla lokeshvu...@ti.com
wrote:
OMAP watchdong driver is adapted to runtime PM like a general device
driver but it is not appropriate. It is causing couple of
(+ linux-omap, linux-watchdog)
Vaibhav,
On Thu, Jul 5, 2012 at 8:06 PM, Bedia, Vaibhav vaibhav.be...@ti.com wrote:
Hi,
On Mon, Jun 18, 2012 at 10:53:16, Vutla, Lokesh wrote:
OMAP watchdong driver is adapted to runtime PM like a general device
driver but it is not appropriate. It is causing
Hi Santosh,
On Fri, Jul 06, 2012 at 12:51:03, Shilimkar, Santosh wrote:
[...]
A few questions based on the description given in the commit message.
1. On OMAP4 SYSCLK can't be gated, because of issue with WDTIMER2 module,
which constantly stays in in transition state. Value of register
Wim,
On Mon, Jun 18, 2012 at 11:11 AM, Shilimkar, Santosh
santosh.shilim...@ti.com wrote:
(You should cc linux-omap too. CC'ing linux-omap)
On Mon, Jun 18, 2012 at 10:53 AM, Lokesh Vutla lokeshvu...@ti.com wrote:
OMAP watchdong driver is adapted to runtime PM like a general device
driver
(You should cc linux-omap too. CC'ing linux-omap)
On Mon, Jun 18, 2012 at 10:53 AM, Lokesh Vutla lokeshvu...@ti.com wrote:
OMAP watchdong driver is adapted to runtime PM like a general device
driver but it is not appropriate. It is causing couple of functional
issues.
1. On OMAP4 SYSCLK
