Re: [PATCH V3] PM: In kernel power management domain_pm created for async schedules

On Thu, Jan 04, 2018 at 08:59:00AM +, Vikas Bansal wrote: > Sender : Rafael J. Wysocki > > Date : 2017-12-14 03:56 (GMT+5:30) > > > > > > On Wed, Dec 13, 2017 at 9:46 AM, Vikas Bansal > wrote: > >> > >> Sender : Rafael J. Wysocki

Re: [PATCH V3] PM: In kernel power management domain_pm created for async schedules

On Thu, Jan 04, 2018 at 08:59:00AM +, Vikas Bansal wrote: > Sender : Rafael J. Wysocki > > Date : 2017-12-14 03:56 (GMT+5:30) > > > > > > On Wed, Dec 13, 2017 at 9:46 AM, Vikas Bansal > wrote: > >> > >> Sender : Rafael J. Wysocki > >> Date : 2017-12-06 19:48 (GMT+5:30) > >> > >>> > >>>

Re: [PATCH V3] PM: In kernel power management domain_pm created for async schedules

On Wed, Dec 13, 2017 at 9:46 AM, Vikas Bansal wrote: > > Sender : Rafael J. Wysocki > Date : 2017-12-06 19:48 (GMT+5:30) > >> On Wednesday, December 6, 2017 3:12:38 PM CET gre...@linuxfoundation.org >> wrote: >> > On Wed, Dec 06, 2017 at

Re: [PATCH V3] PM: In kernel power management domain_pm created for async schedules

On Wed, Dec 13, 2017 at 9:46 AM, Vikas Bansal wrote: > > Sender : Rafael J. Wysocki > Date : 2017-12-06 19:48 (GMT+5:30) > >> On Wednesday, December 6, 2017 3:12:38 PM CET gre...@linuxfoundation.org >> wrote: >> > On Wed, Dec 06, 2017 at 12:07:14PM +, Vikas Bansal wrote: >> > >

Re: [PATCH V3] PM: In kernel power management domain_pm created for async schedules

  Sender : Rafael J. Wysocki  Date : 2017-12-06 19:48 (GMT+5:30)   > On Wednesday, December 6, 2017 3:12:38 PM CET gre...@linuxfoundation.org  > wrote: > > On Wed, Dec 06, 2017 at 12:07:14PM +, Vikas Bansal wrote: > > > Description: > >  > > Why is this here? > >  > > > 

Re: [PATCH V3] PM: In kernel power management domain_pm created for async schedules

  Sender : Rafael J. Wysocki  Date : 2017-12-06 19:48 (GMT+5:30)   > On Wednesday, December 6, 2017 3:12:38 PM CET gre...@linuxfoundation.org  > wrote: > > On Wed, Dec 06, 2017 at 12:07:14PM +, Vikas Bansal wrote: > > > Description: > >  > > Why is this here? > >  > > >  > > > If there is a 

Re: [PATCH V1] PM: In kernel power management domain_pm created for async schedules

On Wednesday, December 6, 2017 3:12:38 PM CET gre...@linuxfoundation.org wrote: > On Wed, Dec 06, 2017 at 12:07:14PM +, Vikas Bansal wrote: > > Description: > > Why is this here? > > > > > If there is a driver in system which starts creating async schedules > > just after resume (Same as

Re: [PATCH V1] PM: In kernel power management domain_pm created for async schedules

On Wednesday, December 6, 2017 3:12:38 PM CET gre...@linuxfoundation.org wrote: > On Wed, Dec 06, 2017 at 12:07:14PM +, Vikas Bansal wrote: > > Description: > > Why is this here? > > > > > If there is a driver in system which starts creating async schedules > > just after resume (Same as

Re: [PATCH V1] PM: In kernel power management domain_pm created for async schedules

On Wed, Dec 06, 2017 at 12:07:14PM +, Vikas Bansal wrote: > Description: Why is this here? > > If there is a driver in system which starts creating async schedules > just after resume (Same as our case, in which we faced issue). > Then async_synchronize_full API in PM cores starts waiting

Re: [PATCH V1] PM: In kernel power management domain_pm created for async schedules

On Wed, Dec 06, 2017 at 12:07:14PM +, Vikas Bansal wrote: > Description: Why is this here? > > If there is a driver in system which starts creating async schedules > just after resume (Same as our case, in which we faced issue). > Then async_synchronize_full API in PM cores starts waiting

Re: [PATCH V1] PM: In kernel power management domain_pm created for async schedules

Greg, I'll take care of this if you don't mind. On Wednesday, December 6, 2017 1:07:14 PM CET Vikas Bansal wrote: > Description: > > If there is a driver in system which starts creating async schedules > just after resume (Same as our case, in which we faced issue). > Then async_synchronize_full

Re: [PATCH V1] PM: In kernel power management domain_pm created for async schedules

Greg, I'll take care of this if you don't mind. On Wednesday, December 6, 2017 1:07:14 PM CET Vikas Bansal wrote: > Description: > > If there is a driver in system which starts creating async schedules > just after resume (Same as our case, in which we faced issue). > Then async_synchronize_full

[PATCH V1] PM: In kernel power management domain_pm created for async schedules

Description: If there is a driver in system which starts creating async schedules just after resume (Same as our case, in which we faced issue). Then async_synchronize_full API in PM cores starts waiting for completion of async schedules created by that driver (Even though those are in a domain).

[PATCH V1] PM: In kernel power management domain_pm created for async schedules

Description: If there is a driver in system which starts creating async schedules just after resume (Same as our case, in which we faced issue). Then async_synchronize_full API in PM cores starts waiting for completion of async schedules created by that driver (Even though those are in a domain).

Re: In kernel power management domain_pm created for async schedules

On Wed, Dec 06, 2017 at 05:38:31AM +, Vikas Bansal wrote: > If there is a driver in system which starts creating async schedules just > after resume (Same as our case, in which we faced issue). Then > async_synchronize_full API in PM cores starts waiting for completion of async > schedules

Re: In kernel power management domain_pm created for async schedules

On Wed, Dec 06, 2017 at 05:38:31AM +, Vikas Bansal wrote: > If there is a driver in system which starts creating async schedules just > after resume (Same as our case, in which we faced issue). Then > async_synchronize_full API in PM cores starts waiting for completion of async > schedules

In kernel power management domain_pm created for async schedules

If there is a driver in system which starts creating async schedules just after resume (Same as our case, in which we faced issue). Then async_synchronize_full API in PM cores starts waiting for completion of async schedules created by that driver (Even though those are in a domain). Because of

In kernel power management domain_pm created for async schedules

If there is a driver in system which starts creating async schedules just after resume (Same as our case, in which we faced issue). Then async_synchronize_full API in PM cores starts waiting for completion of async schedules created by that driver (Even though those are in a domain). Because of