Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Fri, 4 Oct 2019 16:01:50 +0100
From:   Mark Brown <broonie@kernel.org>
To:     "Vaittinen, Matti" <Matti.Vaittinen@fi.rohmeurope.com>
Cc:     "lgirdwood@gmail.com" <lgirdwood@gmail.com>,
        "dianders@chromium.org" <dianders@chromium.org>,
        "m.felsch@pengutronix.de" <m.felsch@pengutronix.de>,
        "kernel@pengutronix.de" <kernel@pengutronix.de>,
        "zhang.chunyan@linaro.org" <zhang.chunyan@linaro.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "ckeepax@opensource.cirrus.com" <ckeepax@opensource.cirrus.com>
Subject: Re: [PATCH 1/3] regulator: core: fix boot-on regulators use_count
 usage
Message-ID: <20191004150150.GD4866@sirena.co.uk>
References: <CAD=FV=WVGj8xzKFFxsjpeuqtVzSvv22cHmWBRJtTbH00eC=E9w@mail.gmail.com>
 <20190923184907.GY2036@sirena.org.uk>
 <CAD=FV=VkaXDn034EFnJWYvWwyLgvq7ajfgMRm9mbhQeRKmPDRQ@mail.gmail.com>
 <20190924182758.GC2036@sirena.org.uk>
 <CAD=FV=WZSy6nHjsY2pvjcoR4iy64b35OPGEb3EPSSc5vpeTTuA@mail.gmail.com>
 <20190927084710.mt42454vsrjm3yh3@pengutronix.de>
 <CAD=FV=XM0i=GsvttJjug6VPOJJGHRqFmsmCp-1XXNvmsYp9sJA@mail.gmail.com>
 <20191004063443.GA26028@localhost.localdomain>
 <20191004113234.GA4866@sirena.co.uk>
 <054bc4c050f1b16988de057f812232b0feb707cb.camel@fi.rohmeurope.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
        protocol="application/pgp-signature"; boundary="UfEAyuTBtIjiZzX6"
Content-Disposition: inline
In-Reply-To: <054bc4c050f1b16988de057f812232b0feb707cb.camel@fi.rohmeurope.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk


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

On Fri, Oct 04, 2019 at 12:03:12PM +0000, Vaittinen, Matti wrote:
> On Fri, 2019-10-04 at 12:32 +0100, Mark Brown wrote:

> > If you want the regulator to be on without any driver present then
> > mark
> > it always-on.  If you want the regulator to be enabled prior to the
> > driver being loaded then the expectation is that the bootloader will
> > do
> > that, it's difficult to see what the benefit there is from having the
> > kernel enable things when it starts prior to having a driver unless
> > the
> > intent is to keep the regulator always on.

> I thought the regulator-boot-on could have been used for that. But as I
> said - I don't really know all this so well =) And no, I am not opposed
> to offloading this from kernel to boot, I was just trying to learn what
> is the correct thing to do (tm). Thanks for educating me on this :) I
> will suggest adding the enabling to boot code if (when) I get questions
> concerning this. (always-on won't do for regulators which need to be
> controlled for power saving or heating issues).

If you want the kernel to do it early on without the bootloader then I
think we really need to understand the use case.  My guess would be that
the underlying request would be to get the driver up earlier which is
something we should be better at but often easier said than done.

--UfEAyuTBtIjiZzX6
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEyBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAl2XXt4ACgkQJNaLcl1U
h9BNdQf416+VGBOjTatwFvaSTvsGBrnD/HdQvJRJ3HcPIpxnx/TapsTWnUxLAOBP
5iNa4+1zINbju+sls2X8cIsEiM4+AsGcQ5geP25xLa+6aNwDvl566Z2ssuwSEbNa
kurJ1cXy4fg/19HaFwQ4V6BPG/aiEfPSNZ4Y2kgz0y9O57uoUctPw/aiiPO6DORa
sElQklRIbI7nKs/OwF66cCKzldUkJJg7+i/DhgY492f+ilOgXQAF+ZOq58iKdwdI
Ej6Rm8PtqEzvyQCstCBI7NvKyslfI1lGTCAiooS81SKYM94E2YlMPN1o57BrHT/6
3PaAGBvv7oDBQelirUtbvrG8opY1
=/EfI
-----END PGP SIGNATURE-----

--UfEAyuTBtIjiZzX6--