From mboxrd@z Thu Jan  1 00:00:00 1970
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: Deadlock scenario in regulator core
Date: Tue, 22 Mar 2011 22:43:17 +0000
Message-ID: <20110322224316.GA10841@opensource.wolfsonmicro.com>
References: <4D891C59.1030009@codeaurora.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <linux-arm-msm-owner@vger.kernel.org>
Received: from opensource.wolfsonmicro.com ([80.75.67.52]:53489 "EHLO
	opensource2.wolfsonmicro.com" rhost-flags-OK-OK-OK-FAIL)
	by vger.kernel.org with ESMTP id S1753063Ab1CVWnE (ORCPT
	<rfc822;linux-arm-msm@vger.kernel.org>);
	Tue, 22 Mar 2011 18:43:04 -0400
Content-Disposition: inline
In-Reply-To: <4D891C59.1030009@codeaurora.org>
Sender: linux-arm-msm-owner@vger.kernel.org
List-Id: linux-arm-msm@vger.kernel.org
To: David Collins <collinsd@codeaurora.org>
Cc: Liam Girdwood <lrg@slimlogic.co.uk>, linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org

On Tue, Mar 22, 2011 at 03:02:01PM -0700, David Collins wrote:

> enable the parent regulator?  Likewise, is the lock around
> _notifier_call_chain required?

For this: we don't want the chain changing under us and the chain is
protected by the mutex.