From: Chanwoo Choi <cw00.choi@samsung.com>
To: Lin Huang <hl@rock-chips.com>, heiko@sntech.de
Cc: myungjoo.ham@samsung.com, mark.yao@rock-chips.com,
airlied@linux.ie, mturquette@baylibre.com,
dbasehore@chromium.org, sboyd@codeaurora.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
dianders@chromium.org, linux-rockchip@lists.infradead.org,
kyungmin.park@samsung.com, linux-arm-kernel@lists.infradead.org,
tixy@linaro.org, typ@rock-chips.com, sudeep.holla@arm.com,
mark.rutland@arm.com, linux-pm@vger.kernel.org
Subject: Re: [PATCH v5 6/8] Documentation: bindings: add dt documentation for rk3399 dmc
Date: Wed, 10 Aug 2016 13:38:02 +0900 [thread overview]
Message-ID: <57AAAFAA.8060200@samsung.com> (raw)
In-Reply-To: <1470799604-12877-7-git-send-email-hl@rock-chips.com>
Hi Lin,
On 2016년 08월 10일 12:26, Lin Huang wrote:
> This patch adds the documentation for rockchip rk3399 dmc driver.
>
> Signed-off-by: Lin Huang <hl@rock-chips.com>
> ---
> Changes in v5:
> -None
>
> Changes in v4:
> -None
>
> Changes in v3:
> -None
>
> Changes in v2:
> -None
>
> Changes in v1:
> -None
>
> .../devicetree/bindings/devfreq/rk3399_dmc.txt | 35 ++++++++++++++++++++++
> 1 file changed, 35 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/devfreq/rk3399_dmc.txt
>
> diff --git a/Documentation/devicetree/bindings/devfreq/rk3399_dmc.txt b/Documentation/devicetree/bindings/devfreq/rk3399_dmc.txt
> new file mode 100644
> index 0000000..90e9581
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/devfreq/rk3399_dmc.txt
> @@ -0,0 +1,35 @@
> +* Rockchip rk3399 dmc device
dmc -> DMC(Dynamic Memory Controller ?)
> +
> +Required properties:
> +- compatible: Must be "rockchip,rk3399-dmc".
> +- devfreq-events: Node to get ddr loading, Refer to
> + Documentation/devicetree/bindings/devfreq/rockchip-dif.txt
> +- interrupts: The interrupt number to the cpu. The interrupt specifier format
> + depends on the interrupt controller.
If you add the specific role of this interrupt, it would be better
to understand the operation of interrupt.
> +- clocks: Phandles for clock specified in "clock-names" property
> +- clock-names : The name of clock used by the DFI, must be "pclk_ddr_mon";
"pclk_ddr_mon" -> "dmc_clk"
> +- operating-points-v2: Refer to Documentation/devicetree/bindings/power/opp.txt
> + for details.
> +- center-supply: Dmc supply node.
> +- status: Marks the node enabled/disabled.
> +
> +Optional properties:
> +- ddr_timing: ddr timing need to pass to arm trust firmware
> +- upthreshold: the upthreshold to simpleondeamnd policy
> +- downdifferential: The downdifferential to simpleondeamnd policy
> +
> +Example:
> + dmc: dmc {
> + compatible = "rockchip,rk3399-dmc";
> + devfreq-events = <&dfi>;
> + interrupts = <GIC_SPI 1 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&cru SCLK_DDRCLK>;
> + clock-names = "dmc_clk";
> + ddr_timing = <&ddr_timing>;
I think that you should add the detailed document for
'ddr_timing' because we don't understand the 'ddr_timing' easily
, it depends on the trust firmware.
> + operating-points-v2 = <&dmc_opp_table>;
I think that you better to add the example of 'dmc_opp_table'
in the documentation.
> + center-supply = <&ppvar_centerlogic>;
> + upthreshold = <15>;
> + downdifferential = <10>;
> + status = "disabled";
> + };
> +
>
Regards,
Chanwoo Choi
next prev parent reply other threads:[~2016-08-10 4:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-10 3:26 [PATCH v5 0/8] rk3399 support ddr frequency scaling Lin Huang
2016-08-10 3:26 ` [PATCH v5 1/8] clk: rockchip: add new clock-type for the ddrclk Lin Huang
2016-08-10 3:26 ` [PATCH v5 2/8] clk: rockchip: rk3399: add SCLK_DDRCLK ID for ddrc Lin Huang
2016-08-10 3:26 ` [PATCH v5 3/8] clk: rockchip: rk3399: add ddrc clock support Lin Huang
2016-08-10 3:26 ` [PATCH v5 4/8] Documentation: bindings: add dt documentation for dfi controller Lin Huang
2016-08-10 4:29 ` Chanwoo Choi
2016-08-10 3:26 ` [PATCH v5 5/8] PM / devfreq: event: support rockchip " Lin Huang
2016-08-10 3:26 ` [PATCH v5 6/8] Documentation: bindings: add dt documentation for rk3399 dmc Lin Huang
2016-08-10 4:38 ` Chanwoo Choi [this message]
2016-08-10 3:26 ` [PATCH v5 7/8] PM / devfreq: rockchip: add devfreq driver " Lin Huang
2016-08-10 4:39 ` kbuild test robot
2016-08-10 4:39 ` [PATCH] PM / devfreq: rockchip: fix semicolon.cocci warnings kbuild test robot
2016-08-10 5:01 ` [PATCH v5 7/8] PM / devfreq: rockchip: add devfreq driver for rk3399 dmc Chanwoo Choi
2016-08-10 9:05 ` kbuild test robot
2016-08-10 9:07 ` kbuild test robot
2016-08-10 3:26 ` [PATCH v5 8/8] drm/rockchip: Add dmc notifier in vop driver Lin Huang
2016-08-10 5:07 ` Chanwoo Choi
2016-08-10 5:28 ` kbuild test robot
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=57AAAFAA.8060200@samsung.com \
--to=cw00.choi@samsung.com \
--cc=airlied@linux.ie \
--cc=dbasehore@chromium.org \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=hl@rock-chips.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mark.yao@rock-chips.com \
--cc=mturquette@baylibre.com \
--cc=myungjoo.ham@samsung.com \
--cc=sboyd@codeaurora.org \
--cc=sudeep.holla@arm.com \
--cc=tixy@linaro.org \
--cc=typ@rock-chips.com \
/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).