We have been noticing intermittent lock up in mxcfb_pan_display function. It seems usdhc4_clk (arch/arm/mach-mx6/clock.c) grabs clocks_mutex of the common clock framework and doesn't release for 1- 2 secs which causes ipu clock (ipu1_clk) to starve for the mutex. Any idea what can cause usdhc4 to grab the mutex for such a long time?
We have an iMx6Q and eMMC on usdhc4.
Hi Smriti
usdhc4_clk may hold due to eMMC long operations (large data transfer)
and possible errors on bus, causing multiple retries.
Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------