Re: [PATCH v3 4/8] drm/panfrost: Rework page table flushing and runtime PM interaction

2019-08-28 Thread Steven Price
On 26/08/2019 23:33, Rob Herring wrote: > There is no point in resuming the h/w just to do flush operations and > doing so takes several locks which cause lockdep issues with the shrinker. > Rework the flush operations to only happen when the h/w is already awake. > This avoids taking any locks

Re: [PATCH v3 4/8] drm/panfrost: Rework page table flushing and runtime PM interaction

2019-08-27 Thread Robin Murphy
On 26/08/2019 23:33, Rob Herring wrote: There is no point in resuming the h/w just to do flush operations and doing so takes several locks which cause lockdep issues with the shrinker. Rework the flush operations to only happen when the h/w is already awake. This avoids taking any locks

[PATCH v3 4/8] drm/panfrost: Rework page table flushing and runtime PM interaction

2019-08-26 Thread Rob Herring
There is no point in resuming the h/w just to do flush operations and doing so takes several locks which cause lockdep issues with the shrinker. Rework the flush operations to only happen when the h/w is already awake. This avoids taking any locks associated with resuming which trigger lockdep