Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp138929imu; Thu, 3 Jan 2019 15:56:49 -0800 (PST) X-Google-Smtp-Source: ALg8bN5cPZ9HzwBxbHFRdap8MjEqME9xLjfFAwCT8IKC1+7OOHzzFIaCLsVLPJPcp0PPhpRk5nme X-Received: by 2002:a17:902:6b0c:: with SMTP id o12mr49614975plk.291.1546559809312; Thu, 03 Jan 2019 15:56:49 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1546559809; cv=none; d=google.com; s=arc-20160816; b=D0bcbaweEYrgRj2c+j1mYwsK2PceMQbsFPL7YLZ0YK1du/gISOiNDJPbdlBqkyoLDz P1NRUMf9d4BtV/ogWM3nUP9sC4VEoOJv5DLldMyDpvFXlJ9ZSeRyCGiBv9Sn2Nm/XrXn o87vD4pLhrQrgbTx90trtdURa60PJB+SMBqHLH2mZWD1f11cnvhUtcQY6FDXFqUC6UM1 NFPhVhG8ouJ41tuRWEUV1RSgpETnyjrgniNCWAU0AoswO+rwu1gB2ELgWXUClTMGIjb8 3/Ym1T57tCu/2ah+5nJPU5GaVTKGHNT5aYlSI4PAklAZy82arN4gBSIKdMPmCcykNc5t XGxQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=HpLaT31lx0Chd9R3UN2zzE7rCUt3h5YDJRDI4MSKi90=; b=XhymrSAvjRNuq44XLb85VwysrPr73VfSIscAMUuoPAWHi70ijo3Hny1j0xvAOTm9aO 57ifbK2Kax8wxNW0WJ3yQKmrN43QPhWuTKw1OFBYu9jUXAE1QjiGTAh/5TZ7AVT8rQZZ YNPYAc4YinhOivVOiqM0Ys8wbPDUgYY4CUp10l5BYUtgk80ACoWN066H2MVMI9lChuAt FXba+a2rMSb35ikopz3d2Gm26A2sIMU0fxwXEq1B2wyK+HAO5O8UXA7jRgJV8NDwCzVV 1y2wYi4lsCfkf4RiqC78xwWWtpqNFNFjR2+4220e6LDxBphhFOjSMvTDTmQ5/TWSi1Oi +FgQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=DcKWQg92; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g33si10684958pgm.426.2019.01.03.15.56.34; Thu, 03 Jan 2019 15:56:49 -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=@kernel.org header.s=default header.b=DcKWQg92; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726392AbfACSqI (ORCPT + 99 others); Thu, 3 Jan 2019 13:46:08 -0500 Received: from mail.kernel.org ([198.145.29.99]:38782 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726332AbfACSqI (ORCPT ); Thu, 3 Jan 2019 13:46:08 -0500 Received: from mail-qk1-f176.google.com (mail-qk1-f176.google.com [209.85.222.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 714AF2184B; Thu, 3 Jan 2019 18:46:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1546541167; bh=feEzb5DmN/tcbVN7HizVbAa2zKmf011KYyDHrWocAPY=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=DcKWQg92TvgrrnqKTYo9AlDequCxuKMlLuLItgL7ixQ/FLd62HxyfdTVOnW13nQwZ dgyL8VI0WdZSFLQcKoU8guNMxWaTzbavFI/RCTMbaI9WeQIJ7U4z5Y+nTDrQ4yyZXE 5aQwtdpBdvAEqqOVRTtvrUPD2u2NFrMleyFbYcKs= Received: by mail-qk1-f176.google.com with SMTP id d15so5738989qkj.0; Thu, 03 Jan 2019 10:46:07 -0800 (PST) X-Gm-Message-State: AJcUuke2MG1ysOildv1nzoX0DZNbi5BZQfNOsZzEt2/g3tRfPbFc+MM9 jQ/kIryq1lQx0abS4iApYbwbCrGfiknJWbF8mg== X-Received: by 2002:ae9:ef14:: with SMTP id d20mr45626127qkg.147.1546541166685; Thu, 03 Jan 2019 10:46:06 -0800 (PST) MIME-Version: 1.0 References: <1546438198-1677-1-git-send-email-henryc.chen@mediatek.com> <1546438198-1677-3-git-send-email-henryc.chen@mediatek.com> In-Reply-To: <1546438198-1677-3-git-send-email-henryc.chen@mediatek.com> From: Rob Herring Date: Thu, 3 Jan 2019 12:45:54 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [RFC RESEND PATCH 2/7] dt-bindings: soc: Add opp table on scpsys bindings To: Henry Chen Cc: Viresh Kumar , Stephen Boyd , Matthias Brugger , Ulf Hansson , Mark Rutland , Fan Chen , Weiyi Lu , James Liao , Kees Cook , "open list:THERMAL" , devicetree@vger.kernel.org, "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" , linux-mediatek@lists.infradead.org, "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jan 2, 2019 at 8:10 AM Henry Chen wrote: > > Add opp table on scpsys dt-bindings for Mediatek SoC. > > Signed-off-by: Henry Chen > --- > Documentation/devicetree/bindings/opp/mtk-opp.txt | 24 +++++++++++++ > .../devicetree/bindings/soc/mediatek/scpsys.txt | 42 ++++++++++++++++++++++ > 2 files changed, 66 insertions(+) > create mode 100644 Documentation/devicetree/bindings/opp/mtk-opp.txt > > diff --git a/Documentation/devicetree/bindings/opp/mtk-opp.txt b/Documentation/devicetree/bindings/opp/mtk-opp.txt > new file mode 100644 > index 0000000..036be1c > --- /dev/null > +++ b/Documentation/devicetree/bindings/opp/mtk-opp.txt > @@ -0,0 +1,24 @@ > +Mediatek OPP bindings to descibe OPP nodes with level values > + > +OPP tables for devices on Mediatek platforms require an additional > +platform specific level value to be specified. > +This value is passed on to the mediatek Power Management Unit by the > +CPU, which then takes the necessary actions to set a voltage rail > +to an appropriate voltage based on the value passed. > + > +The bindings are based on top of the operating-points-v2 bindings > +described in Documentation/devicetree/bindings/opp/opp.txt > +Additional properties are described below. > + > +* OPP Table Node > + > +Required properties: > +- compatible: Allow OPPs to express their compatibility. It should be: > + "operating-points-v2-mtk-level" > + > +* OPP Node > + > +Required properties: > +- mtk,level: On Mediatek platforms an OPP node can describe a positive value > +representing a level that's communicated with a our power management hardware > +which then translates it into a certain voltage on a voltage rail. Work with the Qcom folks and create a common level property. Rob