Re: [PATCH] scsi: ufs: Schedule clk gating work on correct queue

2018-10-17 Thread Martin K. Petersen
Evan, > With commit 10e5e37581fc ("scsi: ufs: Add clock ungating to a separate > workqueue"), clock gating work was moved to a separate work queue with > WQ_MEM_RECLAIM set, since clock gating could occur from a memory > reclaim context. Unfortunately, clk_gating.gate_work was left queued > via

Re: [PATCH] scsi: ufs: Schedule clk gating work on correct queue

2018-10-17 Thread Stephen Boyd
Quoting Evan Green (2018-10-05 10:27:32) > With commit 10e5e37581fc ("scsi: ufs: Add clock ungating to a separate > workqueue"), clock gating work was moved to a > separate work queue with WQ_MEM_RECLAIM set, since clock > gating could occur from a memory reclaim context. Unfortunately, > clk_gatin

Re: [PATCH] scsi: ufs: Schedule clk gating work on correct queue

2018-10-17 Thread Doug Anderson
Hi, On Fri, Oct 5, 2018 at 10:28 AM Evan Green wrote: > > With commit 10e5e37581fc ("scsi: ufs: Add clock ungating to a separate > workqueue"), clock gating work was moved to a > separate work queue with WQ_MEM_RECLAIM set, since clock > gating could occur from a memory reclaim context. Unfortuna

[PATCH] scsi: ufs: Schedule clk gating work on correct queue

2018-10-05 Thread Evan Green
With commit 10e5e37581fc ("scsi: ufs: Add clock ungating to a separate workqueue"), clock gating work was moved to a separate work queue with WQ_MEM_RECLAIM set, since clock gating could occur from a memory reclaim context. Unfortunately, clk_gating.gate_work was left queued via schedule_delayed_wo