From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751718AbcFWKBV (ORCPT ); Thu, 23 Jun 2016 06:01:21 -0400 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:33736 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751483AbcFWKBT (ORCPT ); Thu, 23 Jun 2016 06:01:19 -0400 Date: Thu, 23 Jun 2016 11:01:04 +0100 From: Mark Brown To: Alexandre Courbot Cc: Alexandre Courbot , Liam Girdwood , Rob Herring , Mark Rutland , Linux Kernel Mailing List , "devicetree@vger.kernel.org" Message-ID: <20160623100104.GU28202@sirena.org.uk> References: <20160622082558.20935-1-acourbot@nvidia.com> <20160622082558.20935-2-acourbot@nvidia.com> <20160622103432.GJ28202@sirena.org.uk> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="R7Dyui215VKdTDYA" Content-Disposition: inline In-Reply-To: X-Cookie: Beware of Bigfoot! User-Agent: Mutt/1.6.0 (2016-04-01) X-SA-Exim-Connect-IP: 2a01:348:6:8808:fab::3 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: [PATCH 1/6] regulator: core: Allow simultaneous use of enable op and GPIO X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on mezzanine.sirena.org.uk) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --R7Dyui215VKdTDYA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Jun 23, 2016 at 02:29:39PM +0900, Alexandre Courbot wrote: > There is also another potential problem with not using the enable GPIO > in the regulator core: said GPIO can not be shared anymore between > several regulators, as this was handled by the core. Yeah, but there's more fun there since you'd need to sync up with the device specific enable as well - it's not clear that such hardware would make sense TBH. > That's not a big issue for our use-case but I just wanted to point it > out. Maybe we need a more global solution for shared GPIOs, but I can > see a few challenges on the way (e.g. which policy to adopt and how to > handle conflicts). Indeed. I've never seen such hardware though so... --R7Dyui215VKdTDYA Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJXa7NfAAoJECTWi3JdVIfQ2eQH/1bzIB5cI1yVrQZ9M4rQvPX8 UyvqDtrooec+/1jxceyA8lJuXVBrfqYtEnpZ1swCzmcbpuFYJZ4jXlVhraoRLXVc tBQC/kRo+w9FuPh3fRzqr7bMZ5jlPsnhG24wiNS6noZuYsePEg4WSiWiPT1e0umk VQ/wemmMpsIOXvsgsCn/nNz8OCL7lMZaW220YS1IsXF9u0nZHfHJ/a95zjY7M0Op ax5cto35URAlMOgYuj9HocO4plb2masjc66bRlqFWZHk+v6tYRd9Qyv1IUPgNVfd SmE2iTn9ONiC3JsdcTRdqSlsk0mKKu5SMfJtO+9pn8Nbl+RzdFp5csi9Qi1Yats= =nOtP -----END PGP SIGNATURE----- --R7Dyui215VKdTDYA--