From: Lin Huang <hl@rock-chips.com>
To: heiko@sntech.de, dianders@chromium.org, mturquette@baylibre.com,
myungjoo.ham@samsung.com, kyungmin.park@samsung.com
Cc: linux-clk@vger.kernel.org, sboyd@codeaurora.org,
dbasehore@chromium.org, linux-rockchip@lists.infradead.org,
linux-kernel@vger.kernel.org, Lin Huang <hl@rock-chips.com>
Subject: [PATCH 0/2] Bring up rk3399 ddr frequency scaling
Date: Thu, 19 Nov 2015 18:21:09 +0800 [thread overview]
Message-ID: <1447928471-14448-1-git-send-email-hl@rock-chips.com> (raw)
these patchset bring up rk3399 ddr frequency scaling flow,
use devfreq framework and simple_ondemand policy. Ddr set
rate function will implement in dcf controller which run in
the ATF, and rk3399 ATF not ready now, so we need finish it
when rk3399 ATF ready.
Lin Huang (2):
clk: rockchip: dmc: support rk3399 dmc clock driver
devfreq: rockchip: support rk3399 dmc devfreq
drivers/clk/rockchip/Makefile | 1 +
drivers/clk/rockchip/clk-rk3399-dmc.c | 196 ++++++++++++++++++++
drivers/devfreq/Kconfig | 1 +
drivers/devfreq/Makefile | 1 +
drivers/devfreq/rockchip/Kconfig | 8 +
drivers/devfreq/rockchip/Makefile | 1 +
drivers/devfreq/rockchip/rk3399_dmc.c | 327 ++++++++++++++++++++++++++++++++++
include/soc/rockchip/rk3399-dmc-clk.h | 36 ++++
8 files changed, 571 insertions(+)
create mode 100644 drivers/clk/rockchip/clk-rk3399-dmc.c
create mode 100644 drivers/devfreq/rockchip/Kconfig
create mode 100644 drivers/devfreq/rockchip/Makefile
create mode 100644 drivers/devfreq/rockchip/rk3399_dmc.c
create mode 100644 include/soc/rockchip/rk3399-dmc-clk.h
--
1.9.1
next reply other threads:[~2015-11-19 10:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 10:21 Lin Huang [this message]
2015-11-19 10:21 ` [PATCH 1/2] clk: rockchip: dmc: support rk3399 dmc clock driver Lin Huang
2015-11-19 21:47 ` Heiko Stuebner
2015-11-20 1:37 ` hl
2015-11-21 18:30 ` Heiko Stuebner
2015-11-23 9:20 ` hl
2015-11-19 10:21 ` [PATCH 2/2] devfreq: rockchip: support rk3399 dmc devfreq Lin Huang
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=1447928471-14448-1-git-send-email-hl@rock-chips.com \
--to=hl@rock-chips.com \
--cc=dbasehore@chromium.org \
--cc=dianders@chromium.org \
--cc=heiko@sntech.de \
--cc=kyungmin.park@samsung.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=myungjoo.ham@samsung.com \
--cc=sboyd@codeaurora.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
all inboxes | Powered by JetHome®