Date: Thu, 5 Feb 2015 17:43:53 +0000
From: Mark Brown <broonie@kernel.org>
To: Tim Bird <tim.bird@sonymobile.com>
Cc: "lgirdwood@gmail.com" <lgirdwood@gmail.com>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        =?iso-8859-1?B?IkFuZGVyc3NvbiwgQmr2cm4i?= 
	<Bjorn.Andersson@sonymobile.com>
Message-ID: <20150205174353.GA21293@sirena.org.uk>
References: <54D2A91D.5090700@sonymobile.com>
 <20150205015945.GQ21293@sirena.org.uk>
 <54D3A96B.2020704@sonymobile.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="E0XH9V7c99a/OAH4"
Content-Disposition: inline
In-Reply-To: <54D3A96B.2020704@sonymobile.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Subject: Re: [PATCH] regulator: Support different config and dev of_nodes in
 regulator_register
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 2459
Lines: 57


--E0XH9V7c99a/OAH4
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Thu, Feb 05, 2015 at 09:33:31AM -0800, Tim Bird wrote:
> On 02/04/2015 05:59 PM, Mark Brown wrote:

> > This is explicitly not supported; such bindings are invariably attempts
> > to encode the Linux MFD structure into the device tree (which isn't a
> > wonderful idea as the way we split things into subsystems can and does
> > change) or...

> Sorry - what is the "Linux MFD structure"?

The way we split things up into subsystems via drivers/mfd.  Our set of
subsystems is neither fixed nor authorative.

> Well, the above DT node is not complete.  Let me give some more
> context.  I eventually want to have the charger driver support 2
> regulators - one for the OTG vbus output (shown above) and one
> for a boost hardware device, which controls voltage for this and
> other parts of the system.  These are both for IP blocks that are
> in the register range of this charger hardware (and hence belong, IMHO
> in this driver).  I can easily move the otg-supply to the charger DT node,
> as you request, but what do I do about other regulator attributes,
> if I need to specify them for both the chg_otg and boost regulators
> provided by this driver? How would this be handled?  I can't put them
> all in the charger DT node.

This just sounds like a standard multi-regulator PMIC - usually the
nodes for all the regulators end up getting stuffed in a node (typically
called regulators) which the core can then interate over for you.  I'm
just not seeing what's unusual about this device, sorry.

--E0XH9V7c99a/OAH4
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJU06vYAAoJECTWi3JdVIfQ4h4H/2apXTBN3rr94uZCc0WItott
9JDE85C90SLiDK/M05BHRDwE+7AL4qcR5vyzfXNmuRVTSBqtEMZwGmITvtIf4CBE
HX/kLdysKNNRNB4ZxbQ6kZaG9a9q+BsaIetJDOTvtfoSYQMOOxIcZj9/WhQ5SEnN
CCbasRv2b8elHRxfAP3L8mX9I9si4HgefOfxfqX2yPfC+ZWwlIkF4PW7GRa9+Cnl
M756ZZFeVCswpwuweJo1bjIPTSYTbIdGe1FB+jrC0QoEcqptaz+NfQvvC7bAahcs
o+QUY8b2kspw4QNaiNNSO+9qwWRAocd+jtNpyBfpvutoY1qkDm1VCIR+25O793g=
=FNoo
-----END PGP SIGNATURE-----

--E0XH9V7c99a/OAH4--
--
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/