From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932098AbbJ0IT0 (ORCPT ); Tue, 27 Oct 2015 04:19:26 -0400 Received: from mail-pa0-f54.google.com ([209.85.220.54]:36146 "EHLO mail-pa0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754158AbbJ0ITX (ORCPT ); Tue, 27 Oct 2015 04:19:23 -0400 Date: Tue, 27 Oct 2015 13:49:17 +0530 From: Viresh Kumar To: Mark Brown Cc: Stephen Boyd , Rob Herring , Rafael Wysocki , nm@ti.com, linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org, rob.herring@linaro.org, lee.jones@linaro.org, devicetree@vger.kernel.org, Ian Campbell , Kumar Gala , open list , Mark Rutland , Pawel Moll , "Rafael J. Wysocki" Subject: Re: [PATCH 01/16] PM / OPP: Add 'supply-names' binding Message-ID: <20151027081917.GD5505@ubuntu> References: <2b87b162eabd1570ae2311e1ef8655acda72f678.1441972771.git.viresh.kumar@linaro.org> <55F72C97.2030306@kernel.org> <20151016002243.GA23912@codeaurora.org> <20151016060227.GS19018@linux> <20151016191658.GA16437@codeaurora.org> <20151017041055.GZ19018@linux> <20151022163942.GX8232@sirena.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151022163942.GX8232@sirena.org.uk> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 23-10-15, 01:39, Mark Brown wrote: > When we start doing this we also start having to worry about things like > the sequencing of the updates between the various supplies and end up in > full on power sequencing (or at least baking some sequencing into the DT > which will doubtless need extending at some point). Absolutely. > I'm not sure that's > a place we want to end up just yet, I think it's safer to just have a > little bit of code in the kernel that glues things together in the cases > where this is needed. So you are effectively saying that we shouldn't go ahead with multi regulator support in OPP library, right? I went ahead with it as it came as a requirement (specially from Qcom). To the problem of sequencing, maybe we can just support that for the simple case, where supplies will be programmed in the order in which they are present in the property I added in this patch. And not try to solve problem for the complex cases, if we feel it is getting ugly. @Stephen ? -- viresh