From: Tao Huang <huangtao@rock-chips.com>
To: Heiko Stuebner <heiko@sntech.de>, Caesar Wang <wxt@rock-chips.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org,
Brian Norris <briannorris@chromium.org>,
Xing Zheng <zhengxing@rock-chips.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Catalin Marinas <catalin.marinas@arm.com>,
dbasehore@chromium.org, Will Deacon <will.deacon@arm.com>,
dianders@chromium.org, Rob Herring <robh+dt@kernel.org>,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
tony.xie@rock-chips.com, David Wu <david.wu@rock-chips.com>,
cf@rock-chips.com, Jianqun Xu <jay.xu@rock-chips.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: dts: rockchip: Add idle-states to device tree for rk3399
Date: Mon, 13 Aug 2018 00:24:45 +0800 [thread overview]
Message-ID: <ae312dc3-f640-ecf3-049a-c8576bb83330@rock-chips.com> (raw)
In-Reply-To: <5620784.b19SH5PkdR@phil>
Hi Heiko:
On 2018年08月10日 04:09, Heiko Stuebner wrote:
> Am Mittwoch, 6. Juli 2016, 10:20:54 CEST schrieb Caesar Wang:
>
>> arch/arm64/boot/dts/rockchip/rk3399.dtsi | 18 ++++++++++++++++++
>> 1 file changed, 18 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/rockchip/rk3399.dtsi b/arch/arm64/boot/dts/rockchip/rk3399.dtsi
>> index a6dd623..12ce265 100644
>> --- a/arch/arm64/boot/dts/rockchip/rk3399.dtsi
>> +++ b/arch/arm64/boot/dts/rockchip/rk3399.dtsi
>> @@ -101,6 +101,18 @@
>> };
>> };
>>
>> + idle-states {
>> + entry-method = "psci";
>> + cpu_sleep: cpu-sleep-0 {
>> + compatible = "arm,idle-state";
>> + local-timer-stop;
>> + arm,psci-suspend-param = <0x0010000>;
>> + entry-latency-us = <350>;
>> + exit-latency-us = <600>;
>> + min-residency-us = <1150>;
> Looking at the chromeos kernel, there are some more patches adapting
> this idle-state to use different timings.
Yes, we have another values. So the values of this patch are wrong.
>
> There also was a cluster-idle state added for a while but that seems to
> cause audio issues according to the CrOS history.
DMA or Audio driver should add PM_QOS_CPU_DMA_LATENCY or other methods to avoid the effects of idle.
Idle itself is good.
Thanks!
next prev parent reply other threads:[~2018-08-12 16:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 8:20 [PATCH] arm64: dts: rockchip: Add idle-states to device tree for rk3399 Caesar Wang
2018-08-09 20:09 ` Heiko Stuebner
2018-08-12 16:24 ` Tao Huang [this message]
2018-08-13 8:25 ` Heiko Stuebner
2018-08-13 8:59 ` Tao Huang
2018-08-24 10:02 Tony Xie
2018-08-24 10:03 ` Tony Xie
2018-08-29 12:49 ` Heiko Stuebner
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=ae312dc3-f640-ecf3-049a-c8576bb83330@rock-chips.com \
--to=huangtao@rock-chips.com \
--cc=briannorris@chromium.org \
--cc=catalin.marinas@arm.com \
--cc=cf@rock-chips.com \
--cc=david.wu@rock-chips.com \
--cc=dbasehore@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=heiko@sntech.de \
--cc=jay.xu@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=tony.xie@rock-chips.com \
--cc=will.deacon@arm.com \
--cc=wxt@rock-chips.com \
--cc=yamada.masahiro@socionext.com \
--cc=zhengxing@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).