Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp2005384imj; Sun, 17 Feb 2019 20:57:15 -0800 (PST) X-Google-Smtp-Source: AHgI3IZgkppa1ORL5xVWSndr4WTh50EkhXL8o8UNnyp8Rv2YMK5TivSh8gIiWbk8KRoHn0XqB1I9 X-Received: by 2002:a17:902:7e49:: with SMTP id a9mr2102948pln.303.1550465835570; Sun, 17 Feb 2019 20:57:15 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550465835; cv=none; d=google.com; s=arc-20160816; b=Sao7UcR/J8QbGAsy3p+GAfhhFh4zDimbVMm1TbpJJbG7IyInZnAkqk47gxLOtTAEDh hdEeTC1aGn0/pYzoq6q7WytVllT3UgGlrrbylDHn2Z+I8U8ACUnKYYg85qdn7vbZcPd6 5BLyy0DZfRF3l1j77SeBpP/nSw7vJ76Stbv9VyjfbEhJhcBegAWpO2Y8o26edZTYT44w cnjegIxXqZDg7KLVMJWeCp6q53aenOHMBMl50ltfOnaWUe/7ze8H2uCgkkCJ0FqSH6x0 KI0vmVz8HASNkeVVSmYO2PuZwtL2ySvb000bC35ex8HtTEKX51wAVVuX2n6UCjRiBJav VdWw== 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:mime-version :references:in-reply-to:date:cc:to:from:subject:message-id; bh=fS2vrtKPk+0WPvO5gNSjwfBlRHDLlg+MKpD30nZinEg=; b=pIBwtB1N1zxpAmCC611s8LVca65nOia73hodXhMgwKwkGQIyro0dTC/82YPfe99jOh 8I+TfMP/5Rb1yUygh0Pegbni/NkC1Pj2ALBzavi9SWU11B3DhQtiaBxHpOSRqzk+9aeq O79aVqkb95TwRfWXzf6vgjQOjsPKxaUrxTkZh3fLy2CNq3QUzq+jo9T4Bz9Fgr7w/U2v ni3a95pxagO2eipjbwNTy1y8zzBTInhk4hTs9HcRAX/MuFSg9Gknl3e0PVSLpUuiMsVv fhwetn1e0omx/qBrr4ENUUBX0Bzm6HEMaMuDVj+aXmmOML6xxcnUrD56xZxOH2LqUC94 DM/Q== ARC-Authentication-Results: i=1; mx.google.com; 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 t75si12517937pfa.170.2019.02.17.20.57.00; Sun, 17 Feb 2019 20:57:15 -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; 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 S1728569AbfBREzk (ORCPT + 99 others); Sun, 17 Feb 2019 23:55:40 -0500 Received: from mailgw02.mediatek.com ([210.61.82.184]:16912 "EHLO mailgw02.mediatek.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1727003AbfBREzj (ORCPT ); Sun, 17 Feb 2019 23:55:39 -0500 X-UUID: 888638359e1c4688a19102aa919db65b-20190218 X-UUID: 888638359e1c4688a19102aa919db65b-20190218 Received: from mtkcas07.mediatek.inc [(172.21.101.84)] by mailgw02.mediatek.com (envelope-from ) (mhqrelay.mediatek.com ESMTP with TLS) with ESMTP id 1849433455; Mon, 18 Feb 2019 12:55:33 +0800 Received: from mtkcas09.mediatek.inc (172.21.101.178) by mtkmbs01n1.mediatek.inc (172.21.101.68) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Mon, 18 Feb 2019 12:55:32 +0800 Received: from [172.21.77.4] (172.21.77.4) by mtkcas09.mediatek.inc (172.21.101.73) with Microsoft SMTP Server id 15.0.1395.4 via Frontend Transport; Mon, 18 Feb 2019 12:55:32 +0800 Message-ID: <1550465732.32365.6.camel@mtksdaap41> Subject: Re: [RFC RESEND PATCH 1/7] dt-bindings: soc: Add DVFSRC driver bindings From: Henry Chen To: Rob Herring CC: Mark Rutland , James Liao , Ulf Hansson , "Kees Cook" , Weiyi Lu , , Stephen Boyd , Viresh Kumar , , Fan Chen , , , Matthias Brugger , Date: Mon, 18 Feb 2019 12:55:32 +0800 In-Reply-To: <20190111160918.GA20480@bogus> References: <1546438198-1677-1-git-send-email-henryc.chen@mediatek.com> <1546438198-1677-2-git-send-email-henryc.chen@mediatek.com> <20190111160918.GA20480@bogus> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.4-0ubuntu2 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-MTK: N Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Rob, Sorry for late reply. I missed this mail before. On Fri, 2019-01-11 at 10:09 -0600, Rob Herring wrote: > On Wed, Jan 02, 2019 at 10:09:52PM +0800, Henry Chen wrote: > > Document the binding for enabling DVFSRC on MediaTek SoC. > > > > Signed-off-by: Henry Chen > > --- > > .../devicetree/bindings/soc/mediatek/dvfsrc.txt | 26 ++++++++++++++++++++++ > > include/dt-bindings/soc/mtk,dvfsrc.h | 18 +++++++++++++++ > > 2 files changed, 44 insertions(+) > > create mode 100644 Documentation/devicetree/bindings/soc/mediatek/dvfsrc.txt > > create mode 100644 include/dt-bindings/soc/mtk,dvfsrc.h > > > > diff --git a/Documentation/devicetree/bindings/soc/mediatek/dvfsrc.txt b/Documentation/devicetree/bindings/soc/mediatek/dvfsrc.txt > > new file mode 100644 > > index 0000000..402c885 > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/soc/mediatek/dvfsrc.txt > > @@ -0,0 +1,26 @@ > > +MediaTek DVFSRC Driver > > Bindings are for h/w blocks, not drivers. ok. > > > +The Dynamic Voltage and Frequency Scaling Resource Collector (DVFSRC) is a > > +HW module which is used to collect all the requests from both software and > > +hardware and turn into the decision of minimum operating voltage and minimum > > +DRAM frequency to fulfill those requests. > > Seems like the OPP table should be a child of this instead of where you > currently have it? Do you means the opp table that I put on scpsys likes below? I think this opp table is used for mapping the performance state of power domain, so I put it on scpsys device tree document. dvfsrc_opp_table: opp-table { compatible = "operating-points-v2-level"; dvfsrc_vol_min: opp1 { opp,level = ; }; dvfsrc_freq_medium: opp2 { opp,level = ; }; dvfsrc_freq_max: opp3 { opp,level = ; }; dvfsrc_vol_max: opp4 { opp,level = ; }; }; > > > + > > +Required Properties: > > +- compatible: Should be one of the following > > + - "mediatek,mt8183-dvfsrc": For MT8183 SoC > > +- reg: Address range of the DVFSRC unit > > +- dram_type: Refer to for the > > + different dram type support. > > This information should come from the DDR controller or memory nodes > probably. And we already have some properties related to DDR type. Sorry, I don't know that before, could you give some hint or example for that? > > > +- clock-names: Must include the following entries: > > + "dvfsrc": DVFSRC module clock > > +- clocks: Must contain an entry for each entry in clock-names. > > + > > +Example: > > + > > + dvfsrc_top@10012000 { > > Drop the '_top'. (Don't use '_' in node and property names).. ok > > > + compatible = "mediatek,mt8183-dvfsrc"; > > + reg = <0 0x10012000 0 0x1000>; > > + clocks = <&infracfg CLK_INFRA_DVFSRC>; > > + clock-names = "dvfsrc"; > > + dram_type = ; > > + }; > > diff --git a/include/dt-bindings/soc/mtk,dvfsrc.h b/include/dt-bindings/soc/mtk,dvfsrc.h > > new file mode 100644 > > index 0000000..60b3497 > > --- /dev/null > > +++ b/include/dt-bindings/soc/mtk,dvfsrc.h > > @@ -0,0 +1,18 @@ > > +/* SPDX-License-Identifier: GPL-2.0 > > + * > > + * Copyright (c) 2018 MediaTek Inc. > > + */ > > + > > +#ifndef _DT_BINDINGS_POWER_MTK_DVFSRC_H > > +#define _DT_BINDINGS_POWER_MTK_DVFSRC_H > > + > > +#define MT8183_DVFSRC_OPP_LP4 0 > > +#define MT8183_DVFSRC_OPP_LP4X 1 > > +#define MT8183_DVFSRC_OPP_LP3 2 > > + > > +#define MT8183_DVFSRC_LEVEL_1 1 > > +#define MT8183_DVFSRC_LEVEL_2 2 > > +#define MT8183_DVFSRC_LEVEL_3 3 > > +#define MT8183_DVFSRC_LEVEL_4 4 > > + > > +#endif /* _DT_BINDINGS_POWER_MTK_DVFSRC_H */ > > -- > > 1.9.1 > > > > _______________________________________________ > Linux-mediatek mailing list > Linux-mediatek@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-mediatek