Re: [PATCHv2] ARM: omap2+: omap_hwmod: Set unique lock_class_key per hwmod

2015-02-10 Thread Paul Walmsley
On Tue, 10 Feb 2015, Peter Ujfalusi wrote: > Add struct lock_class_key to omap_hwmod struct and use it to set unique > lockdep class per hwmod. > This will ensure that lockdep will know that each omap_hwmod->_lock should > be treated as separate class and will not give false warning about

[PATCHv2] ARM: omap2+: omap_hwmod: Set unique lock_class_key per hwmod

2015-02-10 Thread Peter Ujfalusi
Add struct lock_class_key to omap_hwmod struct and use it to set unique lockdep class per hwmod. This will ensure that lockdep will know that each omap_hwmod->_lock should be treated as separate class and will not give false warning about deadlock or other issues due to nested use of hwmods.

Re: [PATCHv2] ARM: omap2+: omap_hwmod: Set unique lock_class_key per hwmod

2015-02-10 Thread Paul Walmsley
On Tue, 10 Feb 2015, Peter Ujfalusi wrote: Add struct lock_class_key to omap_hwmod struct and use it to set unique lockdep class per hwmod. This will ensure that lockdep will know that each omap_hwmod-_lock should be treated as separate class and will not give false warning about deadlock or

[PATCHv2] ARM: omap2+: omap_hwmod: Set unique lock_class_key per hwmod

2015-02-10 Thread Peter Ujfalusi
Add struct lock_class_key to omap_hwmod struct and use it to set unique lockdep class per hwmod. This will ensure that lockdep will know that each omap_hwmod-_lock should be treated as separate class and will not give false warning about deadlock or other issues due to nested use of hwmods.