Re: [PATCH 4/5] regulator: core: Add early supply resolution for a bypassed regulator

Path	csiph.com!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod
From	Mark Brown <broonie@kernel.org>
Newsgroups	linux.kernel
Subject	Re: [PATCH 4/5] regulator: core: Add early supply resolution for a bypassed regulator
Date	Mon, 25 Apr 2016 19:00:03 +0200
Message-ID	<rrS1B-Kw-27@gated-at.bofh.it> (permalink)
References	<rqpuH-3tV-15@gated-at.bofh.it> <rqpuH-3tV-23@gated-at.bofh.it> <rqGOR-A5-3@gated-at.bofh.it> <rqHrB-1aV-57@gated-at.bofh.it> <rqJMM-2OK-47@gated-at.bofh.it> <rrPZM-7wH-11@gated-at.bofh.it>
X-Original-To	Jon Hunter <jonathanh@nvidia.com>
MIME-Version	1.0
Content-Type	multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="m2KU9Mr9JJKQaAoQ"
Content-Disposition	inline
X-Cookie	Tomorrow, you can be anywhere.
User-Agent	Mutt/1.5.24 (2015-08-30)
X-Sa-Exim-Connect-IP	2a01:348:6:8808:fab::3
X-Sa-Exim-Mail-From	broonie@sirena.org.uk
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	robomod@news.nic.it
List-ID	<linux-kernel.vger.kernel.org>
X-Mailing-List	linux-kernel@vger.kernel.org
Approved	robomod@news.nic.it
Lines	35
Organization	linux.* mail to news gateway
X-Original-Cc	Liam Girdwood <lgirdwood@gmail.com>, linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org, Thierry Reding <treding@nvidia.com>
X-Original-Date	Mon, 25 Apr 2016 17:54:17 +0100
X-Original-Message-ID	<20160425165417.GN3217@sirena.org.uk>
X-Original-References	<1461255121-5245-1-git-send-email-jonathanh@nvidia.com> <1461255121-5245-5-git-send-email-jonathanh@nvidia.com> <20160422104837.GC3217@sirena.org.uk> <571A0A81.4010009@nvidia.com> <20160422135339.GD3217@sirena.org.uk> <571E2D48.10509@nvidia.com>
X-Original-Sender	linux-kernel-owner@vger.kernel.org
Xref	csiph.com linux.kernel:1386675

Show key headers only | View raw

[Multipart message — attachments visible in raw view] - view raw

On Mon, Apr 25, 2016 at 03:44:24PM +0100, Jon Hunter wrote:
> On 22/04/16 14:53, Mark Brown wrote:

> > We need to only *fail* in the bypass case.

> OK. So this is what I have now. Is it weird to return EPROBE_DEFER in 
> _regulator_get_voltage()? If so, I could add a test for bypass in the
> regulator_register().

It should be fine but perhaps print an error saying that it's a bypassed
regulator with no supply?  Deferring for no explicit reason can be
confusing.

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

[PATCH 0/5] regulator: A few fixes for supply resolution Jon Hunter <jonathanh@nvidia.com> - 2016-04-21 18:20 +0200
  [PATCH 1/5] regulator: core: Don't terminate supply resolution early Jon Hunter <jonathanh@nvidia.com> - 2016-04-21 18:20 +0200
    Applied "regulator: core: Don't terminate supply resolution early" to the regulator tree Mark Brown <broonie@kernel.org> - 2016-04-22 13:00 +0200
  [PATCH 4/5] regulator: core: Add early supply resolution for a bypassed regulator Jon Hunter <jonathanh@nvidia.com> - 2016-04-21 18:20 +0200
    Re: [PATCH 4/5] regulator: core: Add early supply resolution for a  bypassed regulator Mark Brown <broonie@kernel.org> - 2016-04-22 12:50 +0200
      Re: [PATCH 4/5] regulator: core: Add early supply resolution for a  bypassed regulator Jon Hunter <jonathanh@nvidia.com> - 2016-04-22 13:30 +0200
        Re: [PATCH 4/5] regulator: core: Add early supply resolution for a  bypassed regulator Mark Brown <broonie@kernel.org> - 2016-04-22 16:00 +0200
          Re: [PATCH 4/5] regulator: core: Add early supply resolution for a  bypassed regulator Jon Hunter <jonathanh@nvidia.com> - 2016-04-25 16:50 +0200
            Re: [PATCH 4/5] regulator: core: Add early supply resolution for a  bypassed regulator Mark Brown <broonie@kernel.org> - 2016-04-25 19:00 +0200

csiph-web