Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp303121imu; Mon, 26 Nov 2018 21:56:51 -0800 (PST) X-Google-Smtp-Source: AFSGD/VAFBhx2SBmtRaRK3kHwCgfkphVqi0MoRGW4YfyqvEA/2GnARy+sLpH2MWI1m/8c6++EqAL X-Received: by 2002:a62:644:: with SMTP id 65mr638363pfg.161.1543298211095; Mon, 26 Nov 2018 21:56:51 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1543298211; cv=none; d=google.com; s=arc-20160816; b=DWiTcj2oEsXoxUAOHpVxFL4Sgy305UavOgxrAp9YM9ECXPtrYneEG9iSr+1xuxLD7b 9jMl2n87THJSlk0GeM3ZGRAoKldFcMcOCguBVq01zo3l60cVlVgPygJjQTC9Ibjeueqd CnJ/ZC39JSYeLSqcYobhkMMh3H0OgGc/VEJVLAjqLZ0E1lz+sXRsNOrPENYNCmLMcLMw 0xn9fUXwnamSLWLPh3Y+DXlInge+/dhnQmp3mqA4AnrdExMfGt9V2Q7dVFW1JKBEfZGC xAIUixJsDyEEbgCQupImY9G1ksrrmBD/xy0IG/rTubLhVgcLGS41Mkl/1WIHyChVbTyY ahZQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dmarc-filter :dkim-signature:dkim-signature; bh=/5FPBQpDThO8R27HLn3/Mum1JHwkwZbGwA8tbH7cjLo=; b=Yut5lbfb+/D3BdOyVxpkyQ+vpTwUEFepuYolC7AWNOJ1iRhV+vRx9+UnAktRP02fAo zoDo9SC8VNpRR5oJc2XmNZOU+PJVwgdmc8NIWBSkgXrWE7esIXQ7OOx48V8D6shIVWAd bMu9LxAY89LSXnFcYbssO9QDMXFtMEbmfz5WJjFqVZqdbKDeGOGonEgLrBc18R679gPc qkTaoD1EBYJjjZ+VfKqUeSisV8qiIGZ5MW4s+DY0kfKB9n5ZM2qz4v8e8YKYP/9dEt3J LDp34406jl7lHCXPmzXesN8wqwtrPsrOPeHiz/BaMRZKPlo39rITdumpSXhAHNO8hpVa HQBg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@codeaurora.org header.s=default header.b=CQXR4uA+; dkim=pass header.i=@codeaurora.org header.s=default header.b=Mh6oQhRS; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f1si2460821pgn.502.2018.11.26.21.56.36; Mon, 26 Nov 2018 21:56:51 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@codeaurora.org header.s=default header.b=CQXR4uA+; dkim=pass header.i=@codeaurora.org header.s=default header.b=Mh6oQhRS; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728425AbeK0QBB (ORCPT + 99 others); Tue, 27 Nov 2018 11:01:01 -0500 Received: from smtp.codeaurora.org ([198.145.29.96]:53914 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728025AbeK0QBB (ORCPT ); Tue, 27 Nov 2018 11:01:01 -0500 Received: by smtp.codeaurora.org (Postfix, from userid 1000) id 3BBCE60AD8; Tue, 27 Nov 2018 05:04:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1543295062; bh=0pXqJl1GIvIEOOc8YR4EEXatycPH2vI7fo7lm/CYp8U=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=CQXR4uA+GW//SVlMo+N+CDcTp3bWAMPHbS8E4OxAWW0crGeVm5D1W1fkcz5qOPbkP z9bg7rYEWMCXsJWSx8jkUDjMrmyVQOIFboqp/cJzS6nRY15nNicGjm6jafVDvOvxYK Q0TkNIrC/cquZsTYSx6KaIoWoeZTHuyqkpXSfOzA= X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on pdx-caf-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.7 required=2.0 tests=ALL_TRUSTED,BAYES_00, DKIM_INVALID,DKIM_SIGNED autolearn=no autolearn_force=no version=3.4.0 Received: from [10.79.128.194] (blr-bdr-fw-01_globalnat_allzones-outside.qualcomm.com [103.229.18.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: rnayak@smtp.codeaurora.org) by smtp.codeaurora.org (Postfix) with ESMTPSA id AC9D6607C6; Tue, 27 Nov 2018 05:04:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1543295061; bh=0pXqJl1GIvIEOOc8YR4EEXatycPH2vI7fo7lm/CYp8U=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=Mh6oQhRSZ0MVSsi+UjFJMcT9jhcmczW7+fSJzZ4eKnGgArbYqPPRRzKBc6HJri9+d fr+EMfX3BTdknNuwUQO4n1M/FHKDaPDswj1KWoGniUsWCWaHcvpH3wN51saw33W1bG YW+PNo6wBQVstxsdZWe8l+mfwG0JsyYcJss+L5pg= DMARC-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org AC9D6607C6 Authentication-Results: pdx-caf-mail.web.codeaurora.org; dmarc=none (p=none dis=none) header.from=codeaurora.org Authentication-Results: pdx-caf-mail.web.codeaurora.org; spf=none smtp.mailfrom=rnayak@codeaurora.org Subject: Re: [RFC PATCH] dt-bindings: opp: Extend qcom-opp bindings with properties needed for CPR To: Niklas Cassel Cc: Rob Herring , viresh.kumar@linaro.org, sboyd@kernel.org, andy.gross@linaro.org, ulf.hansson@linaro.org, collinsd@codeaurora.org, mka@chromium.org, devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org References: <20180627045234.27403-3-rnayak@codeaurora.org> <20181015124749.27276-1-niklas.cassel@linaro.org> <20181105231745.GA25883@bogus> <20181109163917.GA6673@centauri.lan> <20181120161457.GA12783@centauri.lan> From: Rajendra Nayak Message-ID: <6f827942-6a3c-1855-77c9-3ee076ac8010@codeaurora.org> Date: Tue, 27 Nov 2018 10:34:16 +0530 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.3.1 MIME-Version: 1.0 In-Reply-To: <20181120161457.GA12783@centauri.lan> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11/20/2018 9:44 PM, Niklas Cassel wrote: > On Tue, Nov 20, 2018 at 09:42:05AM +0530, Rajendra Nayak wrote: >> >> >> On 11/9/2018 10:09 PM, Niklas Cassel wrote: >>> On Mon, Nov 05, 2018 at 05:17:45PM -0600, Rob Herring wrote: >>>> On Mon, Oct 15, 2018 at 02:47:49PM +0200, Niklas Cassel wrote: >>>>> Extend qcom-opp bindings with properties needed for Core Power Reduction >>>>> (CPR). >>>>> >>>>> CPR is included in a great variety of Qualcomm SoC, e.g. msm8916 and >>>>> msm8996, and was first introduced in msm8974. >>>>> >>>>> Signed-off-by: Niklas Cassel >>>>> --- >>>>> Hello Rob, Rajendra, >>>>> >>>>> Sorry for not replying sooner. >>>>> Since Rob wanted the binding to be complete before merging, >>>>> this is my proposal to extend the OPP binding with properties >>>>> needed to support CPR (both for msm8916 and msm8996). >>>>> I've discussed the proposal with Viresh, and this proposal >>>>> seems better than what I previously suggested here: >>>>> https://lore.kernel.org/lkml/20181005204424.GA29500@centauri.lan/ >>>>> >>>>> .../devicetree/bindings/opp/qcom-opp.txt | 19 +++++++++++++++++++ >>>>> 1 file changed, 19 insertions(+) >>>>> >>>>> diff --git a/Documentation/devicetree/bindings/opp/qcom-opp.txt b/Documentation/devicetree/bindings/opp/qcom-opp.txt >>>>> index db4d970c7ec7..3ab5dd84de86 100644 >>>>> --- a/Documentation/devicetree/bindings/opp/qcom-opp.txt >>>>> +++ b/Documentation/devicetree/bindings/opp/qcom-opp.txt >>>>> @@ -23,3 +23,22 @@ Required properties: >>>>> representing a corner/level that's communicated with a remote microprocessor >>>>> (usually called the RPM) which then translates it into a certain voltage on >>>>> a voltage rail. >>>> >>>> I've lost the context here. Please send this all together. >>> >>> Will do, as soon as I've gotten your feedback on this mail. >> >> Niklas, are you still waiting for feedback on this mail from Rob? > > Yes. Rob, did you have any further feedback for Niklas based on his binding proposal? > > Rajendra, I realize that your patches have been ready for merging for > a long time, and this fuse-level is quite complex, so the discussion > has been taken longer than expected. Sorry for that. > > Hopefully Rob will reply soon, or perhaps he could agree to merge your > binding as is, and I could extend it later, when we have reached a > consensus. Or should we merge the qcom,level binding for now (since I though we agreed 'reg' is probably not the right fit for it) and then discuss further on how to describe the legacy platforms which require more details like fuse bindings? Note that the current platform (sdm845) only needs the qcom,level binding. What Niklas is proposing is for describing the older SoCs.