From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Chanwoo Choi <cw00.choi@samsung.com>,
myungjoo.ham@samsung.com, kgene@kernel.org
Cc: kyungmin.park@samsung.com, robh+dt@kernel.org,
pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
linux@arm.linux.org.uk, tjakobi@math.uni-bielefeld.de,
linux.amoon@gmail.com, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 02/19] PM / devfreq: exynos: Add documentation for generic exynos bus frequency driver
Date: Thu, 10 Dec 2015 09:39:26 +0900 [thread overview]
Message-ID: <5668C9BE.7050900@samsung.com> (raw)
In-Reply-To: <1449634091-1842-3-git-send-email-cw00.choi@samsung.com>
On 09.12.2015 13:07, Chanwoo Choi wrote:
> This patch adds the documentation for generic exynos bus frequency
> driver.
>
> Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
> ---
> .../devicetree/bindings/devfreq/exynos-bus.txt | 94 ++++++++++++++++++++++
> 1 file changed, 94 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/devfreq/exynos-bus.txt
>
> diff --git a/Documentation/devicetree/bindings/devfreq/exynos-bus.txt b/Documentation/devicetree/bindings/devfreq/exynos-bus.txt
> new file mode 100644
> index 000000000000..54a1f9c46c88
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/devfreq/exynos-bus.txt
> @@ -0,0 +1,94 @@
> +* Generic Exynos Bus frequency device
> +
> +The Samsung Exynos SoC have many buses for data transfer between DRAM
> +and sub-blocks in SoC. Almost Exynos SoC have the common architecture
> +for buses. Generally, the each bus of Exynos SoC includes the source clock
> +and power line and then is able to change the clock according to the usage
> +of each buses on runtime. When gathering the usage of each buses on runtime,
> +thie driver uses the PPMU (Platform Performance Monitoring Unit) which
s/thie/the/
> +is able to measure the current load of sub-blocks.
> +
> +There are a little different composition among Exynos SoC because each Exynos
> +SoC has the different sub-blocks. So, this difference should be specified
> +in devicetree file instead of each device driver. In result, this driver
> +is able to support the bus frequency for all Exynos SoCs.
> +
> +Required properties for bus device:
> +- compatible: Should be "samsung,exynos-bus".
> +- clock-names : the name of clock used by the bus, "bus".
> +- clocks : phandles for clock specified in "clock-names" property.
> +- #clock-cells: should be 1.
This is a clock consumer, right? So the clock-cells is not valid here.
> +- operating-points-v2: the OPP table including frequency/voltage information
> + to support DVFS (Dynamic Voltage/Frequency Scaling) feature.
> +- vdd-supply: the regulator to provide the buses with the voltage.
> +- devfreq-events: the devfreq-event device to monitor the curret utilization
s/curret/current/
> + of buses.
> +
> +Optional properties for bus device:
> +- exynos,saturation-ratio: the percentage value which is used to calibrate
> + the performance count againt total cycle count.
s/againt/against/
> +
> +Example1:
> + Show the AXI buses of Exynos3250 SoC. Exynos3250 divides the buses to
> + power line (regulator). The MIF (Memory Interface) AXI bus is used to
> + transfer data between DRAM and CPU and uses the VDD_MIF regualtor.
> +
> + - power line(VDD_MIF) --> bus for DMC (Dynamic Memory Controller) block
> +
> + - MIF bus's frequency/voltage table
> + -----------------------
> + |Lv| Freq | Voltage |
> + -----------------------
> + |L1| 50000 |800000 |
> + |L2| 100000 |800000 |
> + |L3| 134000 |800000 |
> + |L4| 200000 |800000 |
> + |L5| 400000 |875000 |
> + -----------------------
> +
> +Example2 :
> + The bus of DMC (Dynamic Memory Controller) block in exynos3250.dtsi
> + are listed below:
s/are/is/ (one bus is listed)
> +
> + bus_dmc: bus_dmc {
> + compatible = "samsung,exynos-bus";
> + clocks = <&cmu_dmc CLK_DIV_DMC>;
> + clock-names = "bus";
> + operating-points-v2 = <&bus_dmc_opp_table>;
> + status = "disabled";
> + };
> +
> + bus_dmc_opp_table: opp_table0 {
> + compatible = "operating-points-v2";
> + opp-shared;
> +
> + opp00 {
Maybe use convention with frequency, like:
opp@50000000
This also used in opp.txt examples.
> + opp-hz = /bits/ 64 <50000000>;
> + opp-microvolt = <800000>;
> + };
> + opp01 {
> + opp-hz = /bits/ 64 <100000000>;
> + opp-microvolt = <800000>;
> + };
> + opp02 {
> + opp-hz = /bits/ 64 <134000000>;
> + opp-microvolt = <800000>;
> + };
> + opp03 {
> + opp-hz = /bits/ 64 <200000000>;
> + opp-microvolt = <800000>;
> + };
> + opp04 {
> + opp-hz = /bits/ 64 <400000000>;
> + opp-microvolt = <875000>;
> + };
> + };
> +
> + Usage case to handle the frequency and voltage of bus on runtime
> + in exynos3250-rinato.dts are listed below:
s/are/is/
> +
> + &bus_dmc {
> + devfreq-events = <&ppmu_dmc0_3>, <&ppmu_dmc1_3>;
> + vdd-supply = <&buck1_reg>; /* VDD_MIF */
> + status = "okay";
> + };
>
next prev parent reply other threads:[~2015-12-10 0:39 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 4:07 [PATCH v2 00/19] PM / devferq: Add generic exynos bus frequency driver and new passive governor Chanwoo Choi
2015-12-09 4:07 ` [PATCH v2 01/19] PM / devfreq: exynos: Add generic exynos bus frequency driver Chanwoo Choi
2015-12-09 4:07 ` [PATCH v2 02/19] PM / devfreq: exynos: Add documentation for " Chanwoo Choi
2015-12-10 0:39 ` Krzysztof Kozlowski [this message]
2015-12-10 0:49 ` Chanwoo Choi
2015-12-10 1:25 ` Krzysztof Kozlowski
2015-12-10 1:33 ` Chanwoo Choi
2015-12-09 4:07 ` [PATCH v2 03/19] ARM: dts: Add DMC bus node for Exynos3250 Chanwoo Choi
2015-12-10 0:44 ` Krzysztof Kozlowski
2015-12-10 1:09 ` Chanwoo Choi
2015-12-10 1:20 ` Krzysztof Kozlowski
2015-12-10 2:00 ` Chanwoo Choi
2015-12-10 2:04 ` Krzysztof Kozlowski
2015-12-10 2:17 ` Chanwoo Choi
2015-12-10 2:21 ` Krzysztof Kozlowski
2015-12-09 4:07 ` [PATCH v2 04/19] ARM: dts: Add DMC bus frequency for exynos3250-rinato/monk Chanwoo Choi
2015-12-10 0:53 ` Krzysztof Kozlowski
2015-12-10 0:56 ` Chanwoo Choi
2015-12-09 4:07 ` [PATCH v2 05/19] PM / devfreq: Add new passive governor Chanwoo Choi
2015-12-09 4:07 ` [PATCH v2 06/19] PM / devfreq: Add devfreq_get_devfreq_by_phandle() Chanwoo Choi
2015-12-09 4:07 ` [PATCH v2 07/19] PM / devfreq: Show the related information according to governor type Chanwoo Choi
2015-12-09 4:08 ` [PATCH v2 08/19] PM / devfreq: exynos: Add support of bus frequency of sub-blocks using passive governor Chanwoo Choi
2015-12-09 4:08 ` [PATCH v2 09/19] PM / devfreq: exynos: Update documentation for bus devices " Chanwoo Choi
2015-12-10 1:31 ` Krzysztof Kozlowski
2015-12-10 1:36 ` Chanwoo Choi
2015-12-10 14:21 ` Rob Herring
2015-12-10 15:10 ` Chanwoo Choi
2015-12-11 3:24 ` Rob Herring
2015-12-11 3:56 ` Chanwoo Choi
2015-12-09 4:08 ` [PATCH v2 10/19] PM / devfreq: exynos: Add the detailed correlation between sub-blocks and power line Chanwoo Choi
2015-12-09 4:08 ` [PATCH v2 11/19] PM / devfreq: exynos: Remove unused exynos4/5 busfreq driver Chanwoo Choi
2015-12-09 4:08 ` [PATCH v2 12/19] ARM: dts: Add bus nodes using VDD_INT for Exynos3250 Chanwoo Choi
2015-12-10 2:09 ` Krzysztof Kozlowski
2015-12-10 2:30 ` Chanwoo Choi
2015-12-09 4:08 ` [PATCH v2 13/19] ARM: dts: Add bus nodes using VDD_MIF for Exynos4x12 Chanwoo Choi
2015-12-10 3:17 ` Krzysztof Kozlowski
2015-12-10 4:21 ` Chanwoo Choi
2015-12-09 4:08 ` [PATCH v2 14/19] ARM: dts: Add bus nodes using VDD_INT " Chanwoo Choi
2015-12-10 5:57 ` Krzysztof Kozlowski
2015-12-10 6:08 ` Chanwoo Choi
2015-12-10 6:32 ` Krzysztof Kozlowski
2015-12-10 6:43 ` Chanwoo Choi
2015-12-10 6:53 ` Krzysztof Kozlowski
2015-12-10 7:07 ` Chanwoo Choi
2015-12-10 7:12 ` Krzysztof Kozlowski
2015-12-10 7:18 ` Chanwoo Choi
2015-12-09 4:08 ` [PATCH v2 15/19] ARM: dts: Add bus nodes using VDD_MIF for Exynos4210 Chanwoo Choi
2015-12-09 4:08 ` [PATCH v2 16/19] ARM: dts: Add PPMU node for exynos4412-odroidu3 Chanwoo Choi
2015-12-10 6:44 ` Krzysztof Kozlowski
2015-12-11 2:27 ` Chanwoo Choi
2015-12-09 4:08 ` [PATCH v2 17/19] ARM: dts: Add support of bus frequency using VDD_INT for exynos3250-rinato Chanwoo Choi
2015-12-10 6:58 ` Krzysztof Kozlowski
2015-12-10 7:24 ` Chanwoo Choi
2015-12-09 4:08 ` [PATCH v2 18/19] ARM: dts: Expand the voltage range of buck1/3 regulator for exynos4412-odroidu3 Chanwoo Choi
2015-12-10 7:02 ` Krzysztof Kozlowski
2015-12-10 7:19 ` Chanwoo Choi
2015-12-09 4:08 ` [PATCH v2 19/19] ARM: dts: Add support of bus frequency for exynos4412-trats/odroidu3 Chanwoo Choi
2015-12-10 7:08 ` Krzysztof Kozlowski
2015-12-10 7:23 ` Chanwoo Choi
2015-12-09 19:05 ` [PATCH v2 00/19] PM / devferq: Add generic exynos bus frequency driver and new passive governor Anand Moon
2015-12-10 0:12 ` Chanwoo Choi
2015-12-10 4:14 ` Anand Moon
2015-12-10 4:20 ` Chanwoo Choi
2015-12-10 0:57 ` Krzysztof Kozlowski
2015-12-10 1:22 ` Krzysztof Kozlowski
2015-12-10 2:16 ` Chanwoo Choi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5668C9BE.7050900@samsung.com \
--to=k.kozlowski@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kgene@kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux.amoon@gmail.com \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=myungjoo.ham@samsung.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=tjakobi@math.uni-bielefeld.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox