Re: lockdep dump on devtree_lock (involving esdhc)

2013-06-12 Thread Thomas Gleixner
On Tue, 11 Jun 2013, Scott Wood wrote: I get the following lockdump output on p2020rdb using v3.10-rc5-43-g34376a5. While it's not particularly polite for the esdhc driver to be calling OF functions while holding another lock which can be acquired from interrupt context, why is devtree_lock

Re: lockdep dump on devtree_lock (involving esdhc)

2013-06-12 Thread Stephen Warren
On 06/11/2013 05:33 PM, Scott Wood wrote: I get the following lockdump output on p2020rdb using v3.10-rc5-43-g34376a5. While it's not particularly polite for the esdhc driver to be calling OF functions while holding another lock which can be acquired from interrupt context, why is

Re: lockdep dump on devtree_lock (involving esdhc)

2013-06-12 Thread Scott Wood
On 06/12/2013 10:43:31 AM, Stephen Warren wrote: On 06/11/2013 05:33 PM, Scott Wood wrote: I get the following lockdump output on p2020rdb using v3.10-rc5-43-g34376a5. While it's not particularly polite for the esdhc driver to be calling OF functions while holding another lock which can

lockdep dump on devtree_lock (involving esdhc)

2013-06-11 Thread Scott Wood
I get the following lockdump output on p2020rdb using v3.10-rc5-43-g34376a5. While it's not particularly polite for the esdhc driver to be calling OF functions while holding another lock which can be acquired from interrupt context, why is devtree_lock usually acquired in an irqsafe manner but