Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757112AbcK2LqF (ORCPT ); Tue, 29 Nov 2016 06:46:05 -0500 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:57756 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754654AbcK2Lp4 (ORCPT ); Tue, 29 Nov 2016 06:45:56 -0500 Date: Tue, 29 Nov 2016 11:45:47 +0000 From: Mark Brown To: Charles Keepax Cc: lgirdwood@gmail.com, linux-kernel@vger.kernel.org, patches@opensource.wolfsonmicro.com Message-ID: <20161129114547.erdaezyfvzzdtjuk@sirena.org.uk> References: <1480419045-2275-1-git-send-email-ckeepax@opensource.wolfsonmicro.com> <1480419045-2275-2-git-send-email-ckeepax@opensource.wolfsonmicro.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="vqejv22mrilsn54e" Content-Disposition: inline In-Reply-To: <1480419045-2275-2-git-send-email-ckeepax@opensource.wolfsonmicro.com> X-Cookie: rugged, adj.: User-Agent: NeoMutt/20161014 (1.7.1) X-SA-Exim-Connect-IP: 2001:470:1f1d:6b5::3 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: [PATCH 2/2] regulator: core: Allow enable GPIO to be specified using GPIOD X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: No (on mezzanine.sirena.org.uk); Unknown failure Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1290 Lines: 32 --vqejv22mrilsn54e Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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. --vqejv22mrilsn54e Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAABCAAGBQJYPWpqAAoJECTWi3JdVIfQr94H/RJwn/q8ADQhirqEjEOwWaif JeSdo835wsYNzdmAxwO5Yhq7mFH7HhHPb3FzEh1nrtEkFcaMQfUzu0u2w0QUEtrE 3vDBcyHY6yQjR+836L5EuajGBINGHAIA7lS1Ah9VDJifUABtOFYr3eRuNMEcbVJp fJ0p65YGpkryXUM7WZO/0a9CcNKso9CD1HXFrWwDRgfz7CByi3M5d9gW1v99drT3 a1PoTThGKJTvN4VkeZflx6go3QdTeKog6CNtyuOhVRU8uSHUI03/nVvnO1uccik8 mnVs2rishTYsZ/rg2G70WmjAVyXvSbd1tx08Gkhsq/kPaES5mnz5xBOgizAZ4DU= =ueqO -----END PGP SIGNATURE----- --vqejv22mrilsn54e--