From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
To: Chanwoo Choi <cw00.choi@samsung.com>
Cc: myungjoo.ham@samsung.com, kyungmin.park@samsung.com,
rafael.j.wysocki@intel.com, nm@ti.com, b.zolnierkie@samsaung.com,
pawel.moll@arm.com, mark.rutland@arm.com, swarren@wwwdotorg.org,
ijc+devicetree@hellion.org.uk, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
devicetree@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCHv2 8/8] devfreq: exynos4: Add busfreq driver for exynos4210/exynos4x12
Date: Thu, 13 Mar 2014 17:50:57 +0100 [thread overview]
Message-ID: <3380793.YDA220hUJP@amdc1032> (raw)
In-Reply-To: <1394698649-20996-9-git-send-email-cw00.choi@samsung.com>
On Thursday, March 13, 2014 05:17:29 PM Chanwoo Choi wrote:
> This patch add busfreq driver for Exynos4210/Exynos4x12 memory interface
This patch adds DT binding documentation not the driver itself.
Same comment for the patch summary line.
> and bus to support DVFS(Dynamic Voltage Frequency Scaling) according to PPMU
> counters. PPMU (Performance Profiling Monitorings Units) of Exynos4 SoC provides
> PPMU counters for DMC(Dynamic Memory Controller) to check memory bus utilization
> and then busfreq driver adjusts dynamically the operating frequency/voltage
> by using DEVFREQ Subsystem.
>
> Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
> ---
> .../devicetree/bindings/devfreq/exynos4_bus.txt | 49 ++++++++++++++++++++++
> 1 file changed, 49 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/devfreq/exynos4_bus.txt
>
> diff --git a/Documentation/devicetree/bindings/devfreq/exynos4_bus.txt b/Documentation/devicetree/bindings/devfreq/exynos4_bus.txt
> new file mode 100644
> index 0000000..2a83fcc
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/devfreq/exynos4_bus.txt
> @@ -0,0 +1,49 @@
> +
> +Exynos4210/4x12 busfreq driver
> +-----------------------------
> +
> +Exynos4210/4x12 Soc busfreq driver with devfreq for Memory bus frequency/voltage
SoC
> +scaling according to PPMU counters of memory controllers
> +
> +Required properties:
> +- compatible : should contain Exynos4 SoC type as follwoing:
following
> + - "samsung,exynos4x12-busfreq" for Exynos4x12
> + - "samsung,exynos4210-busfreq" for Exynos4210
> +- reg : offset and length of the ppmudmc0/1
> + - PPMU (Performance Profiling Monitoring Units)
> + : It is to profile performance event of DMC(Dynamic Memory
> + Controller) So, exynos4_bus.c can check memory bus utilization
> + by using PPMU of Exynos4 SoC.
It can be improved by changing ordering, i.e.
: PPMU of Exynos4 SoC is used to profile performance event of DMC (Dynamic
Memory Controller) so the driver can check memory bus utilization.
> +- clocks : clock number of ppmudmc0/1
> +- clock-names : clock name of ppmudmc0/1
> +- vdd_int-supply: regulator for interface block of Exynos4
> +
> +Optional properties:
> +- vdd_mif-supply: regulator for DMC block of Exynos4x12 if Exynos4x12 Soc
if using Exynos4x12 SoC
> +- regs-name : register name of ppmudmc0/1
> +
> +All the required listed above must be defined under code busfreq with devfreq
required properties
> +Exmaple:
Example:
> +For Exynos4210 busfreq,
please add a newline here
> + busfreq@106A0000 {
> + compatible = "samsung,exynos4210-busfreq";
> + reg = <0x106A0000 0x2000>, <0x106B0000 0x2000>;
> + regs-name = "PPMU_DMC0", "PPMU_DMC1";
> + clocks = <&clock CLK_PPMUDMC0>, <&clock CLK_PPMUDMC1>;
> + clock-names = "ppmudmc0", "ppmudmc1";
> +
> + vdd_int-supply = <&buck3_reg>;
> + };
> +
> +For Exynos4x12 busfreq,
ditto
> + busfreq@106A0000 {
> + compatible = "samsung,exynos4x12-busfreq";
> + reg = <0x106A0000 0x2000>, <0x106B0000 0x2000>;
> + regs-name = "PPMU_DMC0", "PPMU_DMC1";
> + clocks = <&clock CLK_PPMUDMC0>, <&clock CLK_PPMUDMC1>;
> + clock-names = "ppmudmc0", "ppmudmc1";
> +
> + vdd_mif-suppy = <&buck1_reg>;
> + vdd_int-supply = <&buck3_reg>;
> + };
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics
next prev parent reply other threads:[~2014-03-13 16:50 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 8:17 [PATCHv2 0/8] devfreq: exynos4: Support dt and use common ppmu driver Chanwoo Choi
2014-03-13 8:17 ` [PATCHv2 1/8] devfreq: exynos4: Support devicetree to get device id of Exynos4 SoC Chanwoo Choi
2014-03-13 8:17 ` [PATCHv2 2/8] devfreq: exynos4: Use common ppmu driver and get ppmu address from dt data Chanwoo Choi
2014-03-13 8:17 ` [PATCHv2 3/8] devfreq: exynos4: Add ppmu's clock control and code clean about regulator control Chanwoo Choi
2014-03-14 17:42 ` Tomasz Figa
2014-03-17 2:51 ` Chanwoo Choi
2014-03-17 5:35 ` Chanwoo Choi
2014-03-17 5:59 ` Chanwoo Choi
2014-03-18 11:13 ` Tomasz Figa
2014-03-19 2:44 ` Chanwoo Choi
2014-03-13 8:17 ` [PATCHv2 4/8] devfreq: exynos4: Fix bug of resource leak and code clean on probe() Chanwoo Choi
2014-03-14 17:49 ` Tomasz Figa
2014-03-17 5:05 ` Chanwoo Choi
2014-03-18 12:18 ` Tomasz Figa
2014-03-19 2:46 ` Chanwoo Choi
2014-03-13 8:17 ` [PATCHv2 5/8] devfreq: exynos4: Use SET_SYSTEM_SLEEP_PM_OPS macro Chanwoo Choi
2014-03-13 8:17 ` [PATCHv2 6/8] devfreq: exynos4: Fix power-leakage of clock on suspend state Chanwoo Choi
2014-03-14 17:52 ` Tomasz Figa
2014-03-17 2:58 ` Chanwoo Choi
2014-03-13 8:17 ` [PATCHv2 7/8] devfreq: exynos4: Add CONFIG_PM_OPP dependency to fix probe fail Chanwoo Choi
2014-03-13 8:17 ` [PATCHv2 8/8] devfreq: exynos4: Add busfreq driver for exynos4210/exynos4x12 Chanwoo Choi
2014-03-13 16:50 ` Bartlomiej Zolnierkiewicz [this message]
2014-03-13 17:53 ` Mark Rutland
2014-03-14 7:14 ` Chanwoo Choi
2014-03-14 10:35 ` Mark Rutland
2014-03-14 10:56 ` Chanwoo Choi
2014-03-14 17:35 ` Tomasz Figa
2014-03-15 11:36 ` Kyungmin Park
2014-03-15 12:41 ` Tomasz Figa
2014-03-17 5:19 ` Chanwoo Choi
2014-03-18 15:46 ` Tomasz Figa
[not found] ` <53286A6C.5090108-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2014-03-19 9:47 ` Chanwoo Choi
2014-03-19 10:23 ` Tomasz Figa
2014-03-13 16:43 ` [PATCHv2 0/8] devfreq: exynos4: Support dt and use common ppmu driver Bartlomiej Zolnierkiewicz
2014-03-14 3:14 ` Chanwoo Choi
2014-03-14 10:47 ` Bartlomiej Zolnierkiewicz
2014-03-17 1:56 ` Chanwoo Choi
2014-03-14 17:58 ` Tomasz Figa
2014-03-17 1:58 ` Chanwoo Choi
2014-03-18 15:47 ` Tomasz Figa
2014-07-09 13:06 ` Tomeu Vizoso
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=3380793.YDA220hUJP@amdc1032 \
--to=b.zolnierkie@samsung.com \
--cc=b.zolnierkie@samsaung.com \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kyungmin.park@samsung.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=myungjoo.ham@samsung.com \
--cc=nm@ti.com \
--cc=pawel.moll@arm.com \
--cc=rafael.j.wysocki@intel.com \
--cc=swarren@wwwdotorg.org \
/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;
as well as URLs for NNTP newsgroup(s).