Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933395AbcK2Lw4 (ORCPT ); Tue, 29 Nov 2016 06:52:56 -0500 Received: from mx0b-001ae601.pphosted.com ([67.231.152.168]:54571 "EHLO mx0b-001ae601.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757344AbcK2LwQ (ORCPT ); Tue, 29 Nov 2016 06:52:16 -0500 Authentication-Results: ppops.net; spf=none smtp.mailfrom=ckeepax@opensource.wolfsonmicro.com Date: Tue, 29 Nov 2016 11:53:06 +0000 From: Charles Keepax To: Mark Brown CC: , , Subject: Re: [PATCH 2/2] regulator: core: Allow enable GPIO to be specified using GPIOD Message-ID: <20161129115306.GI1867@localhost.localdomain> References: <1480419045-2275-1-git-send-email-ckeepax@opensource.wolfsonmicro.com> <1480419045-2275-2-git-send-email-ckeepax@opensource.wolfsonmicro.com> <20161129114547.erdaezyfvzzdtjuk@sirena.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <20161129114547.erdaezyfvzzdtjuk@sirena.org.uk> User-Agent: Mutt/1.5.23 (2014-03-12) X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1609300000 definitions=main-1611290201 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 846 Lines: 18 On Tue, Nov 29, 2016 at 11:45:47AM +0000, Mark Brown wrote: > On Tue, Nov 29, 2016 at 11:30:45AM +0000, Charles Keepax wrote: > > The regulator subsystem has used GPIOs internally for a while, however, > > end drivers must still specify their enable GPIO using a GPIO number. This > > patch allows the end drivers to specify the enable GPIO using GPIOD > > directly. > > The reason we don't support descriptors is that the GPIO API currently > doesn't support having more than one user of a descriptor but GPIO > enables for regulators get shared often enough to be interesting. If > drivers start using this then that'd mean that the shared enable support > would become erratic depending on which driver was in use. Ah ok thanks, guess we can drop this one then. The first patch in the chain is hopefully still good though. Thanks, Charles