Re: Async runtime put in __device_release_driver()

2013-11-07 Thread Rafael J. Wysocki
On Thursday, November 07, 2013 09:18:52 AM Ulf Hansson wrote: > On 7 November 2013 02:05, Rafael J. Wysocki wrote: > > On Wednesday, November 06, 2013 04:21:48 PM Kevin Hilman wrote: > >> On Wed, Nov 6, 2013 at 4:16 PM, Rafael J. Wysocki > >> wrote: > >> > On Wednesday, November 06, 2013

Re: Async runtime put in __device_release_driver()

2013-11-07 Thread Ulf Hansson
On 7 November 2013 02:05, Rafael J. Wysocki wrote: > On Wednesday, November 06, 2013 04:21:48 PM Kevin Hilman wrote: >> On Wed, Nov 6, 2013 at 4:16 PM, Rafael J. Wysocki wrote: >> > On Wednesday, November 06, 2013 11:48:24 PM Ulf Hansson wrote: >> >> >> >> "Rafael J. Wysocki" skrev: >> >> >On

Re: Async runtime put in __device_release_driver()

2013-11-07 Thread Ulf Hansson
On 7 November 2013 02:05, Rafael J. Wysocki r...@rjwysocki.net wrote: On Wednesday, November 06, 2013 04:21:48 PM Kevin Hilman wrote: On Wed, Nov 6, 2013 at 4:16 PM, Rafael J. Wysocki r...@rjwysocki.net wrote: On Wednesday, November 06, 2013 11:48:24 PM Ulf Hansson wrote: Rafael J. Wysocki

Re: Async runtime put in __device_release_driver()

2013-11-07 Thread Rafael J. Wysocki
On Thursday, November 07, 2013 09:18:52 AM Ulf Hansson wrote: On 7 November 2013 02:05, Rafael J. Wysocki r...@rjwysocki.net wrote: On Wednesday, November 06, 2013 04:21:48 PM Kevin Hilman wrote: On Wed, Nov 6, 2013 at 4:16 PM, Rafael J. Wysocki r...@rjwysocki.net wrote: On Wednesday,

Re: Async runtime put in __device_release_driver()

2013-11-06 Thread Rafael J. Wysocki
On Wednesday, November 06, 2013 04:21:48 PM Kevin Hilman wrote: > On Wed, Nov 6, 2013 at 4:16 PM, Rafael J. Wysocki wrote: > > On Wednesday, November 06, 2013 11:48:24 PM Ulf Hansson wrote: > >> > >> "Rafael J. Wysocki" skrev: > >> >On Wednesday, November 06, 2013 05:02:12 PM Alan Stern wrote: >

Re: Async runtime put in __device_release_driver()

2013-11-06 Thread Kevin Hilman
On Wed, Nov 6, 2013 at 4:16 PM, Rafael J. Wysocki wrote: > On Wednesday, November 06, 2013 11:48:24 PM Ulf Hansson wrote: >> >> "Rafael J. Wysocki" skrev: >> >On Wednesday, November 06, 2013 05:02:12 PM Alan Stern wrote: >> >> On Wed, 6 Nov 2013, Rafael J. Wysocki wrote: >> >> >> >> > On

Re: Async runtime put in __device_release_driver()

2013-11-06 Thread Rafael J. Wysocki
On Wednesday, November 06, 2013 11:48:24 PM Ulf Hansson wrote: > > "Rafael J. Wysocki" skrev: > >On Wednesday, November 06, 2013 05:02:12 PM Alan Stern wrote: > >> On Wed, 6 Nov 2013, Rafael J. Wysocki wrote: > >> > >> > On Wednesday, November 06, 2013 09:51:42 AM Tomi Valkeinen wrote: > >> > >

Re: Async runtime put in __device_release_driver()

2013-11-06 Thread Ulf Hansson
"Rafael J. Wysocki" skrev: >On Wednesday, November 06, 2013 05:02:12 PM Alan Stern wrote: >> On Wed, 6 Nov 2013, Rafael J. Wysocki wrote: >> >> > On Wednesday, November 06, 2013 09:51:42 AM Tomi Valkeinen wrote: >> > > On 2013-11-05 23:29, Ulf Hansson wrote: >> > > > On 23 October 2013 12:11,

Re: Async runtime put in __device_release_driver()

2013-11-06 Thread Rafael J. Wysocki
On Wednesday, November 06, 2013 05:02:12 PM Alan Stern wrote: > On Wed, 6 Nov 2013, Rafael J. Wysocki wrote: > > > On Wednesday, November 06, 2013 09:51:42 AM Tomi Valkeinen wrote: > > > On 2013-11-05 23:29, Ulf Hansson wrote: > > > > On 23 October 2013 12:11, Tomi Valkeinen wrote: > > > >> Hi,

Re: Async runtime put in __device_release_driver()

2013-11-06 Thread Alan Stern
On Wed, 6 Nov 2013, Rafael J. Wysocki wrote: > On Wednesday, November 06, 2013 09:51:42 AM Tomi Valkeinen wrote: > > On 2013-11-05 23:29, Ulf Hansson wrote: > > > On 23 October 2013 12:11, Tomi Valkeinen wrote: > > >> Hi, > > >> > > >> I was debugging why clocks were left enabled after removing

Re: Async runtime put in __device_release_driver()

