Re: ufshcd_queuecommand() triggering after ufshcd_suspend()?

2019-01-16 Thread John Stultz
On Sun, Jan 13, 2019 at 7:25 PM Zang Leigang wrote: > I think there are two different issues: > > 1. clk_gating's state(including state's trace event) and is_suspended is not > wrapped by ufshcd_is_clkgating_allowed which Hisilicon's kirin platoform > soc does not need but is set

Re: ufshcd_queuecommand() triggering after ufshcd_suspend()?

2019-01-13 Thread Zang Leigang
rnel.org > Subject: ufshcd_queuecommand() triggering after ufshcd_suspend()? > > Hey all, > Frequently, since support for the HiKey960's UFS code landed in > 4.19, I've noticed the following warning on reboot: > > [ 23.086860] WARNING: CPU: 0 PID: 2507 at > drivers/scsi/uf

Re: ufshcd_queuecommand() triggering after ufshcd_suspend()?

2019-01-10 Thread Avri Altman
: ufshcd_queuecommand() triggering after ufshcd_suspend()? Hey all, Frequently, since support for the HiKey960's UFS code landed in 4.19, I've noticed the following warning on reboot: [ 23.086860] WARNING: CPU: 0 PID: 2507 at drivers/scsi/ufs/ufshcd.c:2460 ufshcd_queuecommand+0x59c/0x5a8 [ 23.096256] Modules

ufshcd_queuecommand() triggering after ufshcd_suspend()?

2019-01-10 Thread John Stultz
Hey all, Frequently, since support for the HiKey960's UFS code landed in 4.19, I've noticed the following warning on reboot: [ 23.086860] WARNING: CPU: 0 PID: 2507 at drivers/scsi/ufs/ufshcd.c:2460 ufshcd_queuecommand+0x59c/0x5a8 [ 23.096256] Modules linked in: [ 23.099313] CPU: 0 PID: