From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Brown Subject: Re: Deadlock scenario in regulator core Date: Wed, 23 Mar 2011 10:42:30 +0000 Message-ID: <20110323104230.GA778@opensource.wolfsonmicro.com> References: <4D891C59.1030009@codeaurora.org> <20110322223702.GO14675@home.goodmis.org> <4D892C0A.1090606@codeaurora.org> <1300835998.14261.13.camel@gandalf.stny.rr.com> <20110323000100.GB2529@opensource.wolfsonmicro.com> <1300840734.14261.72.camel@gandalf.stny.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from opensource.wolfsonmicro.com ([80.75.67.52]:48308 "EHLO opensource2.wolfsonmicro.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1756205Ab1CWKmT (ORCPT ); Wed, 23 Mar 2011 06:42:19 -0400 Content-Disposition: inline In-Reply-To: <1300840734.14261.72.camel@gandalf.stny.rr.com> Sender: linux-arm-msm-owner@vger.kernel.org List-Id: linux-arm-msm@vger.kernel.org To: Steven Rostedt Cc: David Collins , Liam Girdwood , linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org, Peter Zijlstra , Ingo Molnar On Tue, Mar 22, 2011 at 08:38:54PM -0400, Steven Rostedt wrote: > On Wed, 2011-03-23 at 00:01 +0000, Mark Brown wrote: > > What's a mutex type? I have to say this is the first time I've heard of > > mutex types and the documentation in mutex.c and mutex-design.txt isn't > > precisely verbose on what mutex_lock_nested() is for or how one would > > pick subclass. > Sorry, I said "mutex type" as a synonym to "lock class". A lock class is > pretty much how a lock is defined. OK, lock class can be grepped which was the main thing, thanks. > There's better documentation about this in the lockdep-design.txt. That's helpful, though it doesn't really say anything about how one picks subclass?