On Wed, Jun 24, 2015 at 10:40:02AM +0200, Daniel Vetter wrote:
> On Wed, Jun 24, 2015 at 09:09:03AM +0100, Chris Wilson wrote:
> > Akash noticed that we were recursing from the call to
> > intel_runtime_pm_get() inside intel_mark_busy() when we were already
> > waking the device (through another in
On Wed, Jun 24, 2015 at 10:40:02AM +0200, Daniel Vetter wrote:
> On Wed, Jun 24, 2015 at 09:09:03AM +0100, Chris Wilson wrote:
> > Akash noticed that we were recursing from the call to
> > intel_runtime_pm_get() inside intel_mark_busy() when we were already
> > waking the device (through another in
On Wed, Jun 24, 2015 at 09:09:03AM +0100, Chris Wilson wrote:
> Akash noticed that we were recursing from the call to
> intel_runtime_pm_get() inside intel_mark_busy() when we were already
> waking the device (through another intel_runtime_pm_get()). In
> intel_mark_busy() we know the device is awa
Akash noticed that we were recursing from the call to
intel_runtime_pm_get() inside intel_mark_busy() when we were already
waking the device (through another intel_runtime_pm_get()). In
intel_mark_busy() we know the device is awake and purpose of the
reference here is to simply keep the device awak
