Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751495AbdL0I4v (ORCPT ); Wed, 27 Dec 2017 03:56:51 -0500 Received: from mail-pf0-f170.google.com ([209.85.192.170]:42694 "EHLO mail-pf0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751028AbdL0I4t (ORCPT ); Wed, 27 Dec 2017 03:56:49 -0500 X-Google-Smtp-Source: ACJfBotEHAh/l+BEYqImGtL9mcliEPhOtHp1dKdzZaf+2l/jhcgMeWtT5mrqzQEMaAMYsr15+RqSPw== Date: Wed, 27 Dec 2017 14:26:45 +0530 From: Viresh Kumar To: Rob Herring Cc: ulf.hansson@linaro.org, Kevin Hilman , Viresh Kumar , Nishanth Menon , Stephen Boyd , Rafael Wysocki , linux-pm@vger.kernel.org, Vincent Guittot , rnayak@codeaurora.org, sudeep.holla@arm.com, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH V8 3/3] OPP: Allow "opp-hz" and "opp-microvolt" to contain magic values Message-ID: <20171227085645.GF8312@vireshk-i7> References: <476d7ae69184d787ccc6d99f8df6069007fd0a91.1513591822.git.viresh.kumar@linaro.org> <20171226202955.32j7gzonrixtwdpt@rob-hp-laptop> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171226202955.32j7gzonrixtwdpt@rob-hp-laptop> 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 Content-Length: 1468 Lines: 40 On 26-12-17, 14:29, Rob Herring wrote: > On Mon, Dec 18, 2017 at 03:51:30PM +0530, Viresh Kumar wrote: > > +On some platforms the exact frequency or voltage may be hidden from the OS by > > +the firmware and the "opp-hz" or the "opp-microvolt" properties may contain > > +magic values that represent the frequency or voltage in a firmware dependent > > +way, for example an index of an array in the firmware. > > I'm still not convinced this is a good idea. You were kind-of a few days back :) lkml.kernel.org/r/CAL_JsqK-qtAaM_Ou5NtxcWR3F_q=8rMPJUm-VqGtKhbtWe5SAQ@mail.gmail.com So here is the deal: - I proposed "domain-performance-state" property for this stuff initially. - But Kevin didn't like that and proposed reusing "opp-hz" and "opp-microvolt", which we all agreed to multiple times.. - And we are back to the same discussion now and its painful and time killing for all of us. TBH, I don't have too strong preferences about any of the suggestions you guys have and I need you guys to tell me what binding changes to do here and I will do that. > If you have firmware > partially managing things, then I think we should have platform specific > bindings or drivers. What about the initial idea then, like "performance-state" for the power domains ? All platforms will anyway replicate that binding only. > This is complex enough I'm not taking silence from Stephen as an okay. Sure, but I am not sure how to make him speak :) -- viresh