From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lorenzo Pieralisi Subject: [RFC] rk3368 idle states Date: Wed, 2 Dec 2015 11:18:58 +0000 Message-ID: <20151202111858.GB18981@red-moon> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "Linux-rockchip" Errors-To: linux-rockchip-bounces+glpar-linux-rockchip=m.gmane.org-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org To: Heiko Stuebner Cc: linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org List-Id: linux-rockchip.vger.kernel.org Hi Heiko, while reviewing other dts idle states bindings I spotted the following snippet in arch/arm64/boot/dts/rockchip/rk3368.dtsi: cpu_sleep: cpu-sleep-0 { compatible = "arm,idle-state"; arm,psci-suspend-param = <0x1010000>; entry-latency-us = <0x3fffffff>; exit-latency-us = <0x40000000>; min-residency-us = <0xffffffff>; }; Could you please explain to me how you obtained these residency/latency values ? They make NO sense whatsoever and I am quite tempted to ask you to remove this data from the dts file, it is just wrong. Thanks, Lorenzo