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
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.
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
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.
4 matches
Mail list logo