Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753254AbbBFLt7 (ORCPT ); Fri, 6 Feb 2015 06:49:59 -0500 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:53008 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751314AbbBFLt6 (ORCPT ); Fri, 6 Feb 2015 06:49:58 -0500 Date: Fri, 6 Feb 2015 11:49:53 +0000 From: Mark Brown To: Bjorn Andersson Cc: "Bird, Tim" , "lgirdwood@gmail.com" , "linux-kernel@vger.kernel.org" Message-ID: <20150206114953.GT21293@sirena.org.uk> References: <54D2A91D.5090700@sonymobile.com> <20150205015945.GQ21293@sirena.org.uk> <54D3A96B.2020704@sonymobile.com> <20150205174353.GA21293@sirena.org.uk> <54D3B858.9060103@sonymobile.com> <20150205192740.GL21293@sirena.org.uk> <20150205220844.GA3218@sonymobile.com> <20150206003212.GR21293@sirena.org.uk> <20150206005239.GD3218@sonymobile.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="v6y62sMLpNVbummj" Content-Disposition: inline In-Reply-To: <20150206005239.GD3218@sonymobile.com> X-Cookie: My LESLIE GORE record is BROKEN ... User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: 94.175.94.161 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: [PATCH] regulator: Support different config and dev of_nodes in regulator_register 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 Content-Length: 2034 Lines: 49 --v6y62sMLpNVbummj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Feb 05, 2015 at 04:52:40PM -0800, Bjorn Andersson wrote: > On Thu 05 Feb 16:32 PST 2015, Mark Brown wrote: > > On Thu, Feb 05, 2015 at 02:08:54PM -0800, Bjorn Andersson wrote: > > > However this only works for the non-supply regulator properties - and > > > this is where Tim's patch is trying to sort out. > > No, this works completely fine for supply properties - to repeat what I > > said in reply to the original patch the supply is a supply to the chip > > not to an individual IP on the chip. > It does make some sense to consider the vbus-supply being connected to > the block, rather than directly to the vbus-switch. So it would work for > Tim's use case. Like I say if we do that then we don't have consistency in how we map a schematic into a DT binding - you have to dig into the binding of each device and figure out if the supply is viewed as being for blocks or for the chip as a whole and we've got the potential for problems in the binding if we figure out that a supply is actually used by other blocks later on and don't want to break existing DTs. --v6y62sMLpNVbummj Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJU1KpgAAoJECTWi3JdVIfQD6oH/3aqDWmh50a/39ttSmO1tM8H w/PUAXvOIKiK9Gix0ga8vZ8RFfmMJqRolBH5TkFKrSjAa/K2RqnmxEpXNSr6BSKN IkuZ1kgHszpOoaxK2EIkh7VlDXXPtDVcnYpPYufRhFfD+oRjFgRJxKGBKrspy+dz 387nVxF79Sr8s1TcSdotoL8axsnEuw+A0gzfv7JpzEkNqjHAew9aB3RApBemckIh zHMhMNQdiYg99uWDl/xAKrFlEwy1EePEK3kZfCKhpdPMS2MxRd7mB+q6THLydC+z N+D0qO5PaYBvtZsMULy8B8UkLdJo/b8c9U2pVshE/2wAz+fjjYxIHHrbyOL4B6U= =vpWK -----END PGP SIGNATURE----- --v6y62sMLpNVbummj-- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/