From: Lin Huang <hl@rock-chips.com>
To: myungjoo.ham@samsung.com
Cc: cw00.choi@samsung.com, dianders@chromium.org,
linux-rockchip@lists.infradead.org, linux-pm@vger.kernel.org,
dbasehore@chromium.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Lin Huang <hl@rock-chips.com>
Subject: [RESEND PATCH v3 2/2] PM/devfreq: rk3399: get devfreq suspend frequency
Date: Mon, 7 Nov 2016 14:33:40 +0800 [thread overview]
Message-ID: <1478500420-22045-3-git-send-email-hl@rock-chips.com> (raw)
In-Reply-To: <1478500420-22045-1-git-send-email-hl@rock-chips.com>
We need ddr run a specific frequency when ddr dvfs stop
working. For example: if we enable two monitor, then we will
stop ddr dvfs, but we hope ddr can run in highest frequency
obviously.
Signed-off-by: Lin Huang <hl@rock-chips.com>
---
Changes in v2:
- None
Changes in v3:
- None
drivers/devfreq/rk3399_dmc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/devfreq/rk3399_dmc.c b/drivers/devfreq/rk3399_dmc.c
index 5a2da95..39f8e27 100644
--- a/drivers/devfreq/rk3399_dmc.c
+++ b/drivers/devfreq/rk3399_dmc.c
@@ -329,7 +329,7 @@ static int rk3399_dmcfreq_probe(struct platform_device *pdev)
if (IS_ERR(data->devfreq))
return PTR_ERR(data->devfreq);
devm_devfreq_register_opp_notifier(dev, data->devfreq);
-
+ devfreq_opp_get_suspend_opp(dev, data->devfreq);
data->dev = dev;
platform_set_drvdata(pdev, data);
pd_register_notify_to_dmc(data->devfreq);
--
1.9.1
next prev parent reply other threads:[~2016-11-07 6:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 6:33 [RESEND PATCH v3 0/2] set specific ddr frequency when stop ddr dvfs Lin Huang
2016-11-07 6:33 ` [RESEND PATCH v3 1/2] PM/devfreq: add suspend frequency support Lin Huang
2016-11-07 6:33 ` Lin Huang [this message]
[not found] ` <CGME20161107063403epcas5p4f8d0d95b9a997ca7bf2b2702c3e5d337@epcas5p4.samsung.com>
2016-11-08 2:06 ` MyungJoo Ham
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=1478500420-22045-3-git-send-email-hl@rock-chips.com \
--to=hl@rock-chips.com \
--cc=cw00.choi@samsung.com \
--cc=dbasehore@chromium.org \
--cc=dianders@chromium.org \
--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=myungjoo.ham@samsung.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