From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932666AbdDQFdL (ORCPT ); Mon, 17 Apr 2017 01:33:11 -0400 Received: from mail-pf0-f169.google.com ([209.85.192.169]:36207 "EHLO mail-pf0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932370AbdDQFdI (ORCPT ); Mon, 17 Apr 2017 01:33:08 -0400 Date: Mon, 17 Apr 2017 11:03:03 +0530 From: Viresh Kumar To: Sudeep Holla Cc: Rafael Wysocki , ulf.hansson@linaro.org, Kevin Hilman , Viresh Kumar , Nishanth Menon , Stephen Boyd , linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org, Vincent Guittot , robh+dt@kernel.org, lina.iyer@linaro.org, rnayak@codeaurora.org, devicetree@vger.kernel.org Subject: Re: [PATCH V4 1/9] PM / OPP: Allow OPP table to be used for power-domains Message-ID: <20170417053303.GG28191@vireshk-i7> References: <468e756b-7112-4006-b31d-9fcf1c32673d@arm.com> <20170413055049.GN5910@vireshk-i7> <854e3f66-6f93-2b90-14a9-7eaea6a0b74c@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <854e3f66-6f93-2b90-14a9-7eaea6a0b74c@arm.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 13-04-17, 14:43, Sudeep Holla wrote: > Interesting. My understand of power domain and in particular power > domain performance was that it would control both. The abstract number > you introduce would hide clocks and regulators. > > But if the concept treats it just as yet another regulator, we do we > need these at all. Why don't we relate this performance to regulator > values and be done with it ? > > Sorry if I am missing to understand something here. I would look this as > replacement for both clocks and regulators, something similar to ACPI > CPPC. If not, it looks unnecessary to me with the information I have got > so far. I kind of answered that in the other email. Some background may be good here. So Qcom tried to solve all this with virtual regulators, but the problem was that they need to talk in terms of integer values (1, 2, 3..) and not voltages and so they can't use the regulator framework straight away. And so we are doing all this. -- viresh