Hi Eddie,
On 3/29/2019 1:08 PM, Eddie James wrote:
On 3/28/19 4:25 PM, Jae Hyun Yoo wrote:
To prevent this issue, this commit adds spinlock protection and clock
status checking logic into the Aspeed video engine driver.
Thanks Jae. Do you have a reliable way to reproduce this? Haven't seen
i
On 3/28/19 4:25 PM, Jae Hyun Yoo wrote:
Video engine clock control functions in the Aspeed video engine driver are
being called from multiple context without any protection so video clocks
can be disabled twice and eventually it causes a kernel warning with stack
dump printing out like below:
Video engine clock control functions in the Aspeed video engine driver are
being called from multiple context without any protection so video clocks
can be disabled twice and eventually it causes a kernel warning with stack
dump printing out like below:
[ 120.034729] WARNING: CPU: 0 PID: 1334 at
