Received: by 2002:ac0:aed5:0:0:0:0:0 with SMTP id t21csp3202325imb; Tue, 5 Mar 2019 03:37:07 -0800 (PST) X-Google-Smtp-Source: APXvYqzI5S/mIK/kVPMJ6Tp27KoH0qK4Cj87jckatu7xPVgE6dY951N5spDlRnqtAZy6egdXCdEC X-Received: by 2002:a17:902:6a4:: with SMTP id 33mr772553plh.140.1551785827277; Tue, 05 Mar 2019 03:37:07 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1551785827; cv=none; d=google.com; s=arc-20160816; b=PJAzrVp02ii0hWv5hkaQxLkUr5oVpxm5rlTPsGEzT+hza9Ad14Fot8jeWIiO0rywAU GIt1HoBrxJ5yFhy6UbW3ZN7wj9UArERsaam8nh4sFM0tiJEGtzNFLmbs1jg7mirTa6e5 Zk7xrNmk0dZVmBQawf033GUgpMEw/AZU5wiwnqwKrL9cVtBtGAcXwuBl+esuVldxS2aj 2jMN0myncUwWzSt1mDYHxQQNde5M35wQnBJxntrkurwacPWC+GcmXNncDMrfLtr+emai ZGB6QLhz5Eww9pG7KIzsj2FZiQ2GvSSn72ZAugMQzc7XyACcy/zM1L6p1C+fzw3b93TW xdfQ== 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=giS4FYJZ7zjc8sro5BteXwCfEazYz3L1HmrZolB2paE=; b=H56CxLVeRvQOSyCJhBmjJPXqgMPqDHufQzjyDgc2C0AidLJimvqXxj92JYsu+tNibT 2iKiitjaufZ6DNsapbHN4SPn2AM8y77XwEHHHk+RAvTO5lnmOkW0GJJxUNm8Ng9L95tG L73a0wu7F7Y+bWIKkI2NS4iHvCzPTNeGm7FQg09pmwQ2gEO2XlJx/amRHWE+rqHLN4JL 50cleNBG+jIJ830CkHG6zcOBIkT9jusgvNGAPzeLwQ1HHi2MMWq6rq7AzOjR7SR3hqSa lRD3J64Dta+Z49cQYIHZ8iSk+BltsCic8Xt+hNlBssJON2P8RsTjXol7EGGapcNiDkwT EHRA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=rvRzBScn; 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 f23si8558140pfa.228.2019.03.05.03.36.51; Tue, 05 Mar 2019 03:37:07 -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=rvRzBScn; 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 S1727720AbfCELgI (ORCPT + 99 others); Tue, 5 Mar 2019 06:36:08 -0500 Received: from mail.kernel.org ([198.145.29.99]:35626 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727100AbfCELgI (ORCPT ); Tue, 5 Mar 2019 06:36:08 -0500 Received: from mail-lj1-f175.google.com (mail-lj1-f175.google.com [209.85.208.175]) (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 6654D2087C; Tue, 5 Mar 2019 11:36:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1551785766; bh=XFUes7GdOksQM4mA+OSH4FC7XXt5+0KgBMovc5w26Vs=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=rvRzBScn51P+UO8qfFGkJ/HTANQTddrk/YOmlMQ+EJdl2zJ6yCj+F44ZXZ2WVV5Nu xo3eUKK+KaMEsioc+xD2+ZWvDn6W+tnBTiD3a3WfNntqq8gaQ9Z4rGqSuDAEtQA/BV SNP3mRPy5N9PZB5JZE/3/Yb0DemK2u0lD015dLNM= Received: by mail-lj1-f175.google.com with SMTP id g80so7293570ljg.6; Tue, 05 Mar 2019 03:36:06 -0800 (PST) X-Gm-Message-State: APjAAAU4RMsjbNeRX8yRaf6yASYSsCH00flqjpkUZ3o9MrrbpNkAEImI DonSFD/qXIt/F1wKf4gl4pulribNQjDRSPdV7hE= X-Received: by 2002:a2e:2c3:: with SMTP id y64mr13712590lje.131.1551785764433; Tue, 05 Mar 2019 03:36:04 -0800 (PST) MIME-Version: 1.0 References: <1551781151-5562-1-git-send-email-l.luba@partner.samsung.com> <1551781151-5562-5-git-send-email-l.luba@partner.samsung.com> In-Reply-To: <1551781151-5562-5-git-send-email-l.luba@partner.samsung.com> From: Krzysztof Kozlowski Date: Tue, 5 Mar 2019 12:35:53 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v5 4/8] dt-bindings: devfreq: add Exynos5422 DMC device description To: Lukasz Luba Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, "linux-samsung-soc@vger.kernel.org" , =?UTF-8?B?QmFydMWCb21pZWogxbtvxYJuaWVya2lld2ljeg==?= , kgene@kernel.org, Chanwoo Choi , kyungmin.park@samsung.com, Marek Szyprowski , s.nawrocki@samsung.com, myungjoo.ham@samsung.com 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 Tue, 5 Mar 2019 at 11:19, Lukasz Luba wrote: > > The patch adds description for DT binding for a new Exynos5422 Dynamic > Memory Controller device. > > Signed-off-by: Lukasz Luba > --- > .../devicetree/bindings/devfreq/exynos5422-dmc.txt | 177 +++++++++++++++++++++ > 1 file changed, 177 insertions(+) > create mode 100644 Documentation/devicetree/bindings/devfreq/exynos5422-dmc.txt > > diff --git a/Documentation/devicetree/bindings/devfreq/exynos5422-dmc.txt b/Documentation/devicetree/bindings/devfreq/exynos5422-dmc.txt > new file mode 100644 > index 0000000..0e73e98 > --- /dev/null > +++ b/Documentation/devicetree/bindings/devfreq/exynos5422-dmc.txt > @@ -0,0 +1,177 @@ > +* Exynos5422 frequency and voltage scaling for Dynamic Memory Controller device > + > +The Samsung Exynos5422 SoC has DMC (Dynamic Memory Controller) to which the DRAM > +memory chips are connected. The driver is to monitor the controller in runtime > +and switch frequency and voltage. To monitor the usage of the controller in > +runtime, the driver uses the PPMU (Platform Performance Monitoring Unit), which > +is able to measure the current load of the memory. > +When 'userspace' governor is used for the driver, an application is able to > +switch the DMC frequency. > + > +Required properties for DMC device for Exynos5422: > +- compatible: Should be "samsung,exynos5422-bus". > +- clock-names : the name of clock used by the bus, "bus". > +- clocks : phandles for clock specified in "clock-names" property. > +- devfreq-events : phandles for PPMU devices connected to this DMC. > + > +The example definition of a DMC and PPMU devices declared in DT is shown below: > + > + ppmu_dmc0_0: ppmu@10d00000 { > + compatible = "samsung,exynos-ppmu"; > + reg = <0x10d00000 0x2000>; > + clocks = <&clock CLK_PCLK_PPMU_DREX0_0>; > + clock-names = "ppmu"; > + status = "okay"; > + events { > + ppmu_event_dmc0_0: ppmu-event3-dmc0_0 { > + event-name = "ppmu-event3-dmc0_0"; > + }; > + }; > + }; > + > + > + ppmu_dmc0_1: ppmu@10d10000 { > + compatible = "samsung,exynos-ppmu"; > + reg = <0x10d10000 0x2000>; > + clocks = <&clock CLK_PCLK_PPMU_DREX0_1>; > + clock-names = "ppmu"; > + status = "okay"; > + events { > + ppmu_event_dmc0_1: ppmu-event3-dmc0_1 { > + event-name = "ppmu-event3-dmc0_1"; > + }; > + }; > + }; > + > + ppmu_dmc1_0: ppmu@10d10000 { > + compatible = "samsung,exynos-ppmu"; > + reg = <0x10d60000 0x2000>; > + clocks = <&clock CLK_PCLK_PPMU_DREX1_0>; > + clock-names = "ppmu"; > + status = "okay"; > + events { > + ppmu_event_dmc1_0: ppmu-event3-dmc1_0 { > + event-name = "ppmu-event3-dmc1_0"; > + }; > + }; > + }; > + > + ppmu_dmc1_1: ppmu@10d70000 { > + compatible = "samsung,exynos-ppmu"; > + reg = <0x10d70000 0x2000>; > + clocks = <&clock CLK_PCLK_PPMU_DREX1_1>; > + clock-names = "ppmu"; > + status = "okay"; > + events { > + ppmu_event_dmc1_1: ppmu-event3-dmc1_1 { > + event-name = "ppmu-event3-dmc1_1"; > + }; > + }; > + }; > + > + dmc: memory-controller@10c20000 { > + compatible = "samsung,exynos5422-dmc"; > + reg = <0x10c20000 0x10000>, <0x10c30000 0x10000>, > + <0x10000000 0x1000>; > + clocks = <&clock CLK_FOUT_SPLL>, > + <&clock CLK_MOUT_SCLK_SPLL>, > + <&clock CLK_FF_DOUT_SPLL2>, > + <&clock CLK_FOUT_BPLL>, > + <&clock CLK_MOUT_BPLL>, > + <&clock CLK_SCLK_BPLL>, > + <&clock CLK_MOUT_MX_MSPLL_CCORE>, > + <&clock CLK_MOUT_MX_MSPLL_CCORE_PHY>, > + <&clock CLK_MOUT_MCLK_CDREX>, > + <&clock CLK_DOUT_CLK2X_PHY0>, > + <&clock CLK_CLKM_PHY0>, > + <&clock CLK_CLKM_PHY1>, > + <&clock CLK_CDREX_PAUSE>, > + <&clock CLK_CDREX_TIMING_SET>; > + clock-names = "fout_spll", > + "mout_sclk_spll", > + "ff_dout_spll2", > + "fout_bpll", > + "mout_bpll", > + "sclk_bpll", > + "mout_mx_mspll_ccore", > + "mout_mx_mspll_ccore_phy", > + "mout_mclk_cdrex", > + "dout_clk2x_phy0", > + "clkm_phy0", > + "clkm_phy1", > + "clk_cdrex_pause", > + "clk_cdrex_timing_set"; > + status = "okay"; > + operating-points-v2 = <&dmc_opp_table>; > + devfreq-events = <&ppmu_dmc0_0>, <&ppmu_dmc0_1>, > + <&ppmu_dmc1_0>, <&ppmu_dmc1_1>; > + }; > + > +The needed timings of DRAM memory are stored in dedicated nodes. > +There are two nodes with regular timings and for bypass mode. > + > + dmc_bypass_mode: bypass_mode { > + compatible = "samsung,dmc-bypass-mode"; This looks like an example, not bindings. > + > + freq-hz = <400000000>; > + volt-uv = <887500>; -microvolt Documentation/devicetree/bindings/property-units.txt > + dram-timing-row = <0x365a9713>; > + dram-timing-data = <0x4740085e>; > + dram-timing-power = <0x543a0446>; > + }; > + > + dram_timing: timing { > + compatible = "samsung,dram-timing"; Probably you should use timings from Documentation/devicetree/bindings/lpddr2/ If not, all the fields below should be described. All these bindings (memory-controller, timings) look like description of memory controller so maybe they should go into Documentation/devicetree/bindings/memory-controllers ? Best regards, Krzysztof > + > + dram-timing-names = "165MHz", "206MHz", "275MHz", "413MHz", > + "543MHz", "633MHz", "728MHz", "825MHz"; > + dram-timing-row = <0x11223185>, <0x112331C6>, <0x12244287>, > + <0x1B35538A>, <0x244764CD>, <0x2A48758F>, > + <0x30598651>, <0x365A9713>; > + dram-timing-data = <0x2720085E>, <0x2720085E>, <0x2720085E>, > + <0x2720085E>, <0x3730085E>, <0x3730085E>, > + <0x3730085E>, <0x4740085E>; > + dram-timing-power = <0x140C0225>, <0x180F0225>, <0x1C140225>, > + <0x2C1D0225>, <0x38270335>, <0x402D0335>, > + <0x4C330336>, <0x543A0446>; > + }; > + > +The frequencies supported by the DMC are stored in OPP table v2. > + > + dmc_opp_table: opp_table2 { > + compatible = "operating-points-v2"; > + > + opp00 { > + opp-hz = /bits/ 64 <165000000>; > + opp-microvolt = <875000>; > + }; > + opp01 { > + opp-hz = /bits/ 64 <206000000>; > + opp-microvolt = <875000>; > + }; > + opp02 { > + opp-hz = /bits/ 64 <275000000>; > + opp-microvolt = <875000>; > + }; > + opp03 { > + opp-hz = /bits/ 64 <413000000>; > + opp-microvolt = <887500>; > + }; > + opp04 { > + opp-hz = /bits/ 64 <543000000>; > + opp-microvolt = <937500>; > + }; > + opp05 { > + opp-hz = /bits/ 64 <633000000>; > + opp-microvolt = <1012500>; > + }; > + opp06 { > + opp-hz = /bits/ 64 <728000000>; > + opp-microvolt = <1037500>; > + }; > + opp07 { > + opp-hz = /bits/ 64 <825000000>; > + opp-microvolt = <1050000>; > + }; > + }; > + > -- > 2.7.4 >