Re: [PATCH V2] PM / OPP: Call notifier without holding opp_table->lock

2017-09-20 Thread Chanwoo Choi
Hi Viresh, On 2017년 09월 21일 05:25, Viresh Kumar wrote: > The notifier callbacks may want to call some OPP helper routines which > may try to take the same opp_table->lock again and cause a deadlock. One > such usecase was reported by Chanwoo Choi, where calling > dev_pm_opp_disable() leads us to

Re: [PATCH V2] PM / OPP: Call notifier without holding opp_table->lock

2017-09-20 Thread Chanwoo Choi
Hi Viresh, On 2017년 09월 21일 05:25, Viresh Kumar wrote: > The notifier callbacks may want to call some OPP helper routines which > may try to take the same opp_table->lock again and cause a deadlock. One > such usecase was reported by Chanwoo Choi, where calling > dev_pm_opp_disable() leads us to

[PATCH V2] PM / OPP: Call notifier without holding opp_table->lock

2017-09-20 Thread Viresh Kumar
The notifier callbacks may want to call some OPP helper routines which may try to take the same opp_table->lock again and cause a deadlock. One such usecase was reported by Chanwoo Choi, where calling dev_pm_opp_disable() leads us to the devfreq's OPP notifier handler, which further calls

[PATCH V2] PM / OPP: Call notifier without holding opp_table->lock

2017-09-20 Thread Viresh Kumar
The notifier callbacks may want to call some OPP helper routines which may try to take the same opp_table->lock again and cause a deadlock. One such usecase was reported by Chanwoo Choi, where calling dev_pm_opp_disable() leads us to the devfreq's OPP notifier handler, which further calls