From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756398AbcK2MtB (ORCPT ); Tue, 29 Nov 2016 07:49:01 -0500 Received: from mail-wj0-f195.google.com ([209.85.210.195]:34361 "EHLO mail-wj0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751494AbcK2Msv (ORCPT ); Tue, 29 Nov 2016 07:48:51 -0500 MIME-Version: 1.0 In-Reply-To: References: From: "Rafael J. Wysocki" Date: Tue, 29 Nov 2016 13:48:49 +0100 X-Google-Sender-Auth: U8s1HB79IB-idjr4kB3W_nTEL8I Message-ID: Subject: Re: [PATCH V5 00/10] PM / OPP: Multiple regulator support To: Viresh Kumar Cc: Rafael Wysocki , Nishanth Menon , Stephen Boyd , Lists linaro-kernel , Linux PM , Linux Kernel Mailing List , Vincent Guittot , Rob Herring , Dave Gerlach , Mark Brown , "devicetree@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Nov 29, 2016 at 7:36 AM, Viresh Kumar wrote: > Hi, > > Some platforms (like TI) have complex DVFS configuration for CPU > devices, where multiple regulators are required to be configured to > change DVFS state of the device. This was explained well by Nishanth > earlier [1]. > > One of the major complaints around multiple regulators case was that the > DT isn't responsible in any way to represent the order in which multiple > supplies need to be programmed, before or after a frequency change. It > was considered in this patch and such information is left for the > platform specific OPP driver now, which can register its own > opp_set_rate() callback with the OPP core and the OPP core will then > call it during DVFS. > > The patches are tested on Exynos5250 (Dual A15). I have hacked around DT > and code to pass values for multiple regulators and verified that they > are all properly read by the kernel (using debugfs interface). > > Dave Gerlach has already tested [2] it on the real TI platforms and it > works well for him. > > This is rebased over: linux-next branch in the PM tree. > > V4->V5: > - Stephen boyd had some minor review comments and gave his Reviewed-by > tag for the rest. Only 2 patches don't have his RBY tag. > - Individual patches contain the version history from V4 to V5. Cool. I'd still like to see that everyone agrees with patch [6/10] in particular. Thanks, Rafael