From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757148AbcHWLVU (ORCPT ); Tue, 23 Aug 2016 07:21:20 -0400 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:40420 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752840AbcHWLVS (ORCPT ); Tue, 23 Aug 2016 07:21:18 -0400 Date: Tue, 23 Aug 2016 11:40:02 +0100 From: Mark Brown To: Chen-Yu Tsai Cc: Rask Ingemann Lambertsen , Mark Rutland , devicetree , Liam Girdwood , linux-kernel , linux-sunxi , Rob Herring , Maxime Ripard , Lee Jones , linux-arm-kernel Message-ID: <20160823104002.GX22076@sirena.org.uk> References: <20160821021125.1521-1-wens@csie.org> <20160821021125.1521-4-wens@csie.org> <20160822162907.GO22076@sirena.org.uk> <20160822175205.h76hurjaopnosymc@vip.cybercity.dk> <20160822180932.GW22076@sirena.org.uk> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="oIMVlEQ///Q2JYC7" Content-Disposition: inline In-Reply-To: X-Cookie: Satire is what closes in New Haven. 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 3/9] regulator: core: Try full range when adjusting regulators to constraints X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: No (on mezzanine.sirena.org.uk); Unknown failure Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --oIMVlEQ///Q2JYC7 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Aug 23, 2016 at 12:17:23PM +0800, Chen-Yu Tsai wrote: > On Tue, Aug 23, 2016 at 2:09 AM, Mark Brown wrote: > > Sure, but the constraints also say that you can do 1.32V which the > > system is not physically capable of delivering. That's not a good sign > > for the constraints, it suggests that at least the capabilities of the > > regulator have not been taken into consideration when setting up the > > constraints. > So to be clear, the constraints should be the intersection of the > recommended operating parameters of the consumer and the regulator's > output, with the voltage/current steps taken in to consideration. The constraints are there to say what the *system* can deliver. That includes the limitations of the consumers, the regulators and the physical design of the board. Just as one shouldn't just throw in the maximum voltage range that the regulator can deliver one also shouldn't just use the maximum voltage range a consumer can support for similar reasons. --oIMVlEQ///Q2JYC7 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJXvCfxAAoJECTWi3JdVIfQyFEH/1fuJcSJvdSaIkRxIvSY0x3v pUltItbWNT0hV14kw96IcIXb2m/Hqe7fk9ntoEFfENqsPsAbpnC0x3N0sCYRZTYY zrRh9JCdjer8GH8rr5QWwJNww76Yr0cC+WhWQk9ijTwr8TxGPBNvFhii4T4mCyH6 bnsJOelwFI3/oaafyGEJpU+Z4MgKLIeaKO6IfzK0ZnAWyyY/eZYsYBnprSV/yx2r WfcqTqwZQVe7RpgjGFMdWxdZNwSSh33dpI8oEWjHltwPgJ0JA8+tdDutH1d4TRTz vU3fr1Ja8VbXepYnO84oHtyn/kKdVbsdg68KWnDQs2yRWWl2NUsJxEkYEBZsusw= =UyoY -----END PGP SIGNATURE----- --oIMVlEQ///Q2JYC7--