2013-11-06 Thread Rafael J. Wysocki
On Wednesday, November 06, 2013 09:51:42 AM Tomi Valkeinen wrote: > On 2013-11-05 23:29, Ulf Hansson wrote: > > On 23 October 2013 12:11, Tomi Valkeinen wrote: > >> Hi, > >> > >> I was debugging why clocks were left enabled after removing omapdss > >> driver, and I found this commit: > >> > >>

Re: Async runtime put in __device_release_driver()

2013-11-06 Thread Rafael J. Wysocki
On Wednesday, November 06, 2013 09:51:42 AM Tomi Valkeinen wrote: On 2013-11-05 23:29, Ulf Hansson wrote: On 23 October 2013 12:11, Tomi Valkeinen tomi.valkei...@ti.com wrote: Hi, I was debugging why clocks were left enabled after removing omapdss driver, and I found this commit:

Re: Async runtime put in __device_release_driver()

2013-11-06 Thread Alan Stern
On Wed, 6 Nov 2013, Rafael J. Wysocki wrote: On Wednesday, November 06, 2013 09:51:42 AM Tomi Valkeinen wrote: On 2013-11-05 23:29, Ulf Hansson wrote: On 23 October 2013 12:11, Tomi Valkeinen tomi.valkei...@ti.com wrote: Hi, I was debugging why clocks were left enabled after

Re: Async runtime put in __device_release_driver()

2013-11-06 Thread Rafael J. Wysocki
On Wednesday, November 06, 2013 05:02:12 PM Alan Stern wrote: On Wed, 6 Nov 2013, Rafael J. Wysocki wrote: On Wednesday, November 06, 2013 09:51:42 AM Tomi Valkeinen wrote: On 2013-11-05 23:29, Ulf Hansson wrote: On 23 October 2013 12:11, Tomi Valkeinen tomi.valkei...@ti.com wrote:

Re: Async runtime put in __device_release_driver()

2013-11-06 Thread Ulf Hansson
Rafael J. Wysocki r...@rjwysocki.net skrev: On Wednesday, November 06, 2013 05:02:12 PM Alan Stern wrote: On Wed, 6 Nov 2013, Rafael J. Wysocki wrote: On Wednesday, November 06, 2013 09:51:42 AM Tomi Valkeinen wrote: On 2013-11-05 23:29, Ulf Hansson wrote: On 23 October 2013 12:11,

Re: Async runtime put in __device_release_driver()

2013-11-06 Thread Rafael J. Wysocki
On Wednesday, November 06, 2013 11:48:24 PM Ulf Hansson wrote: Rafael J. Wysocki r...@rjwysocki.net skrev: On Wednesday, November 06, 2013 05:02:12 PM Alan Stern wrote: On Wed, 6 Nov 2013, Rafael J. Wysocki wrote: On Wednesday, November 06, 2013 09:51:42 AM Tomi Valkeinen wrote: On

Re: Async runtime put in __device_release_driver()

2013-11-06 Thread Kevin Hilman
On Wed, Nov 6, 2013 at 4:16 PM, Rafael J. Wysocki r...@rjwysocki.net wrote: On Wednesday, November 06, 2013 11:48:24 PM Ulf Hansson wrote: Rafael J. Wysocki r...@rjwysocki.net skrev: On Wednesday, November 06, 2013 05:02:12 PM Alan Stern wrote: On Wed, 6 Nov 2013, Rafael J. Wysocki wrote:

Re: Async runtime put in __device_release_driver()

2013-11-06 Thread Rafael J. Wysocki
On Wednesday, November 06, 2013 04:21:48 PM Kevin Hilman wrote: On Wed, Nov 6, 2013 at 4:16 PM, Rafael J. Wysocki r...@rjwysocki.net wrote: On Wednesday, November 06, 2013 11:48:24 PM Ulf Hansson wrote: Rafael J. Wysocki r...@rjwysocki.net skrev: On Wednesday, November 06, 2013 05:02:12

Re: Async runtime put in __device_release_driver()

2013-11-05 Thread Tomi Valkeinen
On 2013-11-05 23:29, Ulf Hansson wrote: > On 23 October 2013 12:11, Tomi Valkeinen wrote: >> Hi, >> >> I was debugging why clocks were left enabled after removing omapdss >> driver, and I found this commit: >> >> fa180eb448fa263cf18dd930143b515d27d70d7b (PM / Runtime: Idle devices >>

Re: Async runtime put in __device_release_driver()

2013-11-05 Thread Ulf Hansson
On 23 October 2013 12:11, Tomi Valkeinen wrote: > Hi, > > I was debugging why clocks were left enabled after removing omapdss > driver, and I found this commit: > > fa180eb448fa263cf18dd930143b515d27d70d7b (PM / Runtime: Idle devices > asynchronously after probe|release) > > I don't understand

Re: Async runtime put in __device_release_driver()

2013-11-05 Thread Ulf Hansson
On 23 October 2013 12:11, Tomi Valkeinen tomi.valkei...@ti.com wrote: Hi, I was debugging why clocks were left enabled after removing omapdss driver, and I found this commit: fa180eb448fa263cf18dd930143b515d27d70d7b (PM / Runtime: Idle devices asynchronously after probe|release) I don't

Re: Async runtime put in __device_release_driver()

2013-11-05 Thread Tomi Valkeinen
On 2013-11-05 23:29, Ulf Hansson wrote: On 23 October 2013 12:11, Tomi Valkeinen tomi.valkei...@ti.com wrote: Hi, I was debugging why clocks were left enabled after removing omapdss driver, and I found this commit: fa180eb448fa263cf18dd930143b515d27d70d7b (PM / Runtime: Idle devices