From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Lezcano Subject: Re: [PATCH v2 0/4] clocksource: rockchip/timer: Support rktimer for rk3399 Date: Mon, 13 Jun 2016 15:06:25 +0200 Message-ID: <20160613130625.GC10634@linaro.org> References: <1465275273-22076-1-git-send-email-wxt@rock-chips.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <1465275273-22076-1-git-send-email-wxt-TNX95d0MmH7DzftRWevZcw@public.gmane.org> 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: Caesar Wang Cc: huangtao-TNX95d0MmH7DzftRWevZcw@public.gmane.org, devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Heiko Stuebner , Xing Zheng , Masahiro Yamada , Catalin Marinas , Shawn Lin , Brian Norris , Will Deacon , dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org, Mark Rutland , linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, Rob Herring , smbarber-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org, cf-TNX95d0MmH7DzftRWevZcw@public.gmane.org, briannorris-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org, Thomas Gleixner , Jianqun Xu , linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org List-Id: devicetree@vger.kernel.org On Tue, Jun 07, 2016 at 12:54:29PM +0800, Caesar Wang wrote: > This series patches had been tested on rockchip inside kernel. > In order to support the rk3399 SoC timer and turn off interrupts and IPIs to > save power in idle. For my personnal information, are the arch_timer in the same power domain than the CPU ? IOW, what is the 'always-on' property in the DT ? > Okay, it still works bootup on rk3288/other SoCs, even though many socs > hasn't used > the broadcast timer. Yes, unfortunately the SoC design on rk3288 and the previous ones do not allow to use a cpuidle driver with cpu/cluster power down, so obviously the broadcast timer is pointless on these boards :) > History version: > v1: > https://lkml.org/lkml/2016/5/25/186 > > Easy to test for my borad. > localhost / # cat /proc/interrupts > CPU0 CPU1 CPU2 CPU3 CPU4 CPU5 > 1: 0 0 0 0 0 0 GICv3 29 Edge arch_timer > ... > 5: 0 0 0 0 0 0 GICv3 113 Level rk_timer > .. > > localhost / # cat /proc/timer_list | grep event_handler > get "event_handler: hrtimer_interrupt" > event_handler: tick_handle_oneshot_broadcast > event_handler: hrtimer_interrupt What are you trying to demonstrate here ? There are no interrupts for both arch_timer and rk_timer. > That should work for my board. What do you mean ?